Skip to content

Commit 288d625

Browse files
authored
Merge pull request #8797 from MicrosoftDocs/main
Auto push to live 2025-04-24 18:06:20
2 parents 1695642 + 82290d5 commit 288d625

25 files changed

Lines changed: 66 additions & 1159 deletions

.openpublishing.redirection.developer.json

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6258,6 +6258,66 @@
62586258
{
62596259
"source_path": "support/mem/configmgr/update-management/error-0x800f0831-installing-update.md",
62606260
"redirect_url": "/troubleshoot/windows-server/installing-updates-features-roles/error-0x800f0831-installing-update"
6261+
},
6262+
{
6263+
"source_path": "support/sql/database-engine/database-mirroring/assertion-execute-bulk-insert-bcp.md",
6264+
"redirect_url": "/previous-versions/troubleshoot/sql/database-mirroring/assertion-execute-bulk-insert-bcp"
6265+
},
6266+
{
6267+
"source_path": "support/sql/database-engine/database-mirroring/assertion-partner-servers-using-mirroring.md",
6268+
"redirect_url": "/previous-versions/troubleshoot/sql/database-mirroring/assertion-partner-servers-using-mirroring"
6269+
},
6270+
{
6271+
"source_path": "support/sql/database-engine/backup-restore/asr-agent-vss-backup-fails.md",
6272+
"redirect_url": "/previous-versions/troubleshoot/sql/backup-restore/asr-agent-vss-backup-fails"
6273+
},
6274+
{
6275+
"source_path": "support/sql/database-engine/database-file-operations/transaction-log-file-not-grow.md",
6276+
"redirect_url": "/previous-versions/troubleshoot/sql/database-file-operations/transaction-log-file-not-grow"
6277+
},
6278+
{
6279+
"source_path": "support/sql/database-engine/install/windows/error-change-path-shared-component-directory.md",
6280+
"redirect_url": "/previous-versions/troubleshoot/sql/install/error-change-path-shared-component-directory"
6281+
},
6282+
{
6283+
"source_path": "support/sql/database-engine/install/windows/error-upgrade-cluster-node.md",
6284+
"redirect_url": "/previous-versions/troubleshoot/sql/install/error-upgrade-cluster-node"
6285+
},
6286+
{
6287+
"source_path": "support/sql/database-engine/replication/error-replication-monitor.md",
6288+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/error-replication-monitor"
6289+
},
6290+
{
6291+
"source_path": "support/sql/database-engine/replication/rowguidcol-not-supported-merge-replication.md",
6292+
"redirect_url": "/sql/relational-databases/replication/merge/merge-replication"
6293+
},
6294+
{
6295+
"source_path": "support/sql/database-engine/replication/duplicate-keys-sys-syscommittab-table.md",
6296+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/duplicate-keys-sys-syscommittab-table"
6297+
},
6298+
{
6299+
"source_path": "support/sql/database-engine/replication/problem-use-custom-business-logic-handler.md",
6300+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/problem-use-custom-business-logic-handler"
6301+
},
6302+
{
6303+
"source_path": "support/sql/database-engine/replication/merge-replication-cannot-support-centralized-subscriber-topologies.md",
6304+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/merge-replication-cannot-support-centralized-subscriber-topologies"
6305+
},
6306+
{
6307+
"source_path": "support/sql/database-engine/replication/error-use-change-data-capture-service.md",
6308+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/error-use-change-data-capture-service"
6309+
},
6310+
{
6311+
"source_path": "support/sql/database-engine/replication/script-failed-error-merge-publication-snapshot.md",
6312+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/script-failed-error-merge-publication-snapshot"
6313+
},
6314+
{
6315+
"source_path": "support/sql/database-engine/replication/snapshot-logreader-agents-fail-destination-table-empty.md",
6316+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/snapshot-logreader-agents-fail-destination-table-empty"
6317+
},
6318+
{
6319+
"source_path": "support/sql/database-engine/replication/sql-merge-replication-synchronization-fails.md",
6320+
"redirect_url": "/previous-versions/troubleshoot/sql/replication/sql-merge-replication-synchronization-fails"
62616321
}
62626322
]
62636323
}

support/entra/entra-id/dir-dmns-obj/troubleshoot-dynamic-group-processing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to troubleshoot dynamic group processing by using pause a
44
author: genlin
55
ms.author: genli
66
ms.reviewer: yuhko, barclayn, v-weizhu
7-
ms.date: 03/04/2025
7+
ms.date: 04/24/2025
88
ms.service: entra-id
99
ms.custom: sap:Users
1010
---
@@ -24,7 +24,7 @@ These issues can be caused by:
2424
This article provides sample Entra ID PowerShell scripts to pause and resume dynamic group updates. Pausing dynamic group processing can stop rule processing and prevent unintended membership updates. Resuming dynamic group processing can restore normal group functionality.
2525

