This is Sue Bohn, director of program management for Identity and Access Management. I’m thrilled to announce the first post in our Voice of the Partner blog series. Today we’ve invited Joe Stocker of Patriot Consulting to share five tips that can dramatically improve the customer’s migration process from Active Directory Federation Services (ADFS) to Azure Active Directory (Azure AD). This story is a great reminder that some challenges aren’t nearly as difficult as they first seem.
Patriot Consulting, a member of our partner network, focuses on helping customers deploy Microsoft cloud solutions securely. The company has a unique view into current business drivers and customer strategy when it comes to the cloud. For example, Joe Stocker and his colleagues have recently noted an acceleration in the number of customers migrating off ADFS and third-party identity and access solutions to Azure AD. I’m pleased that he agreed to share a couple customer stories that illustrate the following insights:
I am one of the founders at Patriot Consulting Technology Group, which means I spend my days helping Microsoft’s customers deploy and secure Microsoft 365 solutions. This work gives me a broad view of trends developing in the industry. One thing we’ve observed is that our clients have begun to reassess their identity and access management solutions. Some are concerned about an on-premises outage disrupting authentication for all their users. Many discover that they have multiple identity and access management solutions and see an opportunity to cut costs.
Our client at West Coast University are a great example of this trend. They previously used ADFS to authenticate users and supported about 30 software as a service (SaaS) and security assertion markup language (SAML) apps. Users were able to access cloud apps and the network using a single sign-on, however, IT wanted to better protect the organization from compromised user accounts. The security capabilities of Azure AD, especially conditional access, was very attractive to them. Conditional access could allow them to detect session-based conditions and apply automated security policies depending on the risk-level associated with the session. For example, if access to one of those 30 apps was attempted from a personal device, Azure AD could work with Microsoft Cloud App Security and Microsoft Intune to apply security controls. Depending on the circumstances and policies, Azure AD could allow access, force multi-factor authentication or block access. If access was allowed, Azure AD could work with Microsoft Cloud App Security to limit the actions users could take, such as encrypting or blocking downloads.
Our client West Coast University was convinced of the security advantages of Azure AD, but they were worried about a cumbersome migration process. They weren’t certain if Azure AD would support all their apps. The truth is, I don’t blame them. I remember when it could take six to twelve months to migrate that many apps from ADFS to Azure AD, however, Microsoft recently launched the ADFS to Azure AD app migration tool, which has simplified the process. We advised the following tips to West Coast University:
Before we even got started, a program manager at Microsoft did a demo of the migration tool for West Coast University, and our clients were blown away.
“The tool is amazing. I can’t even articulate how much time it saved us with this project. Don’t start your migration without it.”
The demo quickly put their minds at ease, and we got started. The ADFS to Azure AD app migration tool identified twenty apps that would migrate with no problem, and ten that would need additional troubleshooting. We segmented the challenging apps into two categories: one group of apps required SAML request signing. The second group required token encryption. We called the vendors for the first set of apps to understand if SAML request signing was a hard requirement and learned it was not, which cleared those apps. Microsoft recently launched token encryption in public preview, which allowed us to migrate the second group of apps. This tool dramatically simplified the process, allowing us to address problems early in the process.
The project was a huge win for our clients at West Coast University. We were able to complete the migration in about six to eight weeks, and they now have the session-based security controls to better protect the organization.
Economics and security benefits drive organizations to adopt Azure AD, but full adoption and compliance is more likely if users benefit too. We recently implemented a similar project for Southland Industries, and their employees were thrilled.
“User experience is front and center of everything we focus on. Our employees can now access our 3rd party helpdesk application in the same Office 365 App Launcher that they use to access their Office 365 productivity applications. The mobile experience is also fantastic, with single sign-on from Intune-managed mobile devices.” - Josh Pickett, IT Manager, Networking and Security at Southland Industries. “With Patriot’s help, we were able to implement strong conditional access rules to limit access to our 3rd party SAML applications. This is one of the primary reasons why we switched from a competitor to Azure AD.”
I hope you find Joe’s story as valuable as I did. Now check out the Voice of the Customer series for more real-world experiences with Microsoft 365 Identity and Access solutions.
Leverage our partners for help with an implementation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.