Merge pull request #101436 from iainfoulds/azuread-securityui

[AzureAD-Authentication] Updating for Security menu in UI

Author: PRMerger12

articles/active-directory/authentication/concept-mfa-authprovider.md

@@ -45,11 +45,11 @@ If your MFA provider is not linked to an Azure AD tenant, or you link the new MF
 > [!CAUTION]
 > There is no confirmation when deleting an authentication provider. Selecting **Delete** is a permanent process.
 
-Authentication providers can be found in the **Azure portal** > **Azure Active Directory** > **MFA** > **Providers**. Click on listed providers to see details and configurations associated with that provider.
+Authentication providers can be found in the **Azure portal** > **Azure Active Directory** > **Security** > **MFA** > **Providers**. Click on listed providers to see details and configurations associated with that provider.
 
 Before removing an authentication provider, take note of any customized settings configured in your provider. Decide what settings need to be migrated to general MFA settings from your provider and complete the migration of those settings. 
 
-Azure MFA Servers linked to providers will need to be reactivated using credentials generated under **Azure portal** > **Azure Active Directory** > **MFA** > **Server settings**. Before reactivating, the following files must be deleted from the `\Program Files\Multi-Factor Authentication Server\Data\` directory on Azure MFA Servers in your environment:
+Azure MFA Servers linked to providers will need to be reactivated using credentials generated under **Azure portal** > **Azure Active Directory** > **Security** > **MFA** > **Server settings**. Before reactivating, the following files must be deleted from the `\Program Files\Multi-Factor Authentication Server\Data\` directory on Azure MFA Servers in your environment:
 
 - caCert
 - cert
@@ -61,7 +61,7 @@ Azure MFA Servers linked to providers will need to be reactivated using credenti
 
 ![Delete an auth provider from the Azure portal](./media/concept-mfa-authprovider/authentication-provider-removal.png)
 
-When you have confirmed that all settings have been migrated, you can browse to the **Azure portal** > **Azure Active Directory** > **MFA** > **Providers** and select the ellipses **...** and select **Delete**.
+When you have confirmed that all settings have been migrated, you can browse to the **Azure portal** > **Azure Active Directory** > **Security** > **MFA** > **Providers** and select the ellipses **...** and select **Delete**.
 
 > [!WARNING]
 > Deleting an authentication provider will delete any reporting information associated with that provider. You may want to save activity reports before deleting your provider.

articles/active-directory/authentication/howto-mfa-adfs.md

@@ -83,7 +83,7 @@ The first thing we need to do is to configure the AD FS claims. Create two claim
 Now that the claims are in place, we can configure trusted IPs.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-2. Select **Azure Active Directory** > **Conditional Access** > **Named locations**.
+2. Select **Azure Active Directory** > **Security** > **Conditional Access** > **Named locations**.
 3. From the **Conditional Access - Named locations** blade, select **Configure MFA trusted IPs**
 
    ![Azure AD Conditional Access named locations Configure MFA trusted IPs](./media/howto-mfa-adfs/trustedip6.png)

articles/active-directory/authentication/howto-mfa-getstarted.md

@@ -218,7 +218,7 @@ It is important that you prevent being inadvertently locked out of your Azure AD
 ### Create Conditional Access policy
 
 1. Sign in to the [Azure portal](https://portal.azure.com) using a global administrator account.
-1. Browse to **Azure Active Directory**, **Conditional Access**.
+1. Browse to **Azure Active Directory** > **Security** > **Conditional Access**.
 1. Select **New policy**.
    ![Create a Conditional Access policy to enable MFA for Azure portal users in pilot group](media/howto-mfa-getstarted/conditionalaccess-newpolicy.png)
 1. Provide a meaningful name for your policy.

articles/active-directory/authentication/howto-mfaserver-deploy.md

@@ -93,8 +93,8 @@ If you aren't using the Event Confirmation feature, and your users aren't using
 Follow these steps to download the Azure Multi-Factor Authentication Server from the Azure portal:
 
 1. Sign in to the [Azure portal](https://portal.azure.com) as an administrator.
-2. Search for and select *Azure Active Directory*. Select **MFA Server**.
-3. Select **Server settings**.
+2. Search for and select *Azure Active Directory*. Select **Security** > **MFA**.
+3. Under **Manager MFA Server**, select **Server settings**.
 4. Select **Download** and follow the instructions on the download page to save the installer. 
 
    ![Download MFA Server from the Azure portal](./media/howto-mfaserver-deploy/downloadportal.png)

articles/active-directory/authentication/howto-password-ban-bad-configure.md

@@ -23,7 +23,7 @@ Many organizations find their users create passwords using common local words su
 
 Configuring the custom banned password list requires an Azure Active Directory Premium P1 or P2 license. For more detailed information about Azure Active Directory licensing, see the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory/).
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory**, **Authentication methods**, then **Password protection**.
+1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory** > **Security** > **Authentication methods** > **Password protection**.
 1. Set the option **Enforce custom list**, to **Yes**.
 1. Add strings to the **Custom banned password list**, one string per line
    * The custom banned password list can contain up to 1000 terms.

articles/active-directory/authentication/howto-password-ban-bad-on-premises-operations.md

@@ -25,7 +25,7 @@ Follow the guidance in the article [Configuring the custom banned password list]
 
 ## Enable Password Protection
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory**, **Security**,**Authentication methods**, then **Password Protection**.
+1. Sign in to the [Azure portal](https://portal.azure.com) and browse to **Azure Active Directory** > **Security** > **Authentication methods** > **Password Protection**.
 1. Set **Enable Password Protection on Windows Server Active Directory** to **Yes**
 1. As mentioned in the [Deployment guide](howto-password-ban-bad-on-premises-deploy.md#deployment-strategy), it is recommended to initially set the **Mode** to **Audit**
    * After you are comfortable with the feature, you can switch the **Mode** to **Enforced**

articles/active-directory/authentication/howto-sspr-reporting.md

@@ -50,7 +50,7 @@ In the Azure portal experience, we have improved the way that you can view passw
 
 ### Converged registration (preview)
 
-If you are participating in the public preview of converged registration, information regarding user activity in the audit logs will be found under the service **Authentication Methods**.
+If you are participating in the public preview of converged registration, information regarding user activity in the audit logs will be found under **Security** > **Authentication Methods**.
 
 ## Description of the report columns in the Azure portal
 

articles/active-directory/authentication/quickstart-sspr.md

@@ -69,7 +69,7 @@ Now lets test your SSPR configuration with a test user that's part of the group
 
 ## Clean up resources
 
-To disable self-service password reset, search for and select **Azure Active Directory** in the Azure portal. Select **Properties** > **Password Reset**, and then choose **None** under **Self Service Password Reset Enabled**. When ready, select **Save**.
+To disable self-service password reset, search for and select **Azure Active Directory** in the Azure portal. Select **Password Reset**, and then choose **None** under **Self Service Password Reset Enabled**. When ready, select **Save**.
 
 ## Next steps
 

articles/active-directory/authentication/tutorial-mfa-applications.md

@@ -34,10 +34,10 @@ In this tutorial, you walk you through configuring a Conditional Access policy e
 ## Enable Azure Multi-Factor Authentication
 
 1. Sign in to the [Azure portal](https://portal.azure.com) using a Global Administrator account.
-1. Browse to **Azure Active Directory**, **Conditional Access**
+1. Browse to **Azure Active Directory** > **Security** > **Conditional Access**
 1. Select **New policy**
 1. Name your policy **MFA Pilot**
-1. Under **users and groups**, select the **Select users and groups** radio button
+1. Under **Users and groups**, select the **Select users and groups** radio button
     * Select your pilot group created as part of the prerequisites section of this article
     * Click **Done**
 1. Under **Cloud apps**, select the **Select apps** radio button
@@ -68,7 +68,7 @@ To prove that your Conditional Access policy works, you test logging in to a res
 If you decide you no longer want to use the functionality you have configured as part of this tutorial, make the following change.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
-1. Browse to **Azure Active Directory**, **Conditional Access**.
+1. Browse to **Azure Active Directory** > **Security** > **Conditional Access**.
 1. Select the Conditional Access policy you created.
 1. Click **Delete**.