Skip to content

Commit 6cdf10e

Browse files
committed
updating
1 parent 638779f commit 6cdf10e

File tree

4 files changed

+12
-13
lines changed

4 files changed

+12
-13
lines changed

articles/active-directory/hybrid/how-to-connect-group-writeback-disable.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Disable Group Writeback in Azure AD Connect'
2+
title: 'Disable group writeback in Azure AD Connect'
33
description: This article describes how to disable Group Writeback in Azure AD Connect.
44
services: active-directory
55
author: billmath
@@ -15,8 +15,7 @@ ms.collection: M365-identity-device-management
1515
---
1616

1717
# Disabling group writeback
18-
19-
To disable group writeback for your organization, use the following steps:
18+
The following document will walk you thorough disabling group writeback. To disable group writeback for your organization, use the following steps:
2019

2120
1. Launch the Azure Active Directory Connect wizard and navigate to the Additional Tasks page. Select the Customize synchronization options task and click next.
2221
2. On the Optional Features page, uncheck group writeback. You'll receive a warning letting you know that groups will be deleted. Click Yes.

articles/active-directory/hybrid/how-to-connect-group-writeback-enable.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ If the original version of group writeback was not previously enabled, continue
8282
8383
8484
85-
## Optional Configuration
85+
## Optional configuration
8686
8787
To make it easier to find groups being written back from Azure AD to Active Directory, there's an option to write back the group distinguished name with the cloud display name.
8888
@@ -95,9 +95,9 @@ CN=Administrators_e9305786a271, OU=WritebackContainer, DC=domain, DC=com 
9595
When configuring group writeback, there will be a checkbox at the bottom of the Group Writeback configuration window. Select the box to enable this feature.
9696
9797
>[!NOTE]
98-
>Groups being written back from Azure AD to AD will have a source of authority of the cloud. >This means any changes made on-premises to groups that are written back from Azure AD will be overwritten on the next sync cycle.
98+
>Groups being written back from Azure AD to AD will have a source of authority of the cloud. This means any changes made on-premises to groups that are written back from Azure AD will be overwritten on the next sync cycle.
9999
100-
## Next Steps:
100+
## Next steps:
101101
102102
- [Azure AD Connect group writeback](how-to-connect-group-writeback-v2.md)
103103
- [Modify Azure AD Connect group writeback default behavior](how-to-connect-modify-group-writeback.md)

articles/active-directory/hybrid/how-to-connect-group-writeback-v2.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following document will walk you through what you need to know before you en
4040

4141

4242

43-
## Plan Your Implementation
43+
## Plan your implementation
4444
There are a few activities that you'll want to complete before enabling the latest public preview of group writeback. These activities include discovering your current configuration, verifying the prerequisites, and choosing the deployment approach.
4545

4646
## Discovery
@@ -99,7 +99,7 @@ You can also use the PowerShell cmdlet [AzureADDirectorySetting](https://docs.mi
9999
### Discover if AD has been prepared for Exchange
100100
To verify if Active Directory has been prepared for Exchange, see [Prepare Active Directory and domains for Exchange Server, Active Directory Exchange Server, Exchange Server Active Directory, Exchange 2019 Active Directory](https://docs.microsoft.com/Exchange/plan-and-deploy/prepare-ad-and-domains?view=exchserver-2019#how-do-you-know-this-worked)
101101

102-
## Public Preview Prerequisites
102+
## Public preview prerequisites
103103
The following are prerequisites for group writeback.
104104

105105
- An Azure AD Premium 1 license
@@ -122,7 +122,7 @@ To keep the default behavior, continue to the [enable group writeback](how-to-co
122122
The default behavior can be modified as follows:
123123

124124
- Only groups that are configured for write-back will be written back, including newly created Microsoft 365 groups.
125-
- Groups that are written to on prem will be deleted in AD when they're either disabled for group writeback, soft deleted, or hard deleted in Azure AD.
125+
- Groups that are written to on-premises will be deleted in AD when they're either disabled for group writeback, soft deleted, or hard deleted in Azure AD.
126126
- Microsoft 365 groups with up to 250,000 members can be written back to on-premises.
127127

128128
If you plan to make changes to the default behavior, we recommend that you do so prior to enabling group writeback. However, you can still modify the default behavior, if group writeback is already enabled. To modify the default behavior, see [Modifying group writeback](how-to-connect-modify-group-writeback.md).
@@ -143,7 +143,7 @@ While this release has undergone extensive testing, you may still encounter issu
143143

144144

145145

146-
## Next Steps:
146+
## Next steps:
147147

148148
- [Modify Azure AD Connect group writeback default behavior](how-to-connect-modify-group-writeback.md)
149149
- [Enable Azure AD Connect group writeback](how-to-connect-group-writeback-enable.md)

articles/active-directory/hybrid/how-to-connect-modify-group-writeback.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Group writeback is the feature that allows you to write cloud groups back to you
2626

2727
The following document will walk you through deploying the options for modifying the default behaviors of Azure AD Connect group writeback.
2828

29-
## Considerations for Existing Deployments
29+
## Considerations for existing deployments
3030

3131
If the original version of group writeback is already enabled and in use in your environment, then all your Microsoft 365 groups have already been written back to AD. Instead of disabling all Microsoft 365 groups, you'll want to review any use of the previously written back groups, and disable only those that are no longer needed in on-premises AD.
3232

@@ -47,7 +47,7 @@ If the original version of group writeback is already enabled and in use in your
4747
### Disable writeback for each existing Microsoft 365 group.
4848
4949
- Portal: [Entra admin portal](https://docs.microsoft.com/azure/active-directory/enterprise-users/groups-write-back-portal)
50-
- Powershell: [Microsoft Identity Tools PowerShell Module](https://www.powershellgallery.com/packages/MSIdentityTools/2.0.16)
50+
- PowerShell: [Microsoft Identity Tools PowerShell Module](https://www.powershellgallery.com/packages/MSIdentityTools/2.0.16)
5151
Example: `Get-mggroup -filter "groupTypes/any(c:c eq 'Unified')" | Update-MsIdGroupWritebackConfiguration -WriteBackEnabled $false`
5252
- MS Graph: [Update group](https://docs.microsoft.com/graph/api/group-update?view=graph-rest-beta&tabs=http)
5353
@@ -158,7 +158,7 @@ Prior to re-enabling for writeback, or restoring from soft delete in Azure AD, t
158158

159159

160160

161-
## Next Steps:
161+
## Next steps:
162162

163163
- [Azure AD Connect group writeback](how-to-connect-group-writeback-v2.md)
164164
- [Enable Azure AD Connect group writeback](how-to-connect-group-writeback-enable.md) -

0 commit comments

Comments
 (0)