You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -86,7 +86,7 @@ To join the managed domain using **SSSD** and the *User Logon Management* module
86
86
87
87
In YaST, select**System> Network Settings**.
88
88
89
-
1. Select the *Hostname/DNS* tab, then enter the IP address(es) of the managed domain into the text box *Name Server 1*. These IP addresses are shown on the *Properties* window in the Azure portalfor your managed domain, such as *10.0.2.4* and *10.0.2.5*.
89
+
1. Select the *Hostname/DNS* tab, then enter the IP address(es) of the managed domain into the text box *Name Server 1*. These IP addresses are shown on the *Properties* window in the Microsoft Entra admin centerfor your managed domain, such as *10.0.2.4* and *10.0.2.5*.
90
90
91
91
Add your own managed domain IP addresses, thenselect**OK**.
92
92
@@ -162,7 +162,7 @@ To join the managed domain using **winbind** and the *Windows Domain Membership*
162
162
163
163
1. If you want to change the UID and GID ranges for the Samba users and groups, select*Expert Settings*.
164
164
165
-
1. Configure Network Time Protocol (NTP) time synchronization foryour managed domain by selecting *NTP Configuration*. Enter the IP addresses of the managed domain. These IP addresses are shown on the *Properties* windowin the Azure portalfor your managed domain, such as *10.0.2.4* and *10.0.2.5*.
165
+
1. Configure Network Time Protocol (NTP) time synchronization foryour managed domain by selecting *NTP Configuration*. Enter the IP addresses of the managed domain. These IP addresses are shown on the *Properties* windowin the Microsoft Entra admin centerfor your managed domain, such as *10.0.2.4* and *10.0.2.5*.
166
166
167
167
1. Select **OK** and confirm the domain join when prompted for it.
Copy file name to clipboardExpand all lines: articles/active-directory-domain-services/join-windows-vm.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: domain-services
9
9
ms.workload: identity
10
10
ms.topic: tutorial
11
-
ms.date: 06/22/2023
11
+
ms.date: 09/15/2023
12
12
ms.author: justinha
13
13
14
14
#Customer intent: As an server administrator, I want to learn how to join a Windows Server VM to an Azure Active Directory Domain Services managed domain to provide centralized identity and policy.
@@ -43,21 +43,21 @@ To complete this tutorial, you need the following resources:
43
43
44
44
If you already have a VM that you want to domain-join, skip to the section to [join the VM to the managed domain](#join-the-vm-to-the-managed-domain).
45
45
46
-
## Sign in to the Azure portal
46
+
## Sign in to the Microsoft Entra admin center
47
47
48
-
In this tutorial, you create a Windows Server VM to join to your managed domain using the Azure portal. To get started, first sign in to the [Azure portal](https://portal.azure.com).
48
+
In this tutorial, you create a Windows Server VM to join to your managed domain using the Microsoft Entra admin center. To get started, first sign in to the [Microsoft Entra admin center](https://entra.microsoft.com).
49
49
50
50
## Create a Windows Server virtual machine
51
51
52
52
To see how to join a computer to a managed domain, let's create a Windows Server VM. This VM is connected to an Azure virtual network that provides connectivity to the managed domain. The process to join a managed domain is the same as joining a regular on-premises Active Directory Domain Services domain.
53
53
54
54
If you already have a VM that you want to domain-join, skip to the section to [join the VM to the managed domain](#join-the-vm-to-the-managed-domain).
55
55
56
-
1. From the Azure portal menu or from the **Home** page, select **Create a resource**.
56
+
1. From the Microsoft Entra admin center menu or from the **Home** page, select **Create a resource**.
57
57
58
58
1. From **Get started**, choose **Windows Server 2016 Datacenter**.
59
59
60
-
60
+
61
61
62
62
1. In the **Basics** window, configure the core settings for the virtual machine. Leave the defaults for *Availability options*, *Image*, and *Size*.
63
63
@@ -71,7 +71,7 @@ If you already have a VM that you want to domain-join, skip to the section to [j
71
71
72
72
1. By default, VMs created in Azure are accessible from the Internet using RDP. When RDP is enabled, automated sign-in attacks are likely to occur, which may disable accounts with common names such as *admin* or *administrator* due to multiple failed successive sign-in attempts.
73
73
74
-
RDP should only be enabled when required, and limited to a set of authorized IP ranges. This configuration helps improve the security of the VM and reduces the area for potential attack. Or, create and use an Azure Bastion host that allows access only through the Azure portal over TLS. In the next step of this tutorial, you use an Azure Bastion host to securely connect to the VM.
74
+
RDP should only be enabled when required, and limited to a set of authorized IP ranges. This configuration helps improve the security of the VM and reduces the area for potential attack. Or, create and use an Azure Bastion host that allows access only through the Microsoft Entra admin center over TLS. In the next step of this tutorial, you use an Azure Bastion host to securely connect to the VM.
75
75
76
76
Under **Public inbound ports**, select *None*.
77
77
@@ -89,21 +89,21 @@ If you already have a VM that you want to domain-join, skip to the section to [j
89
89
In the **Networking** pane, select the virtual network in which your managed domain is deployed, such as *aaads-vnet*
90
90
1. In this example, the existing *aaads-subnet* is shown that the managed domain is connected to. Don't connect your VM to this subnet. To create a subnet for the VM, select **Manage subnet configuration**.
91
91
92
-
92
+
93
93
94
94
1. In the left-hand menu of the virtual network window, select **Address space**. The virtual network is created with a single address space of *10.0.2.0/24*, which is used by the default subnet. Other subnets, such as for *workloads* or Azure Bastion may also already exist.
95
95
96
96
Add an additional IP address range to the virtual network. The size of this address range and the actual IP address range to use depends on other network resources already deployed. The IP address range shouldn't overlap with any existing address ranges in your Azure or on-premises environment. Make sure that you size the IP address range large enough for the number of VMs you expect to deploy into the subnet.
97
97
98
98
In the following example, an additional IP address range of *10.0.5.0/24* is added. When ready, select **Save**.
99
99
100
-
100
+
101
101
102
102
1. Next, in the left-hand menu of the virtual network window, select **Subnets**, then choose **+ Subnet** to add a subnet.
103
103
104
104
1. Select **+ Subnet**, then enter a name for the subnet, such as *management*. Provide an **Address range (CIDR block)**, such as *10.0.5.0/24*. Make sure that this IP address range doesn't overlap with any other existing Azure or on-premises address ranges. Leave the other options as their default values, then select **OK**.
105
105
106
-
106
+
107
107
108
108
1. It takes a few seconds to create the subnet. Once it's created, select the *X* to close the subnet window.
109
109
1. Back in the **Networking** pane to create a VM, choose the subnet you created from the drop-down menu, such as *management*. Again, make sure you choose the correct subnet and don't deploy your VM in the same subnet as your managed domain.
@@ -112,23 +112,23 @@ If you already have a VM that you want to domain-join, skip to the section to [j
112
112
1. Set **Boot diagnostics** to *Off*. Leave the other options as their default values, then select **Review + create**.
113
113
1. Review the VM settings, then select **Create**.
114
114
115
-
It takes a few minutes to create the VM. The Azure portal shows the status of the deployment. Once the VM is ready, select **Go to resource**.
115
+
It takes a few minutes to create the VM. The Microsoft Entra admin center shows the status of the deployment. Once the VM is ready, select **Go to resource**.
116
116
117
-
117
+
118
118
119
119
## Connect to the Windows Server VM
120
120
121
-
To securely connect to your VMs, use an Azure Bastion host. With Azure Bastion, a managed host is deployed into your virtual network and provides web-based RDP or SSH connections to VMs. No public IP addresses are required for the VMs, and you don't need to open network security group rules for external remote traffic. You connect to VMs using the Azure portal from your web browser. If needed, [create an Azure Bastion host][azure-bastion].
121
+
To securely connect to your VMs, use an Azure Bastion host. With Azure Bastion, a managed host is deployed into your virtual network and provides web-based RDP or SSH connections to VMs. No public IP addresses are required for the VMs, and you don't need to open network security group rules for external remote traffic. You connect to VMs using the Microsoft Entra admin center from your web browser. If needed, [create an Azure Bastion host][azure-bastion].
122
122
123
123
To use a Bastion host to connect to your VM, complete the following steps:
124
124
125
125
1. In the **Overview** pane for your VM, select **Connect**, then **Bastion**.
126
126
127
-
127
+
128
128
129
129
1. Enter the credentials for your VM that you specified in the previous section, then select **Connect**.
130
130
131
-
131
+
132
132
133
133
If needed, allow your web browser to open pop-ups for the Bastion connection to be displayed. It takes a few seconds to make the connection to your VM.
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/concept-authentication-methods-manage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: authentication
8
8
ms.topic: conceptual
9
-
ms.date: 05/19/2023
9
+
ms.date: 09/15/2023
10
10
11
11
ms.author: justinha
12
12
author: justinha
@@ -32,7 +32,7 @@ Most methods also have configuration parameters to more precisely control how th
32
32
33
33
Or let's say you want to enable passwordless authentication with Microsoft Authenticator. You can set extra parameters like showing the user sign-in location or the name of the app being signed into. These options provide more context for users when they sign-in and help prevent accidental MFA approvals.
34
34
35
-
To manage the Authentication methods policyin the Azure AD portal, click **Security** > **Authentication methods** > **Policies**.
35
+
To manage the Authentication methods policy, sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Authentication Policy Administrator](../roles/permissions-reference.md#authentication-policy-administrator) and browse to **Protection** > **Authentication methods** > **Policies**.
36
36
37
37
:::image type="content" border="true" source="./media/concept-authentication-methods-manage/authentication-methods-policy.png" alt-text="Screenshot of Authentication methods policy.":::
Two-way SMS for Azure AD Multi-Factor Authentication (MFA) Server was originally deprecated in 2018, and no longer supported after February 24, 2021, except for organizations that received a support extension until August 2, 2021. Administrators should enable another method for users who still use two-way SMS.
21
21
22
-
Email notifications and Azure portal Service Health notifications (portal toasts) were sent to affected admins on December 8, 2020 and January 28, 2021. The alerts went to the Owner, Co-Owner, Admin, and Service Admin RBAC roles tied to the subscriptions. If you've already completed the following steps, no action is necessary.
22
+
Email notifications and Service Health notifications (portal toasts) were sent to affected admins on December 8, 2020 and January 28, 2021. The alerts went to the Owner, Co-Owner, Admin, and Service Admin RBAC roles tied to the subscriptions. If you've already completed the following steps, no action is necessary.
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/how-to-mfa-server-migration-utility.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -346,7 +346,7 @@ Once you've successfully migrated user data, you can validate the end-user exper
346
346
347
347
#### Enable Staged Rollout
348
348
349
-
1. Navigate to the following url: [Enable staged rollout features - Microsoft Azure](https://portal.azure.com/?mfaUIEnabled=true%2F#view/Microsoft_AAD_IAM/StagedRolloutEnablementBladeV2).
349
+
1. Navigate to the following url: [Enable staged rollout features - Microsoft Azure](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/StagedRolloutEnablementBladeV2).
350
350
351
351
1. Change **Azure multifactor authentication** to **On**, and then click **Manage groups**.
0 commit comments