Book Image

Mastering Identity and Access Management with Microsoft Azure

By : Jochen Nickel
Book Image

Mastering Identity and Access Management with Microsoft Azure

By: Jochen Nickel

Overview of this book

Microsoft Azure and its Identity and Access Management is at the heart of Microsoft’s Software as a Service, including Office 365, Dynamics CRM, and Enterprise Mobility Management. It is an essential tool to master in order to effectively work with the Microsoft Cloud. Through practical, project based learning this book will impart that mastery. Beginning with the basics of features and licenses, this book quickly moves on to the user and group lifecycle required to design roles and administrative units for role-based access control (RBAC). Learn to design Azure AD to be an identity provider and provide flexible and secure access to SaaS applications. Get to grips with how to configure and manage users, groups, roles, and administrative units to provide a user- and group-based application and self-service access including the audit functionality. Next find out how to take advantage of managing common identities with the Microsoft Identity Manager 2016 and build cloud identities with the Azure AD Connect utility. Construct blueprints with different authentication scenarios including multi-factor authentication. Discover how to configure and manage the identity synchronization and federation environment along with multi -factor authentication, conditional access, and information protection scenarios to apply the required security functionality. Finally, get recommendations for planning and implementing a future-oriented and sustainable identity and access management strategy.
Table of Contents (22 chapters)
Mastering Identity and Access Management with Microsoft Azure
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
16
Choosing the Right Technology, Methods, and Future Trends

Using alternate login ID and ADAL


In special scenarios, you need to work with the alternate login ID concept. In this case, you use another attribute than the UPN, for example, the e-mail address. Be aware that this way is usually the last option (in our opinion). Normally, we always try to work out our solutions with the usage of the UPN.

This section will cover the following topics:

  • Disassociation of AAD UPN from AD DS UPN and trade-offs

  • What does modern authentication mean?

  • How does Outlook authentication work today?

  • How authentication happens with Word and SharePoint Online

Disassociation of AAD UPN from AD DS UPN and trade-offs

In case you choose the alternate login ID, your AAD instance will still require a username in the UPN format, such as [email protected]. To provide this solution, you need to customize your AAD Connect, or other synchronization solutions, and your federation options. The following figure gives you an idea of the solution design and the different authentication flows:

...