Merge pull request #245985 from alexbuckgit/alexbuckgit/docutune-autopr-20230724-001629-4587041-ignore-build

[BULK] DocuTune - Standardize formatting of Azure portal links

Author: ttorble

articles/active-directory/app-provisioning/on-premises-powershell-connector.md

@@ -72,7 +72,7 @@ If you have already downloaded the provisioning agent and configured it for anot
 
 ## Configure the On-premises ECMA app
 
- 1. Sign in to the Azure portal as an administrator.
+ 1. Sign in to the [Azure portal](https://portal.azure.com) as an administrator.
  2. Go to **Enterprise applications** and select **New application**.
  3. Search for the **On-premises ECMA app** application, give the app a name, and select **Create** to add it to your tenant.
  4. Navigate to the **Provisioning** page of your application.
@@ -259,7 +259,7 @@ Follow these steps to confirm that the connector host has started and has identi
  1. Return to the web browser window where you were configuring the application provisioning in the portal.
     >[!NOTE]
     >If the window had timed out, then you need to re-select the agent.
-     1. Sign in to the Azure portal.
+     1. Sign in to the [Azure portal](https://portal.azure.com).
      2. Go to **Enterprise applications** and the **On-premises ECMA app** application.
      3. Click on **Provisioning**.
      4. If **Get started** appears, then change the mode to **Automatic**,  on the **On-Premises Connectivity** section, select the agent that you just deployed and select **Assign Agent(s)**, and wait 10 minutes. Otherwise go to **Edit Provisioning**.
@@ -281,7 +281,7 @@ Return to the web browser window where you were configuring the application prov
 >[!NOTE]
 >If the window had timed out, then you need to re-select the agent.
 
-   1. Sign in to the Azure portal.
+   1. Sign in to the [Azure portal](https://portal.azure.com).
    2. Go to **Enterprise applications** and the **On-premises ECMA app** application.
    3. Select on **Provisioning**.
    4. If **Get started** appears, then change the mode to **Automatic**,  on the **On-Premises Connectivity** section, select the agent that you deployed and select **Assign Agent(s)**. Otherwise go to **Edit Provisioning**.

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

@@ -1403,7 +1403,7 @@ It's recommended, but not required, that you support multiple secrets for easy r
 
 #### How to set up OAuth code grant flow
 
-1. Sign in to the Azure portal, go to **Enterprise applications** > **Application** > **Provisioning** and select **Authorize**.
+1. Sign in to the [Azure portal](https://portal.azure.com), go to **Enterprise applications** > **Application** > **Provisioning** and select **Authorize**.
 
    1. Azure portal redirects user to the Authorization URL (sign in page for the third party app).
 

articles/active-directory/app-provisioning/user-provisioning-sync-attributes-for-mapping.md

@@ -117,7 +117,7 @@ Get-AzureADUser -ObjectId 0ccf8df6-62f1-4175-9e55-73da9e742690 | Select -ExpandP
 ## Create an extension attribute using cloud sync
 Cloud sync will automatically discover your extensions in on-premises Active Directory when you go to add a new mapping.  Use the steps below to auto-discover these attributes and set up a corresponding mapping to Azure AD.
 
-1. Sign in to the Azure portal with a hybrid administrator account.
+1. Sign in to the [Azure portal](https://portal.azure.com) with a hybrid administrator account.
 2. Select Azure AD Connect.
 3. Select **Manage Azure AD cloud sync**.
 4. Select the configuration you wish to add the extension attribute and mapping.

articles/active-directory/app-provisioning/workday-integration-reference.md

@@ -419,7 +419,7 @@ Let's say you want to retrieve the following data sets from Workday and use them
 
 The above data sets aren't included by default. 
 To retrieve these data sets:
-1. Sign in to the Azure portal and open your Workday to AD/Azure AD user provisioning app. 
+1. Sign in to the [Azure portal](https://portal.azure.com) and open your Workday to AD/Azure AD user provisioning app. 
 1. In the Provisioning blade, edit the mappings and open the Workday attribute list from the advanced section. 
 1. Add the following attributes definitions and mark them as "Required". These attributes aren't mapped to any attribute in AD or Azure AD. They serve as signals to the connector to retrieve the Cost Center, Cost Center Hierarchy and Pay Group information. 
 
@@ -526,4 +526,3 @@ Use the steps to retrieve attributes associated with international job assignmen
 * [Learn how to configure Workday to Active Directory provisioning](../saas-apps/workday-inbound-tutorial.md)
 * [Learn how to configure write back to Workday](../saas-apps/workday-writeback-tutorial.md)
 * [Learn more about supported Workday Attributes for inbound provisioning](workday-attribute-reference.md)
-

articles/active-directory/app-provisioning/workday-retrieve-pronoun-information.md

@@ -61,7 +61,7 @@ Once you confirm that pronoun data is available in the *Get_Workers* response, g
 
 To retrieve pronouns from Workday, update your Azure AD provisioning app to query Workday using v38.1 of the Workday Web Services. We recommend testing this configuration first in your test/sandbox environment before implementing the change in production. 
 
-1. Sign in to the Azure portal as an administrator.
+1. Sign in to the [Azure portal](https://portal.azure.com) as an administrator.
 1. Open your *Workday to AD User provisioning* app OR *Workday to Azure AD User provisioning* app. 
 1. In the **Admin Credentials** section, update the **Tenant URL** to include the Workday Web Service version v38.1 as shown.
 

articles/active-directory/app-proxy/application-proxy-qlik.md

@@ -28,7 +28,7 @@ To publish QlikSense, you will need to publish two applications in Azure.
 Follow these steps to publish your app. For a more detailed walkthrough of steps 1-8, see [Publish applications using Azure AD Application Proxy](../app-proxy/application-proxy-add-on-premises-application.md). 
 
 
-1. Sign in to the Azure portal as a global administrator. 
+1. Sign in to the [Azure portal](https://portal.azure.com) as a global administrator.
 2. Select **Azure Active Directory** > **Enterprise applications**. 
 3. Select **Add** at the top of the blade. 
 4. Select **On-premises application**. 

articles/active-directory/authentication/concept-certificate-based-authentication-technical-deep-dive.md

@@ -293,7 +293,7 @@ For the first test scenario, configure the authentication policy where the Issue
 
 :::image type="content" border="true" source="./media/concept-certificate-based-authentication-technical-deep-dive/single-factor.png" alt-text="Screenshot of the Authentication policy configuration showing single-factor authentication required." lightbox="./media/concept-certificate-based-authentication-technical-deep-dive/single-factor.png":::  
 
-1. Sign in to the Azure portal as the test user by using CBA. The authentication policy is set where Issuer subject rule satisfies single-factor authentication.
+1. Sign in to the [Azure portal](https://portal.azure.com) as the test user by using CBA. The authentication policy is set where Issuer subject rule satisfies single-factor authentication.
 1. After sign-in was succeeds, click **Azure Active Directory** > **Sign-in logs**.
 
    Let's look closer at some of the entries you can find in the **Sign-in logs**.
@@ -320,7 +320,7 @@ For the next test scenario, configure the authentication policy where the **poli
 
 :::image type="content" border="true" source="./media/concept-certificate-based-authentication-technical-deep-dive/multifactor.png" alt-text="Screenshot of the Authentication policy configuration showing multifactor authentication required." lightbox="./media/concept-certificate-based-authentication-technical-deep-dive/multifactor.png":::  
 
-1. Sign in to the Azure portal using CBA. Since the policy was set to satisfy multifactor authentication, the user sign-in is successful without a second factor.
+1. Sign in to the [Azure portal](https://portal.azure.com) using CBA. Since the policy was set to satisfy multifactor authentication, the user sign-in is successful without a second factor.
 1. Click **Azure Active Directory** > **Sign-ins**.
 
    You'll see several entries in the Sign-in logs, including an entry with **Interrupted** status. 
@@ -391,4 +391,3 @@ For more information about how to enable **Trust multi-factor authentication fro
 - [How to migrate federated users](concept-certificate-based-authentication-migration.md)
 - [FAQ](certificate-based-authentication-faq.yml)
 - [Troubleshoot Azure AD CBA](troubleshoot-certificate-based-authentication.md)
-

articles/active-directory/authentication/how-to-certificate-based-authentication.md

@@ -55,7 +55,7 @@ You can configure CAs by using the Azure portal or PowerShell.
 
 To enable the certificate-based authentication and configure user bindings in the Azure portal, complete the following steps:
 
-1. Sign in to the Azure portal as a Global Administrator.
+1. Sign in to the [Azure portal](https://portal.azure.com) as a Global Administrator.
 1. Click **Azure Active Directory** > **Security**.
 
    :::image type="content" border="true" source="./media/how-to-certificate-based-authentication/certificate-authorities.png" alt-text="Screenshot of certification authorities.":::

articles/active-directory/authentication/howto-authentication-passwordless-security-key.md

@@ -72,7 +72,7 @@ There are some optional settings on the **Configure** tab to help manage how sec
 
 To remove a FIDO2 key associated with a user account, delete the key from the user’s authentication method.
 
-1. Sign in to the Azure portal and search for the user account from which the FIDO key is to be removed.
+1. Sign in to the [Azure portal](https://portal.azure.com) and search for the user account from which the FIDO key is to be removed.
 1. Select **Authentication methods** > right-click **FIDO2 security key** and click **Delete**. 
 
     ![View Authentication Method details](media/howto-authentication-passwordless-deployment/security-key-view-details.png)

articles/active-directory/authentication/howto-authentication-temporary-access-pass.md

@@ -76,7 +76,7 @@ These roles can perform the following actions related to a Temporary Access Pass
 - Authentication Administrators can create, delete, and view a Temporary Access Pass on members  (except themselves)
 - Global Reader can view the Temporary Access Pass details on the user (without reading the code itself).
 
-1. Sign in to the Azure portal by using one of the preceding roles. 
+1. Sign in to the [Azure portal](https://portal.azure.com) by using one of the preceding roles. 
 1. Select **Azure Active Directory**, browse to Users, select a user, such as *Chris Green*, then choose **Authentication methods**.
 1. If needed, select the option to **Try the new user authentication methods experience**.
 1. Select the option to **Add authentication methods**.