One of the ways you can secure data and applications in hybrid clouds is to employ Microsoft's Azure Active Directory...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
(AD) and its single sign-on access control feature. Azure AD is a multitenancy cloud and identity management service designed to enable employees to use a common identity across cloud services and on-premises software.
If you are already using the Azure cloud, setting up single sign-on (SSO) should be simple. With SSO you can enable role-based access to a range of software as a service (SaaS) applications, such as Microsoft Office 365 and Salesforce.com, by allowing employees to securely access multiple resources with a single login.
However, it is difficult to set up SSO access control. Many people get lost in the hall of mirrors that is the Azure set-up process. (See the series of support documents on MSDN here.) Microsoft promises to do a better job integrating SSO access control into the Azure management portal and to simplify its control menus soon.
Eventually, Azure Active Directory will be the control point for the Windows Store, according to the company. Still, Azure AD is mainly a developer's toolkit rather than a polished identity management service such as Okta or Ping Identity. Its main dashboard, shown in Figure 1, is somewhat barebones compared to other SSO tools.
For hybrid management, you should start by downloading the Azure AD Connector to integrate your on-premises directories with Azure AD. The AD Connector installs various pieces of software on your Windows Server AD Forest. Azure AD supports several identity providers, including Windows Live ID, Facebook, Google, Yahoo, JSON Web Tokens, OpenID, SAML and WS-Federation.
It also has a SaaS app catalog you can browse to add SSO logins. You then add each app to your portal page with a simple three-step process to permit the sign-on relationship, enable automatic provisioning, and assign particular users to that app.
Administrators have three choices on how the sign-on happens: either by establishing a federation between Azure and the app service provider (this is probably the preferred method), having Azure store the user's account credentials, or using some other existing SSO relationship. Azure AD Reporting offers more than a dozen reports, including account provisioning activity, irregular sign-ons, and sign-ons from multiple locations.
If you are looking to add multifactor authentication (more than user name and password) to on-premises applications and cloud services, you'll need an Azure AD Premium account and the Enterprise Mobility Suite. Azure Multifactor Authentication is a service (formerly PhoneFactor) that adds a second layer of security via a text message, phone call, mobile app notification or verification code and third-party Open Authentication tokens, according to Microsoft. Once a separate Windows application, it's now integrated with the overall Azure service. Azure Multifactor Authentication is far more limited than other vendors' MFA tools, however, as shown in Figure 2; it does offer, though, a one-time bypass feature if a user is locked out of their account. This means employees can reset their AD passwords from within their own portal pages. (That's one less IT support call when they forget their password).
If you are already using the Azure cloud, it makes sense to take a closer look at what Azure AD will buy you and whether your developers can incorporate its SSO tools into your homegrown apps.
Azure AD has three different pricing options. The free version is included with an Azure or Office 365 subscription and can provide SSO for up to 10 apps per user. There are also basic and premium subscription levels (the latter for unlimited apps that also includes the SSO for no extra charge, which is probably the preference for most enterprises) that are covered by various Microsoft corporate purchase agreements or available online for $6 per user per month.
About the author:
David Strom is a freelance writer and professional speaker based in St. Louis. He is former editor in chief of TomsHardware.com, Network Computingmagazine and DigitalLanding.com. Read more from Strom at Strominator.com.
Learn more on implementing single sign-on for cloud apps with Azure Active Directory