Merge pull request #245742 from alexbuckgit/alexbuckgit/docutune-autopr-20230720-223327-5394967

AnnaMHuff · web-flow · commit d2e939bf6bfe · 2023-07-20T17:07:42.000-06:00
[BULK] DocuTune - Standardize formatting of Azure portal links (part 1)
diff --git a/articles/active-directory-b2c/partner-arkose-labs.md b/articles/active-directory-b2c/partner-arkose-labs.md
@@ -68,9 +68,9 @@ The following diagram illustrates how the Arkose Labs platform integrates with A
 
 ### Create an ArkoseSessionToken custom attribute
 
-To create a custom attribute:  
+To create a custom attribute:
 
-1. Go to the [Azure portal](https://ms.portal.azure.com/#home), then to **Azure AD B2C**.
+1. Go to the [Azure portal](https://portal.azure.com), then to **Azure AD B2C**.
 2. Select **User attributes**.
 3. Select **Add**.
 4. Enter **ArkoseSessionToken** as the attribute Name.
diff --git a/articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md b/articles/active-directory/app-provisioning/application-provisioning-config-problem-scim-compatibility.md
@@ -236,7 +236,7 @@ Below are sample requests to help outline what the sync engine currently sends v
 ## Upgrading from the older customappsso job to the SCIM job
 Following the steps below will delete your existing customappsso job and create a new SCIM job.
 
-1. Sign into the [Azure portal](https://portal.azure.com).
+1. Sign in to the [Azure portal](https://portal.azure.com).
 2. In the **Azure Active Directory > Enterprise Applications** section of the Azure portal, locate and select your existing SCIM application.
 3. In the **Properties** section of your existing SCIM app, copy the **Object ID**.
 4. In a new web browser window, go to https://developer.microsoft.com/graph/graph-explorer and sign in as the administrator for the Azure AD tenant where your app is added.
@@ -275,7 +275,7 @@ Following the steps below will delete your existing customappsso job and create
 ## Downgrading from the SCIM job to the customappsso job (not recommended)
  We allow you to downgrade back to the old behavior but don't recommend it as the customappsso does not benefit from some of the updates we make, and may not be supported forever. 
 
-1. Sign into the [Azure portal](https://portal.azure.com).
+1. Sign in to the [Azure portal](https://portal.azure.com).
 2. In the **Azure Active Directory > Enterprise Applications > Create application** section of the Azure portal, create a new **Non-gallery** application.
 3. In the **Properties** section of your new custom app, copy the **Object ID**.
 4. In a new web browser window, go to https://developer.microsoft.com/graph/graph-explorer and sign in as the administrator for the Azure AD tenant where your app is added.
diff --git a/articles/active-directory/develop/test-setup-environment.md b/articles/active-directory/develop/test-setup-environment.md
@@ -94,7 +94,7 @@ Replicating conditional access policies ensures you don't encounter unexpected b
 
 Viewing your production tenant conditional access policies may need to be performed by a company administrator.
 
-1. Sign into the [Azure portal](https://portal.azure.com) using your production tenant account.
+1. Sign in to the [Azure portal](https://portal.azure.com) using your production tenant account.
 1. Go to **Azure Active Directory** > **Enterprise applications** > **Conditional Access**.
 1. View the list of policies in your tenant. Click the first one.
 1. Navigate to **Cloud apps or actions**.
@@ -110,7 +110,7 @@ In a new tab or browser session, sign in to the [Azure portal](https://portal.az
 
 Replicating permission grant policies ensures you don't encounter unexpected prompts for admin consent when moving to production.
 
-1. Sign into the [Azure portal](https://portal.azure.com) using your production tenant account.
+1. Sign in to the [Azure portal](https://portal.azure.com) using your production tenant account.
 1. Click on **Azure Active Directory**.
 1. Go to **Enterprise applications**.
 1. From your production tenant, go to **Azure Active Directory** > **Enterprise applications** > **Consent and permissions** > **User consent** settings. Copy the settings there to your test tenant.
diff --git a/articles/active-directory/enterprise-users/licensing-service-plan-reference.md b/articles/active-directory/enterprise-users/licensing-service-plan-reference.md
@@ -23,7 +23,7 @@ ms.collection: M365-identity-device-management
 
 # Product names and service plan identifiers for licensing
 
-When managing licenses in the [Azure portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/LicensesMenuBlade/Products) or the [Microsoft 365 admin center](https://admin.microsoft.com), you see product names that look something like *Office 365 E3*. When you use PowerShell v1.0 cmdlets, the same product is identified using a specific but less friendly name: *ENTERPRISEPACK*. When using PowerShell v2.0 cmdlets or [Microsoft Graph](/graph/api/resources/subscribedsku), the same product is identified using a GUID value: *6fd2c87f-b296-42f0-b197-1e91e994b900*. The following table lists the most commonly used Microsoft online service products and provides their various ID values. These tables are for reference purposes in Azure Active Directory (Azure AD), part of Microsoft Entra, and are accurate only as of the date when this article was last updated. Microsoft will continue to make periodic updates to this document. 
+When [managing licenses in the Azure portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/LicensesMenuBlade/Products) or the [Microsoft 365 admin center](https://admin.microsoft.com), you see product names that look something like *Office 365 E3*. When you use PowerShell v1.0 cmdlets, the same product is identified using a specific but less friendly name: *ENTERPRISEPACK*. When using PowerShell v2.0 cmdlets or [Microsoft Graph](/graph/api/resources/subscribedsku), the same product is identified using a GUID value: *6fd2c87f-b296-42f0-b197-1e91e994b900*. The following table lists the most commonly used Microsoft online service products and provides their various ID values. These tables are for reference purposes in Azure Active Directory (Azure AD), part of Microsoft Entra, and are accurate only as of the date when this article was last updated. Microsoft will continue to make periodic updates to this document. 
 
 - **Product name**: Used in management portals
 - **String ID**: Used by PowerShell v1.0 cmdlets when performing operations on licenses or by the **skuPartNumber** property of the **subscribedSku** Microsoft Graph API
diff --git a/articles/active-directory/external-identities/direct-federation.md b/articles/active-directory/external-identities/direct-federation.md
@@ -191,7 +191,7 @@ Next, configure federation with the IdP configured in step 1 in Azure AD. You ca
 
 ### To configure federation in the Azure portal
 
-1. Sign in to the [Azure portal](https://portal.azure.com/) as an External Identity Provider Administrator or a Global Administrator. 
+1. Sign in to the [Azure portal](https://portal.azure.com) as an External Identity Provider Administrator or a Global Administrator. 
 2. In the left pane, select **Azure Active Directory**.
 3. Select **External Identities** > **All identity providers**.
 4. Select **New SAML/WS-Fed IdP**.
@@ -276,7 +276,7 @@ On the **All identity providers** page, you can view the list of SAML/WS-Fed ide
 You can remove your federation configuration. If you do, federation guest users who have already redeemed their invitations can no longer sign in. But you can give them access to your resources again by [resetting their redemption status](reset-redemption-status.md).
 To remove a configuration for an IdP in the Azure portal:
 
-1. Sign in to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
+1. Sign in to the [Azure portal](https://portal.azure.com). In the left pane, select **Azure Active Directory**.
 1. Select **External Identities**.
 1. Select **All identity providers**.
 1. Under **SAML/WS-Fed identity providers**, scroll to the identity provider in the list or use the search box.
diff --git a/articles/active-directory/manage-apps/f5-bigip-deployment-guide.md b/articles/active-directory/manage-apps/f5-bigip-deployment-guide.md
@@ -63,7 +63,7 @@ You can deploy a BIG-IP in different topologies. This guide focuses on a network
 
 To deploy BIG-IP VE from the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps).
 
-1. Log into the [Azure portal](https://portal.azure.com/#home) using an account with permissions to create VMs. For example, Contributor.
+1. Sign in to the [Azure portal](https://portal.azure.com/#home) using an account with permissions to create VMs, such as Contributor.
 2. In the top ribbon search box, type **marketplace**
 3. Select **Enter**.
 4. Type **F5** into the Marketplace filter.
diff --git a/articles/active-directory/saas-apps/tableau-online-provisioning-tutorial.md b/articles/active-directory/saas-apps/tableau-online-provisioning-tutorial.md
@@ -200,7 +200,7 @@ In June 2022, Tableau released a SCIM 2.0 connector. Completing the steps below
 >Be sure to note any changes that have been made to the settings listed above before completing the steps below. Failure to do so will result in the loss of customized settings.
 
 
-1. Sign into the [Azure portal](https://portal.azure.com).
+1. Sign in to the [Azure portal](https://portal.azure.com).
 
 
 1. Navigate to your current Tableau Cloud app under **Azure Active Directory > Enterprise Applications**.
diff --git a/articles/active-directory/saas-apps/workplace-by-facebook-provisioning-tutorial.md b/articles/active-directory/saas-apps/workplace-by-facebook-provisioning-tutorial.md
@@ -177,8 +177,8 @@ In December 2021, Facebook released a SCIM 2.0 connector. Completing the steps b
 > [!NOTE]
 > Be sure to note any changes that have been made to the settings listed above before completing the steps below. Failure to do so will result in the loss of customized settings. 
 
-1. Sign into the [Azure portal](https://portal.azure.com) 
-2. Navigate to your current Workplace by Facebook app under Azure Active Directory > Enterprise Applications
+1. Sign in to the [Azure portal](https://portal.azure.com).
+2. Navigate to your current Workplace by Facebook app under Azure Active Directory > Enterprise Applications.
 3. In the Properties section of your new custom app, copy the Object ID.
 
 	![Screenshot of Workplace by Facebook app in the Azure portal](./media/workplace-by-facebook-provisioning-tutorial/app-properties.png)
diff --git a/articles/ai-services/Anomaly-Detector/includes/create-anomaly-detector-resource.md b/articles/ai-services/Anomaly-Detector/includes/create-anomaly-detector-resource.md
@@ -12,7 +12,7 @@ ms.author: mbullwin
 
 ## Create an Anomaly Detector resource
 
-1. Sign into the <a href="https://portal.azure.com" target="_blank">Azure portal</a>.
+1. Sign in to the <a href="https://portal.azure.com" target="_blank">Azure portal</a>.
 1. Select <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesAnomalyDetector" target="_blank">Create Anomaly Detector</a> resource.
 1. Enter all required settings:
 
@@ -29,8 +29,5 @@ ms.author: mbullwin
 
     |Keys and Endpoint tab in the portal|Setting|Value|
     |--|--|--|
-    |**Overview**|Endpoint|Copy the endpoint. It looks similar to ` https://<your-resource-name>.cognitiveservices.azure.com/`|
+    |**Overview**|Endpoint|Copy the endpoint. It looks similar to `https://<your-resource-name>.cognitiveservices.azure.com/`|
     |**Keys**|API Key|Copy 1 of the two keys. It is a 32 alphanumeric-character string with no spaces or dashes, `xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`.|
-
-
-
