Now you've freed yourself doubly- everyone else can just trust that logins work, and the team focusing on logins can focus on just that one thing.
Logins are a bad example because it really shouldn't take 100k lines to handle it, but replace 'logins' with any business domain logic that you need.
And honestly, the biggest challenge often is building the simplest API possible without limiting your clients.
So, where you might think microservices others may be thinking of your monolithic login service.
If everyone interacts with the login service through the same interfaces, then they don't need to know how it breaks out internally or care.
If, however, you use it through one set of API features, and I use it through another very disconnected set, then perhaps it's time to break it down further.
At the end of the day, though, what does it contain? A list of users, their roles, and access control mechanisms. Does it make sense to have unified logins or multiple sets of logins across your company's services? If the latter, break it down to be run once per other application with specialised selection of features per application. If the former, let the login team handle control of the system and leave it a 100k monolith or break it down as they see fit.
What % of your services consist of less than 100 lines of code? 1,000? 10,000?
PS: Nanoservices are often used as the negative extreme, but as Microservices have a rather fluid definition people are not always on the same page.