I have a back-end service that needs to read from and write into Azure AD. I was able to read and write using graph api by authenticating using tenant info, client id and secret key (these values come from Authentication Scenarios for Azure AD | Basics of Registering an Application in Azure AD).
Using the tenant info, client id and secret key for authentication means that end users need to register their tenants by manually specifying these values and I am trying to avoid this manual step of registration where users need to specify these values.
I have also looked at the multi-tenant application admin/user consent and its associated sampleIntegrating applications with azure active directory. However, the issue with the admin consent is that it enables all users in the directory to have access to the directory.
Is there any other way where I can provide a registration link of some sort, let the global admin user authenticate and consent for permission at which point some sort of an access or refresh token can be persisted for use by the back-end service?