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
An object in Azure AD, like any directory, is a programmatic high-level data construct that represents such things as users, groups, and contacts. When you create a new user or contact in Azure AD, you are creating a new instance of that object. These instances can be differentiated based on their properties.
22
+
# Understand the Azure AD schema
23
+
An object in Azure Active Directory (Azure AD), like any directory, is a programmatic high-level data construct that represents such things as users, groups, and contacts. When you create a new user or contact in Azure AD, you're creating a new instance of that object. These instances can be differentiated based on their properties.
24
24
25
-
Properties, in Azure AD are the elements responsible for storing information about an instance of an object in Azure AD.
25
+
Properties in Azure AD are the elements responsible for storing information about an instance of an object in Azure AD.
26
26
27
-
The Azure AD schema defines the rules for which properties may be used in an entry, the kinds of values that those properties may have, and how users may interact with those values.
27
+
The Azure AD schema defines the rules for which properties might be used in an entry, the kinds of values that those properties might have, and how users might interact with those values.
28
28
29
-
Azure AD has two types of properties. The properties are:
30
-
-**Builtin properties** – Properties that are pre-defined by the Azure AD schema. These properties provide different uses and may or may not be accessible.
31
-
-**Directory extensions** – Properties that are provided so that you can customize Azure AD for your own use. For example, if you have extended your on-premises Active Directory with a certain attribute and want to flow that attribute, you can use one of the custom properties that are provided.
29
+
Azure AD has two types of properties:
30
+
-**Built-in properties**: Properties that are predefined by the Azure AD schema. These properties provide different uses and might or might not be accessible.
31
+
-**Directory extensions**: Properties that are provided so that you can customize Azure AD for your own use. For example, if you've extended your on-premises Active Directory with a certain attribute and want to flow that attribute, you can use one of the custom properties that's provided.
32
32
33
33
## Attributes and expressions
34
-
When an object, such as a user is provisioned to Azure AD, a new instance of the user object is created. This creation includes the properties of that object, which are also known as attributes. Initially, the newly created object will have its attributes set to values that are determined by the synchronization rules. These attributes are then kept up to date via the cloud provisioning agent.
34
+
When an object such as a user is provisioned to Azure AD, a new instance of the user object is created. This creation includes the properties of that object, which are also known as attributes. Initially, the newly created object has its attributes set to values that are determined by the synchronization rules. These attributes are then kept up to date via the cloud provisioning agent.
For example, if a user is part of the Marketing department, their Azure AD department attribute will initially be created when they are provisioned and then the value would be set to Marketing. But then, six months later, they change to Sales. Their on-premises AD department attribute is changed to Sales. This change will then synchronize to Azure AD and be reflected on their Azure AD user object.
38
+
For example, a user might be part of a Marketing department. Their Azure AD department attribute is initially created when they're provisioned, and the value is set to Marketing. Six months later if they change to Sales, their on-premises Active Directory department attribute is changed to Sales. This change synchronizes to Azure AD and is reflected in their Azure AD user object.
39
39
40
-
Attribute synchronization may be either direct, where the value in Azure AD is directly set to the value of the on-premises attribute. Or, there may be a programmatic expression that handles this synchronization. A programmatic expression would be needed in cases where some logic or a determination needed to be made in order to populate the value.
40
+
Attribute synchronization might be direct, where the value in Azure AD is directly set to the value of the on-premises attribute. Or, a programmatic expression might handle the synchronization. A programmatic expression is needed in cases where some logic or a determination must be made to populate the value.
41
41
42
-
For example, if I had my mail attribute ("[email protected]") and I needed to strip out the "@contoso.com" portion and flow just the value "john.smith" I would use something like this:
42
+
For example, if you had the mail attribute "[email protected]" and needed to strip out the "@contoso.com" portion and flow only the value "john.smith," you'd use something like this:
For additional information, on writing custom expressions, and the syntax see [Writing Expressions for Attribute Mappings in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/functions-for-customizing-application-data).
51
+
For more information on how to write custom expressions and the syntax, see [Writing expressions for attribute mappings in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/functions-for-customizing-application-data).
52
52
53
-
The following list are common attributes and how they are synchronized to Azure AD.
53
+
The following table lists common attributes and how they're synchronized to Azure AD.
54
54
55
55
56
-
|On-premises Active Directory|Mapping Type|Azure AD|
56
+
|On-premises Active Directory|Mapping type|Azure AD|
57
57
|-----|-----|-----|
58
58
|cn|Direct|commonName
59
59
|countryCode|Direct|countryCode|
@@ -63,14 +63,14 @@ The following list are common attributes and how they are synchronized to Azure
63
63
|userprincipalName|Direct|userPrincipalName|
64
64
|ProxyAdress|Direct|ProxyAddress|
65
65
66
-
## Viewing the schema
67
-
In order to view the schema and verify it, do the following steps:
66
+
## View the schema
67
+
To view the schema and verify it, follow these steps.
68
68
69
-
1.Navigate to [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
70
-
2. Sign in with your global administrator account
71
-
3. On the left, click**modify permissions** and ensure that **Directory.ReadWrite.All** is Consented.
72
-
4. Run the following query:https://graph.microsoft.com/beta/serviceprincipals/. This query will return a list of service principals.
73
-
5. Locate "appDisplayName": "Active Directory to Azure Active Directory Provisioning" and note the "id:" value.
69
+
1.Go to [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer).
70
+
1. Sign in with your global administrator account.
71
+
1. On the left, select**modify permissions** and ensure that **Directory.ReadWrite.All** is *Consented*.
72
+
1. Run the query https://graph.microsoft.com/beta/serviceprincipals/. This query returns a list of service principals.
73
+
1. Locate `"appDisplayName": "Active Directory to Azure Active Directory Provisioning"` and note the value for `"id"`.
74
74
```
75
75
"value": [
76
76
{
@@ -143,8 +143,8 @@ In order to view the schema and verify it, do the following steps:
143
143
"passwordCredentials": []
144
144
},
145
145
```
146
-
6. Replace the {Service Principal id} with your value and run the following query: `https://graph.microsoft.com/beta/serviceprincipals/{Service Principal id}/synchronization/jobs/`
147
-
7. Locate the "id": "AD2AADProvisioning.fd1c9b9e8077402c8bc03a7186c8f976" section and note the "id:".
146
+
1. Replace `{Service Principal id}` with your value, and run the query `https://graph.microsoft.com/beta/serviceprincipals/{Service Principal id}/synchronization/jobs/`.
147
+
1. Locate `"id": "AD2AADProvisioning.fd1c9b9e8077402c8bc03a7186c8f976"` and note the value for `"id"`.
@@ -235,16 +235,17 @@ In order to view the schema and verify it, do the following steps:
235
235
]
236
236
}
237
237
```
238
-
8. Now run the following query: `https://graph.microsoft.com/beta/serviceprincipals/{Service Principal Id}/synchronization/jobs/{AD2AAD Provisioning id}/schema`
238
+
1. Now run the query `https://graph.microsoft.com/beta/serviceprincipals/{Service Principal Id}/synchronization/jobs/{AD2AAD Provisioning id}/schema`.
# Azure AD Connect cloud provisioning agent: Automatic upgrade
21
21
22
-
Making sure your Azure AD Connect cloud provisioning agent installation is always up to date has never been easier with the **automatic upgrade** feature. This feature is enabled by default and cannot be disabled.
22
+
Making sure your Azure Active Directory (Azure AD) Connect cloud provisioning agent installation is always up to date is easy with the automatic upgrade feature. This feature is enabled by default and can't be disabled.
23
23
24
-
The agent is installed here: **"Program files\Azure AD Connect Provisioning Agent\AADConnectProvisioningAgent.exe"**
24
+
The agent is installed here: "Program files\Azure AD Connect Provisioning Agent\AADConnectProvisioningAgent.exe"
25
25
26
-
You can verify your version by right-clicking on the executable and selecting properties and then details.
26
+
To verify your version, right-click the executable and select properties and then details.
Copy file name to clipboardExpand all lines: articles/active-directory/cloud-provisioning/how-to-configure.md
+52-43Lines changed: 52 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: 'Azure AD Connect cloud provisioning new agent configuration'
3
-
description: This topic describes how to install cloud provisioning.
3
+
description: This article describes how to install cloud provisioning.
4
4
services: active-directory
5
5
author: billmath
6
6
manager: daveba
@@ -13,67 +13,76 @@ ms.author: billmath
13
13
ms.collection: M365-identity-device-management
14
14
---
15
15
16
-
# Azure AD Connect cloud provisioning new configuration
16
+
# Azure AD Connect cloud provisioning new agent configuration
17
17
18
-
Once you have installed the agent, you need to sign-in to the Azure portal and configure provisioning. Use the following steps to enable the agent.
18
+
After you've installed the agent, you need to signin to the Azure portal and configure Azure Active Directory (Azure AD) Connect cloud provisioning. Follow these steps to enable the agent.
19
19
20
20
## Configure provisioning
21
-
To configure provisioning, use the following steps:
21
+
To configure provisioning, follow these steps.
22
22
23
-
1. In the Azure AD portal, click **Azure Active Directory**
24
-
2. Click **Azure AD Connect**
25
-
3. Select **Manage provisioning (Preview)**
26
-
23
+
1. In the Azure portal, select **Azure Active Directory**.
24
+
1. Select **Azure AD Connect**.
25
+
1. Select **Manage provisioning (Preview)**.
27
26
28
-
4. Click on **New configuration**.
29
-
5. On the configuration screen, the on-premises domain is pre-populated
30
-
6. Enter a **Notification email**. This email will be notified when provisioning is not healthy.
31
-
8. Move the selector to **Enable** and click **Save**.
## Scoping provisioning to specific users and groups
35
-
If you want to scope the agent to only synchronize specific users and groups, you can do this. You can scope using on-premises AD groups or Organizational Units. You cannot configure groups and Organizational Units within a configuration.
29
+
1. Select **New configuration**.
30
+
1. On the configuration screen, the on-premises domain is prepopulated.
31
+
1. Enter a **Notification email**. This email will be notified when provisioning isn't healthy.
32
+
1. Move the selector to **Enable**, and select **Save**.
36
33
37
-
1. In the Azure AD portal, click **Azure Active Directory**
38
-
2. Click **Azure AD Connect**
39
-
3. Select **Manage provisioning (Preview)**
40
-
4. Under **Configuration** click on your configuration.
41
-
34
+
42
35
43
-
5. Under **Configure**, select **All users** to change the scope of the configuration rule.
44
-
36
+
## Scope provisioning to specific users and groups
37
+
You can scope the agent to synchronize specific users and groups by using on-premises Active Directory groups or organizational units. You can't configure groups and organizational units within a configuration.
45
38
46
-
6. On the right, you can change the scope to include only security groups by entering the distinguished name of the group and clicking **Add**.
47
-
39
+
1. In the Azure portal, select **Azure Active Directory**.
40
+
1. Select **Azure AD Connect**.
41
+
1. Select **Manage provisioning (Preview)**.
42
+
1. Under **Configuration**, select your configuration.
48
43
49
-
7. Or change it to include only specific OUs. Click **Done** and **Save**.
0 commit comments