Chapter 11.  Managing Transition Scenarios with Special Scenarios

This chapter closes the basic hybrid identity and access management scenario. We will discuss additional important points that will help you to build the transition processes, including multi-forest and pure-cloud considerations. Furthermore, we will provide you with different capabilities for several availability scenarios and connection types to the Azure infrastructure. Additionally, a Service Provider example architecture will be part of the chapter. With this information and your knowledge of the previous chapters, you should be able to identify the right strategy to decide the correct direction for your coming projects.

In this chapter, we will cover the following:

• Identifying special Active Directory and ADFS considerations

• Planning the correct connectivity to your Azure infrastructure

• Integrating Azure MFA in your MIM 2016 deployment

• Knowing the migration from AD RMS to Azure RMS shortcut

Identifying special Active Directory and ADFS considerations

In this section, we will provide three special scenarios we always encounter in our daily business. We have had the chance to help many service providers to build up their modern, on-premise service provider model. In this time, we have always had the same questions about integrating Azure Identity and Access Management services into their portfolio. We will try to give you a short overview about this topic as well. The section is divided into three main points chosen from the most frequently asked questions. Hopefully, we will also cover at least one of yours!

The most common questions cover the following:

• Single Forest scenario with multiple Azure AD tenants

• Extending your resource access to external partners (on-premise)

• Modern Service Provider architectures and Azure IdAM integrations

Single Forest scenario with multiple Azure AD tenants

In recent months, we have had several discussions about using a single forest environment with...

Planning the correct connectivity to your Azure infrastructure

With the extension of your current infrastructure to the Azure services, you need to think about the topic of connectivity. Azure provides and supports three types of connection, two server, and one client-focused option. A server connection is always between your current network infrastructure and Azure virtual networks. The three connection types are as follows:

• Site-to-Site VPN (server-focused)

• Express Route (server-focused)

• Point-to-Site (client-focused)

Generally, we can use the following principles to use the different types:

• Use a Site-to-Site connection when:

  • Building hybrid solutions

  • Connections need to be persistent and without client-side configuration

• Use a Point-to-Site connection when the following apply:

  • Configuration of a few clients that need to access the virtual network

  • Administrative remote access

  • Combinations of S2S connections with small groups of single clients (small branches)

  • You have a VPN device that doesn't match...

Integrating Azure MFA in your MIM 2016 deployment

With the release of Microsoft Identity Manager 2016, we have begun to migrate our existing customer Forefront Identity Manager deployments and build new projects directly with the new version. One option that gives you a lot of flexibility is the integration of Azure MFA with the Password Reset and Account Unlock feature of MIM 2016. The benefits are as follows:

• If you only use the One-time password email or the Q&A gate nothing, if you want to stay on these methods

• If you use the One-time password SMS gate, you will get more flexibility and a native integration in your 2FA-solution if you move to Azure MFA

• You can also use Azure MFA for approvals in Authorization Workflows. You can find out more by visiting the following link: http://bit.ly/23h02Bk

The following process shows the flow of the password reset process that can be initiated through the Windows Logon UI and the Login Assistant (SSLA) Portal. You have the ability to use different...

Knowing the migrate from AD RMS to Azure RMS shortcut

With the new Azure RMS capabilities, we have several customers who want to migrate their AD RMS infrastructure to Azure RMS. Microsoft provides a high-level plan for the migration process, which includes the following 10 points:

1. Prepare your toolset:

   • Azure Rights Management Administration Tool: http://bit.ly/1SBEM6q

   • BYOK toolset: http://bit.ly/1SE8OYA

2. Export the configuration data of the on-premise AD RMS infrastructure.

3. Prepare the Azure RMS infrastructure for your organization.

4. Migrate the key material and policies to the Azure RMS configuration.

5. Activate Azure RMS.

6. Remove your Service Connection Point information.

7. Relocate the RMS-enabled clients to Azure RMS.

8. Reconfigure on-premise services such as file servers, SharePoint, and Exchange to use the RMS Connector.

9. Decommission the on-premise RMS infrastructure.

10. This is a good chance to renew keys after the migration process.

This small list is just a hint with the most important information in...

Summary

After reading this and the previous chapters, you should be able to describe the correct design and consolidation steps for a basic hybrid identity and access management solution with a concrete project direction. You will also be able to provide a solid recommendation to the management and IT department of the company. Also, you should know to address relevant changes and shifts to the current architecture.

In the following chapters, we focus on complex identity and access management considerations and tasks. Ready to go?