Integrating applications into Azure AD
In this, we will understand the process of integrating applications with Azure Active Directory (AD). You’ll also learn about several inventories that might assist you with your application integration process. So, let’s begin.
Taking inventory
Before integrating apps with Azure AD, you need the first to figure out where you want to go. The questions below will assist you in planning your Azure AD application integration project.
Application inventory
- Where are all of your applications? Who owns them?
- What kind of authentication do your applications require?
- Who needs access to which applications?
- Do you want to deploy a new application?
User and group inventory
Where do your user accounts reside?
- On-premises Active Directory
- Azure AD
- Within a separate application database that you own
- In unsanctioned applications
- All of the above
What kind of permissions and roles do each users have? Is it essential to go through their permissions again? Or are you certain that your current user access and role assignments are adequate?
Are groups already established in your on-premises Active Directory?
- How are your groups organized?
- Who are the group members?
- What permissions/role assignments do the groups currently have?
Does it require cleaning up user/group databases before integrating?
Access management inventory
- How do you manage user access to applications?
- Is there any other ways for managing access, such as with RBAC for example?
- Who needs access to what?
However, it can be possible that you don’t have the answers to all of these questions upfront but that’s okay. But, within this tutorial, you will get answer to some of those questions and make some informed decisions.
Finding unsanctioned cloud applications with Cloud Discovery
As previously stated, there may be applications for which your company has not yet taken responsibility. Unauthorized cloud apps can thus be discovered as part of the inventory process.
Integrating applications with Azure AD
The article belows provides the different ways for integrating applications with Azure AD, and provides some guidance.
- Firstly, determining which Active Directory to use
- Secondly, using applications in the Azure application gallery
- Lastly, integrating SaaS applications tutorials list
Authentication Types
Authentication needs for each of your applications may differ. Signing certificates, on the other hand, maybe used with apps that employ the SAML 2.0, WS-Federation, or OpenID Connect protocols, as well as Password Single Sign On, in Azure AD.
Enabling SSO with Azure AD App Proxy
Using Microsoft Azure AD Application Proxy, you can securely provide access to apps on your private network from anywhere. However, after you’ve deployed an application proxy connector in your environment, configuring it with Azure AD is simple.
Integrating custom applications
- Firstly, if you are writing a new application and want to assist developers in leveraging the power of Azure AD then, Guiding developers can be helpful.
- Secondly, if you want to add your custom application to the Azure Application Gallery then check “Bring your own app” with Azure AD Self-Service SAML configuration.
Reference: Microsoft Documentation