To manage an Azure cloud system environment in One Identity Manager, the following basic data is relevant.
Target system managers
A default application role exists for the target system manager in One Identity Manager. Assign the employees who are authorized to read all Azure related objects and the Active directory User, Group and Service Principal objects for the Azure Active Directory tenants in One Identity Manager to this application role. Define additional application roles if you want to limit the edit or view permissions for target system managers to individual tenants. The application roles must be added under the default application role.
For more information about implementing and editing application roles, see the One Identity Manager Authorization and Authentication Guide.
Implementing application roles for target system managers
- The One Identity Manager administrator assigns employees to be target system managers.
- These target system managers add employees to the default application role for target system managers. Target system managers with the default application role are authorized to edit all tenants in One Identity Manager.
- Target system managers can authorize other employees within their area of responsibility as target system managers and if necessary, create additional child application roles and assign these to individual connections.
Default Application Roles for Target System Managers
Table 12: Default Application Roles for Target System Managers
|
Users |
Tasks |
|
Target system managers |
Target system managers must be assigned to Target systems | Azure Cloud Access Governance or a sub-application role. Users with this application role:
Assume administrative tasks for the target system.
-
Read objects like user accounts, groups, service principals, Management groups, subscriptions, resource groups, resource, roles and role assignments.
-
Configure synchronization in the Synchronization Editor and defines the mapping for comparing target systems and One Identity Manager.
-
Edit the synchronization's target system types and outstanding objects.
-
Authorize other employees within their area of responsibility as target system managers and create child application roles if required. |
To initially specify employees to be target system administrators
-
Log in to One Identity Manager as Manager administrator (Base role | Administrators).
-
Select One Identity Manager Administration | Target systems | Administrators.
-
Select Assign employees.
To add the first employees to the default application as target system managers
-
Log into One Identity Manager as Target System Administrator (Target systems | Administrators).
-
Select One Identity Manager Administration | Target systems | Azure Cloud Access Governance.
-
Select Assign employees in the Task view.
-
Assign the employees you want and save the changes.
To authorize other employees as target system managers when you are a target system manager
-
Log into One Identity Manager as target system manager.
-
Select the application role in Azure Cloud Access Governance | Basic configuration data | Target system managers.
-
Select Assign employees.
-
Assign the employees you want and save the changes.
To specify target system managers for individual clients
-
Log into One Identity Manager as target system manager.
-
Select Azure Cloud Access Governance | Tenants.
-
Select the client from the result list.
-
Select Change master data.
-
On the General tab, select the application role in the Azure Cloud System manager field.
NOTE: In case the Azure Cloud Target System Manager field is not present, install the AAD.Forms.vif refer to KB article (CIM Enhancement for AAD Module).
-
Next to the Target system manager menu, click to create a new application role.
-
Enter the application role name and assign the Target systems | Azure Cloud Access Governance parent application role.
-
Click OK to add the new application role.
-
Save the changes.
-
Assign employees to this application role who are permitted to edit the client in One Identity Manager.
You must provide details about your organization the first time you register for a Microsoft cloud service. This detailed information is used to make a new Azure Active Directory partition. The organization represents one Azure Active Directory tenant. In One Identity Manager, you can edit the main data of each Azure Active Directory tenant.
However, you cannot create new Azure Active Directory tenants in One Identity Manager.
General Master Data for Microsoft Azure Connection
To edit CIM Target system manager for Azure Active Directory tenant data
-
In the Manager, select the Azure Active Directory > Tenants category.
-
In the result list, select the Azure Active Directory tenant.
-
Select the Change main data task.
-
Edit the Azure Cloud Target System Manager field for Azure Active Directory tenant.
-
Save the changes.
Detailed information about this topic
More details can be found in Azure Active Directory Synchronization Admin Guide
The following are the Azure objects that are synchronized from the target azure tenant.
Azure Scope Objects
Root Scope(/)
RootScope is the top most level scope above the management group. If the user's access is elevated, the user is assigned the User Access Administrator role in Azure at root scope (/). All role assignments defined at the rootscope will be inherited at all levels below. Role assignments at the rootscope can be defined using Azure PowerShell, Azure CLI, or the REST API.
Management Group
Management Groups provide a scope above Subscriptions. All Subscriptions within a Management Group inherit conditions applied at the management group. Governance policies can be applied to Management Group so that Subscriptions inherit it. By default, all Azure Tenants automatically have a Root Management Group created.
Each directory is given a single top-level management group called the root management group. The root management group is built into the hierarchy to have all management groups and subscriptions fold up to it.
Azure management groups support Azure role-based access control for all resource accesses and role definitions. These permissions are inherited to child resources that exist in the hierarchy.
Subscription
Azure Subscriptions are the container that hosts all Azure Resources. It is the Resource access and billing boundary
Resource Groups
Azure Resource Group is a container that holds the related resources needed for a particular solution. Resource Groups are created under an Azure Subscription.
The resource group stores metadata about the resources. Therefore, when you specify a location for the resource group, you are specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
Resources
Azure Resource is the entity such as virtual machine that is managed by Azure.
These are the building blocks of an Azure IT environment. The resources are organized into Resource Groups inside of an Azure subscription. There are billable and non-billable resources. Billable resources have a Meter attached to them that runs while the resource is provisioned.
Roles
Azure Roles is a collection of permissions and defines the following:
-
List of Actions that can be performed the Resource
-
List of Actions that are excluded from the allowed list of Actions
-
List of Actions that can be performed on the underlying data
-
List of Actions that are excluded from the allowed list of data actions
Role definitions are created at a particular scope (Management Group / Subscriptions / Resource Group) and can be assigned to AAD Users / AAD Service Principal / AAD Managed Identities at the scope at which Role was created or at a child scope level. Example: The Built in Owner role was created at the Root Management Scope level. This role can be assigned to an AADUser at the Management scope level or at a child scope level such as Subscription or Resource.
Built in Roles
Built in Roles are created by Azure at Root Management Group Scope and cannot be modified.
Custom Roles
Custom Roles can be created and assigned multiple scopes at Management Group / Subscriptions / Resource Group level.
Locations / Regions
Azure Regions contain the Azure Data Centers. When a Resource Group / Resource is created we select the Azure Region where the resource is created, and its data resides
Resource Types
Azure Resource Provider is a service that supplies resources. Example Microsoft.Compute. Resource Types are resources available through the Resource Provider. Example VMs. Each Resource Type is available for deployment on certain regions. The API lists the regions on which a particular Resource Type is available for deployment.
Role Assignments
Built in Roles and Custom Roles can be assigned to AAD User, AAD Service Principal, AAD Group and Managed Identities at various scopes. The roles are also inherited based on scope hierarchy.
Role assignment to Security Principals helps you to manage access to Azure resources. To grant access, you assign roles to users, groups, service principals at a particular scope.
You can assign and remove roles from a security principal in One Identity Manager, which can be provided to target system by provisioning.
To add role assignment to a user, group, service principal or managed identity, you can assign the role directly or it can be added indirectly through the IT Shop.
