When you decide to move your Exchange environment to the cloud, you might be confused to discover that you still need to maintain an on-premises Exchange server. There are several reasons for this, stemming from the migration process and on to Identity Management.
If you’re moving from an active on-premises Exchange deployment, you’ll first configure an interim “Exchange Hybrid” environment which hosts mailboxes within Exchange Online and your local Exchange server. The two locations share namespace, address books, free-busy, calendars, really every Exchange functionality is synced between them. Mail flow and other functions appear to be internal, but might actually be processed and stored in the cloud environment.
Microsoft Azure Active Directory (AAD) is a multi-tenant cloud-based directory and identity management service. It combines core directory services, access management, and identity protection in to a single solution. Azure Active Directory is not to be confused with Azure Active Directory Domain Services, which is a separate service and not the focus of this article.
For every organization that chooses to subscribe to Microsoft Online Services– Office 365, Dynamics 365, Intune, etc., choosing the correct identity model for AAD becomes an important task. In this article, we will have a look at the characteristics of each.
While there are no specific dependencies on the identity model of AAD for Microsoft Online Services to function, your organizational needs and other factors such as manageability, access control, auditing, and user experience determine which identity model should be deployed.
Microsoft Azure Active Directory, or AAD, is an IDaaS (Identity as a Service) offering that helps you manage corporate identities in the cloud. In this blog series, we're taking a look at the primary AAD features that you'll use to get your ID management up and running for Azure cloud services.
In Part 1 we discussed Connect, Single-Sign On, and Multifactor Authentication. You can also find a table of AAD pricing on that post. Remember, this series is not a deep dive into AAD configuration, but rather an overview of key features. Depending on your SKU you may or may not have access to all of these features.
Part 2 includes Self Service Password Resets, Identity Protection, Conditional Access, and Privileged Identity Management. These features help you control access and maintain security and compliance protocol across your enterprise cloud.
Microsoft Azure Active Directory is an IDaaS (Identity as a Service) offering that helps you manage corporate identities in the cloud. The solution itself is a cloud service that is hosted in Microsoft Azure datacenters globally. You can provision your tenant in a datacenter closest to where your organization is located.
Since AAD is a cloud offering it of course requires a paid subscription to use many of its features. But there’s a free tier for those who want to explore and are just getting started with the service.
This two part article is not a deep dive how-to guide. Rather, this is an effort to talk about a few major features available with AAD that you can use to get started with managing identities in the cloud. Depending on your AAD SKU, you may, or you may not have some of the features that are being discussed.
Within the tech industry there are many challenges standing in the way of growing tech firms, particularly to those attempting to separate themselves from the rest of the pack.