Merge pull request #250161 from MicrosoftDocs/JasonWHowell-patch-1

Fix build suggestions

Author: prmerger-automator[bot]

articles/cost-management-billing/costs/pricing-calculator.md

@@ -170,4 +170,4 @@ If you want to provide feedback about the Pricing Calculator, there's a link at
 ## Next steps
 
 - Estimate prices with the [Azure Pricing Calculator](https://azure.microsoft.com/pricing/calculator/).
-- Learn more about the [Azure Retail Prices API](/api/cost-management/retail-prices/azure-retail-prices).
+- Learn more about the [Azure Retail Prices API](/rest/api/cost-management/retail-prices/azure-retail-prices).

articles/cost-management-billing/manage/mca-enterprise-operations.md

@@ -33,7 +33,7 @@ The following changes apply to enterprise administrators on an Enterprise Agreem
 
 - A billing profile is created for your enrollment. You'll use the billing profile to manage billing for your organization, like your Enterprise Agreement enrollment. To learn more about billing profiles, [understand billing profiles](../understand/mca-overview.md#billing-profiles).
 - An invoice section is created for each department in your Enterprise Agreement enrollment. You'll use the invoice sections to manage your departments. You can create new invoice sections to set up additional departments. To learn more about invoice sections, see [understand invoice sections](../understand/mca-overview.md#invoice-sections).
-- You'll use the Azure subscription creator role on invoice sections to give others permission to create Azure subscription, like the accounts that were created in Enterprise Agreement enrollment.
+- You'll use the Azure subscription creator role on invoice sections to give others permission to create Azure subscriptions, like the accounts that were created in Enterprise Agreement enrollment.
 - You'll use the [Azure portal](https://portal.azure.com) to manage billing for your organization, instead of the Azure EA portal.
 
 You are given the following roles on the new billing account:
@@ -58,15 +58,15 @@ An invoice section is created for each department you had in your Enterprise Agr
 
 The accounts that were created in your Enterprise Agreement enrollment are not supported in the new billing account. The account's subscriptions belong to the respective invoice section for their department. Account owners can create and manage subscriptions for their invoice sections.
 
-To view aggregate cost for subscriptions that belonged to an account, you must set a cost center for each subscription. Then you can use the Azure usage and charges csv file to filter the subscriptions by the cost center.
+To view the aggregate cost for subscriptions that belonged to an account, you must set a cost center for each subscription. Then you can use the Azure usage and charges .csv file to filter the subscriptions by the cost center.
 
 ### Download usage and charges csv, price sheet, and tax documents
 
-A monthly invoice is generated for each billing profile in your billing account. For each invoice, you can download Azure usage and charges csv file, price sheet, and tax document (if applicable). You can also download Azure usage and charges csv file for the current month's charges.
+A monthly invoice is generated for each billing profile in your billing account. For each invoice, you can download the Azure usage and charges .csv file, price sheet, and tax document (if applicable). You can also download Azure usage and charges .csv file for the current month's charges.
 
-To learn how to download Azure usage and charges csv file, see [download usage for your Microsoft Customer Agreement](../understand/download-azure-daily-usage.md).
+To learn how to download Azure usage and charges .csv file, see [download usage for your Microsoft Customer Agreement](../understand/download-azure-daily-usage.md).
 
-To learn how to download price sheet, see [download pricing for your Microsoft Customer Agreement](ea-pricing.md).
+To learn how to download the price sheet, see [download pricing for your Microsoft Customer Agreement](ea-pricing.md).
 
 To learn how to download tax documents, see [view the tax documents for your Microsoft Customer Agreement](../understand/mca-download-tax-document.md#view-and-download-tax-documents).
 
@@ -82,19 +82,19 @@ Create an invoice section to organize your costs based on your needs, like depar
 
 ### Create a new account
 
-Assign users the Azure subscription creator role on invoice sections to give them permission to create Azure subscription, like the accounts that are created in Enterprise Agreement enrollment. For more information on assigning roles, see [Manage billing roles in the Azure portal](understand-mca-roles.md#manage-billing-roles-in-the-azure-portal)
+Assign users the Azure subscription creator role on invoice sections to give them permission to create Azure subscriptions, like the accounts that are created in Enterprise Agreement enrollment. For more information on assigning roles, see [Manage billing roles in the Azure portal](understand-mca-roles.md#manage-billing-roles-in-the-azure-portal)
 
 ## Changes for department administrators
 
 The following changes apply to department administrators on an Enterprise Agreement that got renewed to a Microsoft Customer Agreement.
 
 - An invoice section is created for each department in your Enterprise Agreement enrollment. You'll use the invoice section(s) to manage your department(s). To learn more about invoice sections, see [understand invoice sections](../understand/mca-overview.md#invoice-sections).
-- You'll use the Azure subscription creator role on the invoice section to give others permission to create Azure subscription, like the accounts that are created in Enterprise Agreement enrollment.
+- You'll use the Azure subscription creator role on the invoice section to give others permission to create Azure subscriptions, like the accounts that are created in Enterprise Agreement enrollment.
 - You'll use the Azure portal to manage billing for your organization, instead of the Azure EA portal.
 
 You are given the following roles on the new billing account:
 
-**Invoice section owner** - You are assigned the invoice section owner role on the invoice section that is created for the department(s) you had in Enterprise Agreement. The role lets you view and track charges, and control who can create Azure subscriptions and buy other products for the invoice section.
+**Invoice section owner** - You are assigned the invoice section owner role on the invoice section that is created for the department(s) you had in the Enterprise Agreement. The role lets you view and track charges and control who can create Azure subscriptions and buy other products for the invoice section.
 
 ### View charges for your department
 
@@ -108,36 +108,36 @@ To learn how to provide, access to your invoice section, see [manage billing rol
 
 ### Create a new account in your department
 
-Assign users the Azure subscription creator role on invoice section that's created for your department. For more information on assigning roles, see [Manage billing roles in the Azure portal](understand-mca-roles.md#manage-billing-roles-in-the-azure-portal)
+Assign users the Azure subscription creator role on the invoice section that's created for your department. For more information on assigning roles, see [Manage billing roles in the Azure portal](understand-mca-roles.md#manage-billing-roles-in-the-azure-portal)
 
 ### View charges for accounts in your departments
 
 The accounts that were created in your Enterprise Agreement enrollment are not supported in the new billing account. The account's subscriptions belong to the respective invoice section for their department. Account owners can create and manage subscriptions for their invoice sections.
 
-To view aggregate cost for subscriptions that belonged to an account in your department, you must set a cost center for each subscription. Then you can use the Azure usage and charges file to filter the subscriptions by the cost center.
+To view the aggregate cost for subscriptions that belonged to an account in your department, you must set a cost center for each subscription. Then you can use the Azure usage and charges file to filter the subscriptions by the cost center.
 
 ## Changes for account owners
 
 Account owners on the Enterprise Agreement get permission to create Azure subscriptions on the new billing account. Your existing Azure subscriptions belong to the invoice section that is created for your department. If your account doesn't belong to a department, your subscriptions belong to an invoice section named Default invoice section.
 
 To create additional Azure subscriptions, you are given the following role on the new billing account.
 
-**Azure subscription creator** - You are assigned the Azure subscription creator role on the invoice section that is created for your department in Enterprise Agreement. If your account doesn't belong to a department, you get Azure subscription creator role on a section named Default invoice section. The role lets you create Azure subscriptions for the invoice section.
+**Azure subscription creator** - You are assigned the Azure subscription creator role on the invoice section that is created for your department in the Enterprise Agreement. If your account doesn't belong to a department, you get Azure subscription creator role on a section named Default invoice section. The role lets you create Azure subscriptions for the invoice section.
 
 ### Create an Azure subscription
 
 You can create Azure subscriptions for your invoice section in the Azure portal. For more information, see [create an additional Azure subscription for Microsoft Customer Agreement](create-subscription.md)
 
 ### View charges for your account
 
-To view charges for subscriptions that belonged to an account, go to the [subscriptions page](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) in the Azure portal. The subscriptions page displays charges for all your subscription.
+To view charges for subscriptions that belonged to an account, go to the [subscriptions page](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) in the Azure portal. The subscriptions page displays charges for all your subscriptions.
 
 ### View charges for a subscription
 
 You can view charges for a subscription either on the [subscriptions page](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) or the Azure cost analysis. For more information on Azure cost analysis, see [explore and analyze costs with Cost analysis](../costs/quick-acm-cost-analysis.md).
 
 > [!NOTE]
-> To understand what could change upon migration from Enterprise Agreement to Microsoft Customer Agreement, refer [this](https://learn.microsoft.com/azure/cost-management-billing/costs/migrate-cost-management-api) document.
+> To understand what could change upon migration from Enterprise Agreement to Microsoft Customer Agreement, refer to the [Migrate Cost Management API](../costs/migrate-cost-management-api.md) article.
 
 ## Need help? Contact support
 

articles/data-factory/connector-office-365.md

@@ -13,7 +13,7 @@ ms.author: jianleishen
 # Copy and transform data from Microsoft 365 (Office 365) into Azure using Azure Data Factory or Synapse Analytics
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
-Azure Data Factory and Synapse Analytics pipelines integrate with [Microsoft Graph data connect](/graph/data-connect-concept-overview), allowing you to bring the rich organizational data in your Microsoft 365 (Office 365) tenant into Azure in a scalable way and build analytics applications and extract insights based on these valuable data assets. Integration with Privileged Access Management provides secured access control for the valuable curated data in Microsoft 365 (Office 365).  Please refer to [this link](/graph/data-connect-concept-overview) for an overview on Microsoft Graph data connect and refer to [this link](/graph/data-connect-policies#licensing) for licensing information.
+Azure Data Factory and Synapse Analytics pipelines integrate with [Microsoft Graph data connect](/graph/data-connect-concept-overview), allowing you to bring the rich organizational data in your Microsoft 365 (Office 365) tenant into Azure in a scalable way and build analytics applications and extract insights based on these valuable data assets. Integration with Privileged Access Management provides secured access control for the valuable curated data in Microsoft 365 (Office 365).  Please refer to [this link](/graph/data-connect-concept-overview) for an overview of Microsoft Graph data connect.
 
 This article outlines how to use the Copy Activity to copy data and Data Flow to transform data from Microsoft 365 (Office 365). For an introduction to copy data, read the [copy activity overview](copy-activity-overview.md). For an introduction to transforming data, read [mapping data flow overview](concepts-data-flow-overview.md).
 

articles/data-factory/tutorial-managed-virtual-network-on-premise-sql-server.md

@@ -213,17 +213,24 @@ the page.
 ## Creating Forwarding Rule to Endpoint
 
 1. Login and copy script [ip_fwd.sh](https://github.com/sajitsasi/az-ip-fwd/blob/main/ip_fwd.sh) to your backend server VMs. 
-2. Run the script on with the following options:<br/>
-    **sudo ./ip_fwd.sh -i eth0 -f 1433 -a <FQDN/IP> -b 1433**<br/>
-    <FQDN/IP> is your target SQL Server IP.<br/>
+
+2. Run the script with the following options:
+   
+    ```bash
+    sudo ./ip_fwd.sh -i eth0 -f 1433 -a <FQDN/IP> -b 1433
+    ```
+   Set the placeholder `<FQDN/IP>` is your target SQL Server IP.
 
     > [!NOTE] 
     > FQDN doesn't work for on-premises SQL Server unless you add a record in Azure DNS zone.
     
-3. Run below command and check the iptables in your backend server VMs. You can see one record in your iptables with your target IP.<br/>
-    **sudo iptables -t nat -v -L PREROUTING -n --line-number**
+4. Run the following command and check the iptables in your backend server VMs. You can see one record in your iptables with your target IP.<br/>
+
+   ```bash
+   sudo iptables -t nat -v -L PREROUTING -n --line-number**
+   ```
 
-    :::image type="content" source="./media/tutorial-managed-virtual-network/command-record-1.png" alt-text="Screenshot that shows the command record.":::
+   :::image type="content" source="./media/tutorial-managed-virtual-network/command-record-1.png" alt-text="Screenshot that shows the command record.":::
 
     > [!NOTE]
     > If you have more than one SQL Server or data sources, you need to define multiple load balancer rules and IP table records with different ports. Otherwise, there will be some conflict. For example,<br/>
@@ -245,7 +252,7 @@ data factory from the resources list.
 4. Select + **New** under **Managed private endpoints**.
 5. Select the **Private Link Service** tile from the list and select **Continue**.
 6. Enter the name of private endpoint and select **myPrivateLinkService** in private link service list.
-7. Add <FQDN>,<port> of your target on-premises SQL Server. By default, port is 1433.
+7. Add the `<FQDN>,<port>` of your target on-premises SQL Server. By default, port is 1433.
 
     :::image type="content" source="./media/tutorial-managed-virtual-network/private-endpoint-6.png" alt-text="Screenshot that shows the private endpoint settings.":::
 

articles/synapse-analytics/security/gateway-ip-addresses.md

@@ -14,7 +14,7 @@ ms.custom: references_regions
 
 The table below lists the individual Gateway IP addresses and also Gateway IP address ranges per region.
 
-Periodically, we will retire Gateways using old hardware and migrate the traffic to new Gateways as per the process outlined at [Azure SQL Database traffic migration to newer Gateways](https://learn.microsoft.com/azure/azure-sql/database/gateway-migration?view=azuresql&tabs=in-progress-ip). We strongly encourage customers to use the **Gateway IP address subnets** in order to not be impacted by this activity in a region.
+Periodically, we will retire Gateways using old hardware and migrate the traffic to new Gateways as per the process outlined at [Azure SQL Database traffic migration to newer Gateways](/azure/azure-sql/database/gateway-migration?view=azuresql&tabs=in-progress-ip&preserve-view=true). We strongly encourage customers to use the **Gateway IP address subnets** in order to not be impacted by this activity in a region.
 
 > [!IMPORTANT]  
 > - Logins for SQL Database or dedicated SQL pools (formerly SQL DW) in Azure Synapse can land on **any of the Gateways in a region**. For consistent connectivity to SQL Database or dedicated SQL pools (formerly SQL DW) in Azure Synapse, allow network traffic to and from **ALL** Gateway IP addresses and Gateway IP address subnets for the region.

articles/synapse-analytics/spark/apache-spark-concepts.md

@@ -31,7 +31,7 @@ Spark instances are created when you connect to a Spark pool, create a session,
 
 When you submit a second job, if there's capacity in the pool, the existing Spark instance also has capacity. Then, the existing instance will process the job. Otherwise, if capacity is available at the pool level, then a new Spark instance will be created.
 
-Billing for the instances starts when the Azure VM(s) starts. Billing for the Spark pool instances stops when pool instances changes to terminating. For more details on how Azure VMs are started, de-allocated see [States and billing status of Azure Virtual Machines](https://learn.microsoft.com/azure/virtual-machines/states-billing)
+Billing for the instances starts when the Azure VM(s) starts. Billing for the Spark pool instances stops when pool instances change to terminating. For more information on how Azure VMs are started and deallocated, see [States and billing status of Azure Virtual Machines](/azure/virtual-machines/states-billing).
 
 ## Examples
 

articles/synapse-analytics/sql/create-use-external-tables.md

@@ -36,7 +36,7 @@ The following table lists the data formats supported:
 
 ## Prerequisites
 
-Your first step is to create a database where the tables will be created. Before creating a database scoped credential, the database must have a master key to protect the credential. For more information on this, see [CREATE MASTER KEY (Transact-SQL)](https://learn.microsoft.com/sql/t-sql/statements/create-master-key-transact-sql). Then create the following objects that are used in this sample:
+Your first step is to create a database where the tables will be created. Before creating a database scoped credential, the database must have a master key to protect the credential. For more information on this, see [CREATE MASTER KEY (Transact-SQL)](/sql/t-sql/statements/create-master-key-transact-sql). Then create the following objects that are used in this sample:
 - DATABASE SCOPED CREDENTIAL `sqlondemand` that enables access to SAS-protected `https://sqlondemandstorage.blob.core.windows.net` Azure storage account.
 
     ```sql