Merge pull request #245911 from alexbuckgit/alexbuckgit/docutune-autopr-20230721-203406-5077364-ignore-build

[BULK] DocuTune - Standardize formatting of Azure portal links (part 8)

Author: American-Dipper

articles/sentinel/normalization-schema-network.md

@@ -119,7 +119,7 @@ The following list mentions fields that have specific guidelines for Network Ses
 | Field               | Class       | Type       |  Description        |
 |---------------------|-------------|------------|--------------------|
 | **EventCount** | Mandatory | Integer | Netflow sources support aggregation, and the **EventCount** field should be set to the value of the Netflow **FLOWS** field. For other sources, the value is typically set to `1`. |
-| <a name="eventtype"></a> **EventType** | Mandatory | Enumerated | Describes the scenario reported by the record.<br><br> For Network Session records, the allowed values are:<br> - `EndpointNetworkSession`<br> - `NetworkSession` <br> - `L2NetworkSession`<br>- `IDS` <br> - `Flow`<br><br>For more information on event types, refer to the the [schema overview](#schema-overview) |
+| <a name="eventtype"></a> **EventType** | Mandatory | Enumerated | Describes the scenario reported by the record.<br><br> For Network Session records, the allowed values are:<br> - `EndpointNetworkSession`<br> - `NetworkSession` <br> - `L2NetworkSession`<br>- `IDS` <br> - `Flow`<br><br>For more information on event types, refer to the [schema overview](#schema-overview) |
 | <a name="eventsubtype"></a>**EventSubType** | Optional | String | Additional description of the event type, if applicable. <br> For Network Session records, supported values include:<br>- `Start`<br>- `End`<br><br>This is field is not relevant for `Flow` events. |
 | <a name="eventresult"></a>**EventResult** | Mandatory | Enumerated | If the source device does not provide an event result, **EventResult** should be based on the value of [DvcAction](#dvcaction).  If [DvcAction](#dvcaction) is `Deny`, `Drop`, `Drop ICMP`, `Reset`, `Reset Source`, or `Reset Destination`<br>, **EventResult** should be `Failure`. Otherwise, **EventResult** should be `Success`. |
 | **EventResultDetails** | Recommended | Enumerated | Reason or details for the result reported in the [EventResult](#eventresult) field. Supported values are:<br> - Failover <br> - Invalid TCP <br> - Invalid Tunnel<br> - Maximum Retry<br> - Reset<br> - Routing issue<br> - Simulation<br> - Terminated<br> - Timeout<br> - Transient error<br> - Unknown<br> - NA.<br><br>The original, source specific, value is stored in the [EventOriginalResultDetails](normalization-common-fields.md#eventoriginalresultdetails) field. |

articles/service-bus-messaging/includes/service-bus-create-namespace-portal.md

@@ -15,7 +15,7 @@ To begin using Service Bus messaging entities in Azure, you must first create a
 
 To create a namespace:
 
-1. Sign in to the [Azure portal](https://portal.azure.com)
+1. Sign in to the [Azure portal](https://portal.azure.com).
 2. In the left navigation pane of the portal, select **All services**, select **Integration** from the list of categories, hover the mouse over **Service Bus**, and then select **Create** on the Service Bus tile. 
 
     :::image type="content" source="./media/service-bus-create-namespace-portal/create-resource-service-bus-menu.png" alt-text="Image showing selection of Create a resource, Integration, and then Service Bus in the menu.":::

articles/service-bus-messaging/private-link-service.md

@@ -50,7 +50,7 @@ If you select the **Private access** option on the **Networking** page of the na
 
 If you already have an existing namespace, you can create a private endpoint by following these steps:
 
-1. Sign in to the [Azure portal](https://portal.azure.com). 
+1. Sign in to the [Azure portal](https://portal.azure.com).
 2. In the search bar, type in **Service Bus**.
 3. Select the **namespace** from the list to which you want to add a private endpoint.
 2. On the left menu, select **Networking** option under **Settings**.  

articles/service-bus-messaging/service-bus-quickstart-cli.md

@@ -17,7 +17,7 @@ This quickstart shows you how to create a Service Bus namespace and a queue usin
 ## Prerequisites
 If you don't have an Azure subscription, you can create a [free account][free account] before you begin.
 
-In this quickstart, you use Azure Cloud Shell that you can launch after sign into the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/cli/azure/install-azure-cli) and use Azure PowerShell on your machine. 
+In this quickstart, you use Azure Cloud Shell that you can launch after signing in to the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/cli/azure/install-azure-cli) and use Azure PowerShell on your machine. 
 
 ## Provision resources
 1. Sign in to the [Azure portal](https://portal.azure.com).

articles/service-bus-messaging/service-bus-quickstart-powershell.md

@@ -19,7 +19,7 @@ This quickstart shows you how to create a Service Bus namespace and a queue usin
 
 To complete this quickstart, make sure you have an Azure subscription. If you don't have an Azure subscription, you can create a [free account][] before you begin. 
 
-In this quickstart, you use Azure Cloud Shell that you can launch after sign into the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/powershell/azure/install-azure-powershell) and use Azure PowerShell on your machine. 
+In this quickstart, you use Azure Cloud Shell that you can launch after sign in to the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/powershell/azure/install-azure-powershell) and use Azure PowerShell on your machine. 
 
 
 ## Provision resources

articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-cli.md

@@ -26,7 +26,7 @@ Service Bus topics and subscriptions enable you to scale to process a large numb
 ## Prerequisites
 If you don't have an Azure subscription, you can create a [free account][free account] before you begin.
 
-In this quickstart, you use Azure Cloud Shell that you can launch after sign into the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/cli/azure/install-azure-cli) and use Azure PowerShell on your machine. 
+In this quickstart, you use Azure Cloud Shell that you can launch after sign in to the Azure portal. For details about Azure Cloud Shell, see [Overview of Azure Cloud Shell](../cloud-shell/overview.md). You can also [install](/cli/azure/install-azure-cli) and use Azure PowerShell on your machine. 
 
 ## Create a Service Bus topic and subscriptions
 Each [subscription to a topic](service-bus-messaging-overview.md#topics) can receive a copy of each message. Topics are fully protocol and semantically compatible with Service Bus queues. Service Bus topics support a wide array of selection rules with filter conditions, with optional actions that set or modify message properties. Each time a rule matches, it produces a message. To learn more about rules, filters, and actions, follow this [link](topic-filters.md).

articles/service-health/resource-health-faq.yml

@@ -65,7 +65,7 @@ sections:
       - question: |
           Where do I find Resource Health?
         answer: |
-          After you log in to the Azure portal, there are multiple ways you can access Resource Health:
+          After you sign in to the Azure portal, there are multiple ways you can access Resource Health:
           - Navigate to your resource. In the left-hand navigation, select **Resource health**
           - Go to the Azure Service Health blade.  In the left-hand navigation, select **Resource health**.
           

articles/site-recovery/azure-to-azure-tutorial-migrate.md

@@ -88,9 +88,9 @@ The following steps show how to prepare the virtual machine for the move using A
 
 ### Create the vault in any region, except the source region
 
-1. Sign in to the [Azure portal](https://portal.azure.com)
+1. Sign in to the [Azure portal](https://portal.azure.com).
 1. In search, type Recovery Services > click Recovery Services vaults
-1. In the Recovery Services vaults menu, click +Add.
+1. In the Recovery Services vaults menu, click **+ Add**.
 1. In **Name**, specify the friendly name **ContosoVMVault**. If you have more than one subscription, select the appropriate one.
 1. Create the resource group **ContosoRG**.
 1. Specify an Azure region. To check supported regions, see geographic availability in [Azure Site Recovery pricing details](https://azure.microsoft.com/pricing/details/site-recovery/).

articles/site-recovery/vmware-azure-deploy-configuration-server.md

@@ -32,14 +32,14 @@ Minimum hardware requirements for a configuration server are summarized in the f
 You must have a user with one of the following permissions set in Azure Active Directory (Azure AD) to register the configuration server with Azure Site Recovery services.
 
 1. The user must have an application developer role to create an application.
-    - To verify, sign in to the Azure portal.</br>
-    - Go to **Azure Active Directory** > **Roles and administrators**.</br>
+    - To verify, sign in to the Azure portal.
+    - Go to **Azure Active Directory** > **Roles and administrators**.
     - Verify that the application developer role is assigned to the user. If not, use a user with this permission or contact an [administrator to enable the permission](../active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md#assign-roles).
 
 2. If the application developer role can't be assigned, ensure that the **Users can register applications** flag is set as **true** for the user to create an identity. To enable these permissions:
-    - Sign in to the Azure portal.
-    - Go to **Azure Active Directory** > **User settings**.
-    - Under **App registrations**, **Users can register applications**, select **Yes**.
+    1. Sign in to the Azure portal.
+    1. Go to **Azure Active Directory** > **User settings**.
+    1. Under **App registrations**, **Users can register applications**, select **Yes**.
 
       ![Azure AD_application_permission](media/vmware-azure-deploy-configuration-server/AAD_application_permission.png)