2626
> [!IMPORTANT]
27-
> Dynamic membership group changes are usually processed within a few hours. However, processing may take more than 24 hours depending on factors such as tenant size, group size, number of attribute changes, rule complexity, and operator choice (such as using `CONTAINS`, `MATCH`, or `MemberOf`).
27+
> Dynamic membership group changes are usually processed within a few hours. However, processing may take more than 24 hours depending on factors such as tenant size, group size, number of attribute changes, rule complexity, and operator choice (such as using `CONTAINS`, `MATCH`, or `MemberOf`). For more information, see [Understanding and Managing Dynamic Group Processing in Microsoft Entra ID](/entra/identity/users/manage-dynamic-group).
2828
2929
## Download pause and resume dynamic group processing scripts
3030

support/entra/entra-id/dir-dmns-obj/troubleshoot-dynamic-groups.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ You receive an error when deleting a group.
7272

7373
You restored a deleted group but didn't see any update.
7474

75-
- When a dynamic group is deleted and restored, it's seen as a new group and re-populated according to the rule. This process might take up to 24 hours.
75+
- When a dynamic group is deleted and restored, it's seen as a new group and re-populated according to the rule. This process may take some time to complete depending on factors such as tenant size.
7676

7777
## Evaluate whether a group is a dynamic group<a id="1"></a>
7878

@@ -184,9 +184,9 @@ You've created a dynamic group and configured a rule, but encountered one of the
184184
- Allow a guest user addition by following the **Manage guest user** setting for groups in a tenant.
185185
- Change the group rule to exclude a guest user by adding: `(user.userType -eq "member")`.
186186

187-
5. If everything looks correct, allow some time for the group to populate. Depending on the size of your tenant, the group may take up to 24 hours to populate the first time, or after a rule change.
187+
5. If everything looks correct, wait for the group to populate. Depending on the size of your tenant, the group may take some time to populate the first time, or after a rule change. We recommend waiting a minimum of 24 hours to allow group processing to complete.
188188

189-
6. If problem still exists after 24 hours and the processing status shows as complete, you can [reset the processing for the group](#18) to resolve any transient system issue.
189+
6. If the processing status shows as complete and the issue persists, you can [reset the processing for the group](#18) to resolve any transient system issue.
190190

191191
If the processing status shows as **in processing**, continue to wait.
192192

@@ -256,11 +256,7 @@ Before attempting to delete a group in Microsoft Entra ID, ensure you have [dele
256256

257257
- If an Office 365 group is deleted, it can only be restored up to 30 days before permanent deletion occurs. Once permanently deleted, the group can no longer be restored. To learn more about restoring groups, see [Restore a deleted Microsoft 365 group in Microsoft Entra ID](/azure/active-directory/fundamentals/active-directory-groups-restore-azure-portal).
258258
- This functionality isn't supported for security groups and distribution groups.
259-
- Verify that you're authorized to restore an Office 365 group. Only Global administrators, User account administrators, Intune service administrators, , or the owner of the group can restore a group.
260-
261-
### You restored a deleted dynamic group, but didn't see any update
262-
263-
When a dynamic group is deleted and restored, it's seen as a new group and re-populated according to the rule. This process might take up to 24 hours.
259+
- Verify that you're authorized to restore an Office 365 group. Only Global administrators, User account administrators, Intune service administrators, or the owner of the group can restore a group.
264260

265261
## Related articles
266262

support/sql/database-engine/backup-restore/asr-agent-vss-backup-fails.md

Lines changed: 0 additions & 83 deletions
This file was deleted.
Binary file not shown.

support/sql/database-engine/backup-restore/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@ items:
33
href: access-violations-memory-dump-files.md
44
- name: A TDE-enabled database may not recover
55
href: tde-enabled-database-not-recover.md
6-
- name: ASR Agent or non-component VSS Backup fails
7-
href: asr-agent-vss-backup-fails.md
86
- name: Azure Site Recovery jobs fail on servers hosting SQL servers
97
href: revocery-jobs-fail-servers.md
108
- name: Back up a database using a VSS backup application

support/sql/database-engine/database-file-operations/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,6 @@ items:
3535
href: support-network-database-files.md
3636
- name: Support on iSCSI technology components
3737
href: support-iscsi-technology-components.md
38-
- name: Transaction log file doesn't grow
39-
href: transaction-log-file-not-grow.md
4038
- name: Transaction log file grows for databases with In-Memory OLTP
4139
href: transaction-log-file-grows-databases-in-memory-oltp.md
4240
- name: Troubleshoot errors related to system disk sector size greater than 4 KB

support/sql/database-engine/database-file-operations/transaction-log-file-not-grow.md

Lines changed: 0 additions & 58 deletions
This file was deleted.

0 commit comments

Comments
 (0)