Skip to content

Commit c69c8c5

Browse files
authored
Merge pull request #97564 from MicrosoftDocs/master
12/02 PM Publish
2 parents 48b7a50 + 231cd8b commit c69c8c5

File tree

224 files changed

+2063
-2429
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

224 files changed

+2063
-2429
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43846,6 +43846,11 @@
4384643846
"source_path": "articles/lab-services/classroom-labs/how-to-enable-multi-vm-environment.md",
4384743847
"redirect_url": "/azure/lab-services/classroom-labs/how-to-enable-nested-virtualization-template-vm",
4384843848
"redirect_document_id": false
43849+
},
43850+
{
43851+
"source_path": "articles/service-bus-messaging/migrate-java-apps-wild-fly.md",
43852+
"redirect_url": "/azure/app-service/containers/configure-language-java#use-service-bus-as-a-message-broker",
43853+
"redirect_document_id": false
4384943854
}
4385043855
]
4385143856
}

articles/active-directory-domain-services/check-health.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This article shows how to view the Azure AD DS health status and understand the
2525
The health status for an Azure AD DS managed domain is viewed using the Azure portal. Information on the last backup time and synchronization with Azure AD can be seen, along with any alerts that indicate a problem with the managed domain's health. To view the health status for an Azure AD DS managed domain, complete the following steps:
2626

2727
1. In the Azure portal, search for and select **Azure AD Domain Services**.
28-
1. Select your Azure AD DS managed domain, such as *contoso.com*.
28+
1. Select your Azure AD DS managed domain, such as *aadds.contoso.com*.
2929
1. On the left-hand side of the Azure AD DS resource window, select **Health**. The following example screenshot shows a healthy Azure AD DS managed domain and the status of the last backup and Azure AD synchronization:
3030

3131
![Health page overview in the Azure portal showing the Azure Active Directory Domain Services status](./media/check-health/health-page.png)

