Azure AD App Registration in Plain English (Exam Prep FAQs) 

Glad it helped. 👍

Thank you! Glad this was helpful. 👍

You're very welcome! ☺

Glad you liked 👍

Yes. Planning to produce an updated version in the next few weeks to address recent changes. Can add some guidance in areas you are suggesting.

You are welcome!

Excellent. Glad to hear that. Good luck! 🤞👍

Glad you liked it!

Thanks. Hope it helps! 👍

Glad it helped!

Thank you kindly!

Thanks! 👍

It would be more accurate to say service principals avoid use of service accounts as they exist in on-premises Active Directory. You'll find a good read on service principals and managed identities at devblogs.microsoft.com/devops/demystifying-service-principals-managed-identities/

Glad it helped. 👍

Per-site access is possible. Look at good blog posts here devblogs.microsoft.com/microsoft365dev/controlling-app-access-on-specific-sharepoint-site-collections/ and here mmsharepoint.wordpress.com/2021/08/18/accessing-sharepoint-sites-with-resource-specific-consent-rsc-and-microsoft-graph/

Sorry for delayed reply, your comment was incorrectly flagged by RU-vid as spam. managed identity came along after service principal, and are the preferred approach. Use system identities on services that support them, as it is auto-created and auto-removed along with the service it is tied to. User-assigned managed identities are created independent of a resource, but you have to delete them manually (less convenient). You could say the difference between a managed identity and a service principal is that a managed identity "manages" the creation and automatic renewal of a service principal on your behalf.

Sounds a bit more complicated as you have a custom authentication strategy. Some high-level guidance from Microsoft starts here - docs.microsoft.com/en-us/azure/active-directory/fundamentals/five-steps-to-full-application-integration-with-azure-ad

Hmm, your comment just popped up here. For non-Microsoft apps, the vendor (Oracle, in this case) will generally provide instructions for app registration in Azure AD in their documentation.

It depends. Are you expecting users to authenticate with a work identity (Azure AD or federated) or social identity (Facebook, Google, etc). If the first, look at Azure AD B2B. If the latter, Azure AD B2C.

@@InsideCloudAndSecurity Thanks for the answer, I am still a bit not sure? as for my scenario, I like the user to Signup with any email id (abc@xyz.com), and that email I am looking to save in the backend(Spring + mysql DB) as well and then map that email as Primary key for that customer in the DB

You bet!

Don't. App registration is tough for EVERYONE! 😉

Sorry, your comment got automatically pushed into a moderation bucket. This is a feature of Azure AD, so you don't need an Azure sub or Office 365 to use this feature.