This section provides the prerequisites for onboarding an Azure application to Britive as well as those for checking in or checking out profiles after onboarding the application.
1. Onboarding Prerequisites
The onboarding prerequisites include getting the required accounts and accesses and performing specific configurations in Azure, as explained in the following sections.
1.1 Accounts and Access
You must have the following accounts and accesses before onboarding an Azure application to Britive:
- Active Azure account
- Administrator access to Azure account
- Active Britive tenant account
- Administrator access to Britive account
1.2 Prerequisite Configurations in Azure
Before onboarding an Azure application in Britive, you must perform the prerequisite configurations in Azure. As mentioned in the introduction of this guide, you can configure the onboarded Azure application for discovery and visibility as well as dynamic permissioning.
The following common prerequisites apply to both discovery and visibility as well as dynamic permissioning:
1.2.1 Prerequisites for discovery and visibility
The prerequisites for discovery and visibility functionalities are given below. Though the prerequisites look similar for discovery and visibility and dynamic permissioning, they are slightly different in terms of configurations.
- Assigning Azure Permissions for discovery and visibility
- Assigning Directory Permissions for discovery and visibility
1.2.2 Prerequisites for dynamic permissioning
The prerequisites for dynamic permissioning include:
- Assigning Azure Permissions for dynamic permissioning
- Assigning Directory Permissions for dynamic permissioning
2. Prerequisites for Check out and Check in of Profiles
Before using the check-out and check-in functionality in Britive for the onboarded Azure application, you need to associate the new IAM role or existing IAM roles in the Azure account with the Britive Identity Provider.
For more information, see Onboarding an Azure Application.