articles/active-directory-domain-services/create-gmsa.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ First, create a custom OU using the [New-ADOrganizationalUnit][New-AdOrganizatio
6161
> [!TIP]
6262
> To complete these steps to create a gMSA, [use your management VM][tutorial-create-management-vm]. This management VM should already have the required AD PowerShell cmdlets and connection to the managed domain.
6363
64-
The following example creates a custom OU named *myNewOU* in the Azure AD DS managed domain named *contoso.com*. Use your own OU and managed domain name:
64+
The following example creates a custom OU named *myNewOU* in the Azure AD DS managed domain named *aadds.contoso.com*. Use your own OU and managed domain name:
6565

6666
```powershell
6767
New-ADOrganizationalUnit -Name "myNewOU" -Path "DC=contoso,DC=COM"
@@ -71,20 +71,20 @@ Now create a gMSA using the [New-ADServiceAccount][New-ADServiceAccount] cmdlet.
7171

7272
* **-Name** is set to *WebFarmSvc*
7373
* **-Path** parameter specifies the custom OU for the gMSA created in the previous step.
74-
* DNS entries and service principal names are set for *WebFarmSvc.contoso.com*
74+
* DNS entries and service principal names are set for *WebFarmSvc.aadds.contoso.com*
7575
* Principals in *CONTOSO-SERVER$* are allowed to retrieve the password use the identity.
7676

7777
Specify your own names and domain names.
7878

7979
```powershell
8080
New-ADServiceAccount -Name WebFarmSvc `
81-
-DNSHostName WebFarmSvc.contoso.com `
81+
-DNSHostName WebFarmSvc.aadds.contoso.com `
8282
-Path "OU=MYNEWOU,DC=contoso,DC=com" `
8383
-KerberosEncryptionType AES128, AES256 `
8484
-ManagedPasswordIntervalInDays 30 `
85-
-ServicePrincipalNames http/WebFarmSvc.contoso.com/contoso.com, `
86-
http/WebFarmSvc.contoso.com/contoso, `
87-
http/WebFarmSvc/contoso.com, `
85+
-ServicePrincipalNames http/WebFarmSvc.aadds.contoso.com/aadds.contoso.com, `
86+
http/WebFarmSvc.aadds.contoso.com/contoso, `
87+
http/WebFarmSvc/aadds.contoso.com, `
8888
http/WebFarmSvc/contoso `
8989
-PrincipalsAllowedToRetrieveManagedPassword CONTOSO-SERVER$
9090
```

articles/active-directory-domain-services/create-ou.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,11 +62,11 @@ To create a custom OU, you use the Active Directory Administrative Tools from a
6262
1. Sign in to your management VM. For steps on how to connect using the Azure portal, see [Connect to a Windows Server VM][connect-windows-server-vm].
6363
1. From the Start screen, select **Administrative Tools**. A list of available management tools is shown that were installed in the tutorial to [create a management VM][tutorial-create-management-vm].
6464
1. To create and manage OUs, select **Active Directory Administrative Center** from the list of administrative tools.
65-
1. In the left pane, choose your Azure AD DS managed domain, such as *contoso.com*. A list of existing OUs and resources is shown:
65+
1. In the left pane, choose your Azure AD DS managed domain, such as *aadds.contoso.com*. A list of existing OUs and resources is shown:
6666

6767
![Select your Azure AD DS managed domain in the Active Directory Administrative Center](./media/active-directory-domain-services-admin-guide/create-ou-adac-overview.png)
6868

69-
1. The **Tasks** pane is shown on the right side of the Active Directory Administrative Center. Under the domain, such as *contoso.com*, select **New > Organizational Unit**.
69+
1. The **Tasks** pane is shown on the right side of the Active Directory Administrative Center. Under the domain, such as *aadds.contoso.com*, select **New > Organizational Unit**.
7070

7171
![Select the option to create a new OU in the Active Directory Administrative Center](./media/active-directory-domain-services-admin-guide/create-ou-adac-new-ou.png)
7272

articles/active-directory-domain-services/delete-aadds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ If you no longer need a managed domain, you can delete an Azure Active Directory
3131
To delete an Azure AD DS managed domain, complete the following steps:
3232

3333
1. In the Azure portal, search for and select **Azure AD Domain Services**.
34-
1. Select the name of your Azure AD DS managed domain, such as *contoso.com*.
34+
1. Select the name of your Azure AD DS managed domain, such as *aadds.contoso.com*.
3535
1. On the **Overview** page, select **Delete**. To confirm the deletion, type the domain name of the managed domain again, then select **Delete**.
3636

3737
It can take 15-20 minutes or more to delete the Azure AD DS managed domain.

articles/active-directory-domain-services/deploy-kcd.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Resource-based KCD is configured using PowerShell. You use the [Set-ADComputer][
5252

5353
## Configure resource-based KCD for a computer account
5454

55-
In this scenario, let's assume you have a web app that runs on the computer named *contoso-webapp.contoso.com*. The web app needs to access a web API that runs on the computer named *contoso-api.contoso.com* in the context of domain users. Complete the following steps to configure this scenario:
55+
In this scenario, let's assume you have a web app that runs on the computer named *contoso-webapp.aadds.contoso.com*. The web app needs to access a web API that runs on the computer named *contoso-api.aadds.contoso.com* in the context of domain users. Complete the following steps to configure this scenario:
5656

5757
1. [Create a custom OU](create-ou.md). You can delegate permissions to manage this custom OU to users within the Azure AD DS managed domain.
5858
1. [Domain-join the virtual machines][create-join-windows-vm], both the one that runs the web app, and the one that runs the web API, to the Azure AD DS managed domain. Create these computer accounts in the custom OU from the previous step.
@@ -63,8 +63,8 @@ In this scenario, let's assume you have a web app that runs on the computer name
6363
1. Finally, configure resource-based KCD using the [Set-ADComputer][Set-ADComputer] PowerShell cmdlet. From your domain-joined management VM and logged in as user account that's a member of the *Azure AD DC administrators* group, run the following cmdlets. Provide your own computer names as needed:
6464

6565
```powershell
66-
$ImpersonatingAccount = Get-ADComputer -Identity contoso-webapp.contoso.com
67-
Set-ADComputer contoso-api.contoso.com -PrincipalsAllowedToDelegateToAccount $ImpersonatingAccount
66+
$ImpersonatingAccount = Get-ADComputer -Identity contoso-webapp.aadds.contoso.com
67+
Set-ADComputer contoso-api.aadds.contoso.com -PrincipalsAllowedToDelegateToAccount $ImpersonatingAccount
6868
```
6969
7070
## Configure resource-based KCD for a user account

articles/active-directory-domain-services/deploy-sp-profile-sync.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ From your Azure AD DS management VM, complete the following steps:
5858
5959
1. From the Start screen, select **Administrative Tools**. A list of available management tools is shown that were installed in the tutorial to [create a management VM][tutorial-create-management-vm].
6060
1. To manage group membership, select **Active Directory Administrative Center** from the list of administrative tools.
61-
1. In the left pane, choose your Azure AD DS managed domain, such as *contoso.com*. A list of existing OUs and resources is shown.
61+
1. In the left pane, choose your Azure AD DS managed domain, such as *aadds.contoso.com*. A list of existing OUs and resources is shown.
6262
1. Select the **Users** OU, then choose the *AAD DC Service Accounts* security group.
6363
1. Select **Members**, then choose **Add...**.
6464
1. Enter the name of the SharePoint service account, then select **OK**. In the following example, the SharePoint service account is named *spadmin*:

articles/active-directory-domain-services/join-windows-vm-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ To create a Windows Server VM then join it to an Azure AD DS managed domain, com
8989
| Existing Subnet Name | The name of the existing virtual network subnet, such as *Workloads*. |
9090
| DNS Label Prefix | Enter a DNS name to use for the VM, such as *myvm*. |
9191
| VM size | Specify a VM size, such as *Standard_DS2_v2*. |
92-
| Domain To Join | The Azure AD DS managed domain DNS name, such as *contoso.com*. |
92+
| Domain To Join | The Azure AD DS managed domain DNS name, such as *aadds.contoso.com*. |
9393
| Domain Username | The user account in the Azure AD DS managed domain that should be used to join the VM to the managed domain. This account must be a member of the *Azure AD DC administrators* group. |
9494
| Domain Password | The password for the user account specified in the previous setting. |
9595
| Optional OU Path | The custom OU in which to add the VM. If you don't specify a value for this parameter, the VM is added to the default *AAD DC Computers* OU. |

articles/active-directory-domain-services/manage-dns.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To create and modify DNS records in Azure AD DS, you need to install the DNS Ser
4848
1. In the *Dashboard* pane of the **Server Manager** window, select **Add Roles and Features**.
4949
1. On the **Before You Begin** page of the *Add Roles and Features Wizard*, select **Next**.
5050
1. For the *Installation Type*, leave the **Role-based or feature-based installation** option checked and select **Next**.
51-
1. On the **Server Selection** page, choose the current VM from the server pool, such as *myvm.contoso.com*, then select **Next**.
51+
1. On the **Server Selection** page, choose the current VM from the server pool, such as *myvm.aadds.contoso.com*, then select **Next**.
5252
1. On the **Server Roles** page, click **Next**.
5353
1. On the **Features** page, expand the **Remote Server Administration Tools** node, then expand the **Role Administration Tools** node. Select **DNS Server Tools** feature from the list of role administration tools.
5454

@@ -65,7 +65,7 @@ With the DNS Server tools installed, you can administer DNS records on the Azure
6565
> To administer DNS in an Azure AD DS managed domain, you must be signed in to a user account that's a member of the *AAD DC Administrators* group.
6666
6767
1. From the Start screen, select **Administrative Tools**. A list of available management tools is shown, including **DNS** installed in the previous section. Select **DNS** to launch the DNS Management console.
68-
1. In the **Connect to DNS Server** dialog, select **The following computer**, then enter the DNS domain name of the managed domain, such as *contoso.com*:
68+
1. In the **Connect to DNS Server** dialog, select **The following computer**, then enter the DNS domain name of the managed domain, such as *aadds.contoso.com*:
6969

7070
![Connect to the Azure AD DS managed domain in the DNS console](./media/active-directory-domain-services-admin-guide/dns-console-connect-to-domain.png)
7171

articles/active-directory-domain-services/manage-group-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ To create and configure Group Policy Object (GPOs), you need to install the Grou
4949
1. In the *Dashboard* pane of the **Server Manager** window, select **Add Roles and Features**.
5050
1. On the **Before You Begin** page of the *Add Roles and Features Wizard*, select **Next**.
5151
1. For the *Installation Type*, leave the **Role-based or feature-based installation** option checked and select **Next**.
52-
1. On the **Server Selection** page, choose the current VM from the server pool, such as *myvm.contoso.com*, then select **Next**.
52+
1. On the **Server Selection** page, choose the current VM from the server pool, such as *myvm.aadds.contoso.com*, then select **Next**.
5353
1. On the **Server Roles** page, click **Next**.
5454
1. On the **Features** page, select the **Group Policy Management** feature.
5555

@@ -72,7 +72,7 @@ Default group policy objects (GPOs) exist for users and computers in an Azure AD
7272

7373
There are two built-in Group Policy Objects (GPOs) in an Azure AD DS managed domain - one for the *AADDC Computers* container, and one for the *AADDC Users* container. You can customize these GPOs to configure group policy as needed within your Azure AD DS managed domain.
7474

75-
1. In the **Group Policy Management** console, expand the **Forest: contoso.com** node. Next, expand the **Domains** nodes.
75+
1. In the **Group Policy Management** console, expand the **Forest: aadds.contoso.com** node. Next, expand the **Domains** nodes.
7676

7777
Two built-in containers exist for *AADDC Computers* and *AADDC Users*. Each of these containers has a default GPO applied to them.
7878

0 commit comments

Comments
 (0)