Skip to content

Commit 9cb2dba

Browse files
Merge pull request #226067 from billmath/fixes3
updating
2 parents 47fbda9 + b1b662d commit 9cb2dba

File tree

1 file changed

+5
-42
lines changed

1 file changed

+5
-42
lines changed

articles/active-directory/cloud-sync/how-to-prerequisites.md

Lines changed: 5 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You need the following to use Azure AD Connect cloud sync:
2626
- On-premises firewall configurations.
2727

2828
## Group Managed Service Accounts
29-
A group Managed Service Account is a managed domain account that provides automatic password management, simplified service principal name (SPN) management,the ability to delegate the management to other administrators, and also extends this functionality over multiple servers. Azure AD Connect Cloud Sync supports and uses a gMSA for running the agent. You will be prompted for administrative credentials during setup, in order to create this account. The account will appear as (domain\provAgentgMSA$). For more information on a gMSA, see [Group Managed Service Accounts](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)
29+
A group Managed Service Account is a managed domain account that provides automatic password management, simplified service principal name (SPN) management, the ability to delegate the management to other administrators, and also extends this functionality over multiple servers. Azure AD Connect Cloud Sync supports and uses a gMSA for running the agent. You will be prompted for administrative credentials during setup, in order to create this account. The account will appear as (domain\provAgentgMSA$). For more information on a gMSA, see [group Managed Service Accounts](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)
3030

3131
### Prerequisites for gMSA:
3232
1. The Active Directory schema in the gMSA domain's forest needs to be updated to Windows Server 2012 or later.
@@ -48,46 +48,9 @@ If you are creating a custom gMSA account, you need to ensure that the account h
4848
|Allow |gMSA Account |Read all properties |Descendant Contact objects|
4949
|Allow |gMSA Account |Create/delete User objects|This object and all descendant objects|
5050

51-
For steps on how to upgrade an existing agent to use a gMSA account see [Group Managed Service Accounts](how-to-install.md#group-managed-service-accounts).
52-
53-
#### Create gMSA account with PowerShell
54-
You can use the following PowerShell script to create a custom gMSA account. Then you can use the [cloud sync gMSA cmdlets](how-to-gmsa-cmdlets.md) to apply more granular permissions.
55-
56-
```powershell
57-
# Filename: 1_SetupgMSA.ps1
58-
# Description: Creates and installs a custom gMSA account for use with Azure AD Connect cloud sync.
59-
#
60-
# DISCLAIMER:
61-
# Copyright (c) Microsoft Corporation. All rights reserved. This
62-
# script is made available to you without any express, implied or
63-
# statutory warranty, not even the implied warranty of
64-
# merchantability or fitness for a particular purpose, or the
65-
# warranty of title or non-infringement. The entire risk of the
66-
# use or the results from the use of this script remains with you.
67-
#
68-
#
69-
#
70-
#
71-
# Declare variables
72-
$Name = 'provAPP1gMSA'
73-
$Description = "Azure AD Cloud Sync service account for APP1 server"
74-
$Server = "APP1.contoso.com"
75-
$Principal = Get-ADGroup 'Domain Computers'
76-
77-
# Create service account in Active Directory
78-
New-ADServiceAccount -Name $Name `
79-
-Description $Description `
80-
-DNSHostName $Server `
81-
-ManagedPasswordIntervalInDays 30 `
82-
-PrincipalsAllowedToRetrieveManagedPassword $Principal `
83-
-Enabled $True `
84-
-PassThru
85-
86-
# Install the new service account on Azure AD Cloud Sync server
87-
Install-ADServiceAccount -Identity $Name
88-
```
89-
90-
For additional information on the cmdlets above, see [Getting Started with Group Managed Service Accounts](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj128431(v=ws.11)?redirectedfrom=MSDN).
51+
For steps on how to upgrade an existing agent to use a gMSA account see [group Managed Service Accounts](how-to-install.md#group-managed-service-accounts).
52+
53+
For more information on how to prepare your Active Directory for group Managed Service Account, see [group Managed Service Accounts Overview](/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview).
9154

9255
### In the Azure Active Directory admin center
9356

@@ -104,7 +67,7 @@ Run the [IdFix tool](/office365/enterprise/prepare-directory-attributes-for-sync
10467

10568
2. The PowerShell execution policy on the local server must be set to Undefined or RemoteSigned.
10669

107-
3. If there's a firewall between your servers and Azure AD, configure see [Firewall and proxy requirements](#firewall-and-proxy-requirements) below.
70+
3. If there's a firewall between your servers and Azure AD, see [Firewall and proxy requirements](#firewall-and-proxy-requirements) below.
10871

10972
>[!NOTE]
11073
> Installing the cloud provisioning agent on Windows Server Core is not supported.

0 commit comments

Comments
 (0)