Skip to content

Commit 8f182c2

Browse files
more edits
1 parent 2349ed4 commit 8f182c2

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

articles/azure-monitor/scom-manage-instance/configure-network-firewall.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,8 +100,8 @@ To function properly, SCOM Managed Instance must have access to the following po
100100
|*.azuremonitor-scommiconnect.azure.com|443|Outbound| |Bridge Service|
101101

102102
> [!IMPORTANT]
103-
> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
103+
> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and the network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
104104
105105
## Next steps
106106

107-
- [Verify Azure and internal GPO policies](verify-azure-and-internal-gpo-policies.md)
107+
- [Verify Azure and internal GPO policies](verify-azure-internal-group-policy-object-policies.md)

articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
ms.assetid:
3-
title: Create a computer group and group-managed service account for Azure Monitor SCOM Managed Instance
4-
description: This article describes how to create a group-managed service account, computer group, and domain user account in on-premises Active Directory.
3+
title: Create a computer group and gMSA account for Azure Monitor SCOM Managed Instance
4+
description: This article describes how to create a gMSA account, computer group, and domain user account in on-premises Active Directory.
55
author: PriskeyJeronika-MS
66
ms.author: v-gjeronika
77
manager: jsuri
@@ -11,7 +11,7 @@ ms.subservice: operations-manager-managed-instance
1111
ms.topic: how-to
1212
---
1313

14-
# Create a computer group and group-managed service account for Azure Monitor SCOM Managed Instance
14+
# Create a computer group and gMSA account for Azure Monitor SCOM Managed Instance
1515

1616
This article describes how to create a group-managed service account (gMSA) account, computer group, and domain user account in on-premises Active Directory.
1717

@@ -73,8 +73,8 @@ Add-KdsRootKey -EffectiveTime ((get-date).addhours(-10))
7373
Ensure that the created gMSA account is a local admin account. If there are any Group Policy Object policies on the local admins at the Active Directory level, ensure that they have the gMSA account as the local admin.
7474

7575
> [!IMPORTANT]
76-
> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
76+
> To minimize the need for extensive communication with both your Active Directory admin and the network admin, see [Self-verification](self-verification-of-steps.md). The article outlines the procedures that the Active Directory admin and network admin use to validate their configuration changes and ensure their successful implementation. This process reduces unnecessary back-and-forth interactions from the Operations Manager admin to the Active Directory admin and the network admin. This configuration saves time for the admins.
7777
7878
## Next steps
7979

80-
[Store domain credentials in Azure Key Vault](store-domain-credentials-key-vault.md)
80+
[Store domain credentials in Azure Key Vault](store-domain-credentials-in-key-vault.md)

0 commit comments

Comments
 (0)