You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/roles/custom-assign-powershell.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.workload: identity
9
9
ms.subservice: roles
10
10
ms.topic: how-to
11
-
ms.date: 09/07/2021
11
+
ms.date: 05/10/2022
12
12
ms.author: rolyon
13
13
ms.reviewer: vincesm
14
14
ms.custom: it-pro
@@ -52,7 +52,7 @@ To assign the role to a service principal instead of a user, use the [Get-AzureA
52
52
53
53
## Role definitions
54
54
55
-
Role definition objects contain the definition of the built-in or custom role, along with the permissions that are granted by that role assignment. This resource displays both custom role definitions and built-in directory roles (which are displayed in roleDefinition equivalent form). Today, an Azure AD organization can have a maximum of 30 unique custom role definitions defined.
55
+
Role definition objects contain the definition of the built-in or custom role, along with the permissions that are granted by that role assignment. This resource displays both custom role definitions and built-in directory roles (which are displayed in roleDefinition equivalent form). For information about the maximum number of custom roles that can be created in an Azure AD organization, see [Azure AD service limits and restrictions](../enterprise-users/directory-service-limits-restrictions.md).
1. Select **Sync users from Microsoft Azure** and click **Next**.
58
+
3. Select **Sync users from Microsoft Azure** and click **Next**.
59
59
60
60
61
61
62
-
1. Copy and save the **Tenant URL** and the **Secret token**. These values will be entered in the **Tenant URL** and **Secret Token** fields in the Provisioning tab of your Adobe Identity Management application in the Azure portal.
62
+
4. Copy and save the **Tenant URL** and the **Secret token**. These values will be entered in the **Tenant URL** and **Secret Token** fields in the Provisioning tab of your Adobe Identity Management application in the Azure portal.
@@ -80,68 +80,71 @@ The Azure AD provisioning service allows you to scope who will be provisioned ba
80
80
81
81
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
1. Under the **Admin Credentials** section, input your Adobe Identity Management Tenant URL and Secret Token retrieved earlier from Step 2. Click **Test Connection** to ensure Azure AD can connect to Adobe Identity Management. If the connection fails, ensure your Adobe Identity Management account has Admin permissions and try again.
104
+
5. Under the **Admin Credentials** section, input your Adobe Identity Management Tenant URL and Secret Token retrieved earlier from Step 2. Click **Test Connection** to ensure Azure AD can connect to Adobe Identity Management. If the connection fails, ensure your Adobe Identity Management account has Admin permissions and try again.
1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
108
+
6. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Adobe Identity Management**.
114
+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Adobe Identity Management**.
112
115
113
-
1. Review the user attributes that are synchronized from Azure AD to Adobe Identity Management in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Adobe Identity Management for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Adobe Identity Management API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
116
+
9. Review the user attributes that are synchronized from Azure AD to Adobe Identity Management in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Adobe Identity Management for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Adobe Identity Management API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
114
117
115
-
|Attribute|Type|Supported for filtering|Required by Adobe Identity Management
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Adobe Identity Management**.
128
+
10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Adobe Identity Management**.
126
129
127
-
1. Review the group attributes that are synchronized from Azure AD to Adobe Identity Management in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Adobe Identity Management for update operations. Select the **Save** button to commit any changes.
130
+
11. Review the group attributes that are synchronized from Azure AD to Adobe Identity Management in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Adobe Identity Management for update operations. Select the **Save** button to commit any changes.
128
131
129
-
|Attribute|Type|Supported for filtering|Required by Adobe Identity Management
130
-
|---|---|---|---|
131
-
|displayName|String|✓|✓
132
-
|members|Reference||
132
+
|Attribute|Type|
133
+
|---|---|
134
+
|displayName|String|
135
+
|members|Reference|
133
136
134
-
1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
137
+
12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
135
138
136
-
1. To enable the Azure AD provisioning service for Adobe Identity Management, change the **Provisioning Status** to **On** in the **Settings** section.
139
+
13. To enable the Azure AD provisioning service for Adobe Identity Management, change the **Provisioning Status** to **On** in the **Settings** section.
137
140
138
141
139
142
140
-
1. Define the users and/or groups that you would like to provision to Adobe Identity Management by choosing the desired values in **Scope** in the **Settings** section.
143
+
14. Define the users and/or groups that you would like to provision to Adobe Identity Management by choosing the desired values in **Scope** in the **Settings** section.
@@ -150,11 +153,11 @@ This operation starts the initial synchronization cycle of all users and groups
150
153
## Step 6. Monitor your deployment
151
154
Once you've configured provisioning, use the following resources to monitor your deployment:
152
155
153
-
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
154
-
* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
155
-
* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
156
+
1. Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
157
+
2. Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
158
+
3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
156
159
157
-
## More resources
160
+
## Additional resources
158
161
159
162
*[Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
160
163
*[What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
Copy file name to clipboardExpand all lines: articles/azure-arc/servers/manage-agent.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Managing the Azure Arc-enabled servers agent
3
3
description: This article describes the different management tasks that you will typically perform during the lifecycle of the Azure Connected Machine agent.
4
-
ms.date: 04/15/2022
4
+
ms.date: 05/11/2022
5
5
ms.topic: conceptual
6
6
---
7
7
@@ -69,7 +69,7 @@ This parameter specifies a resource in Azure Resource Manager to delete from Azu
69
69
70
70
To disconnect using a service principal, run the following command:
0 commit comments