Merge pull request #109907 from craigcaseyMSFT/vcraic0401a

fix broken links from CATS report

Author: megvanhuygen

articles/active-directory/fundamentals/active-directory-ops-guide-auth.md

@@ -218,7 +218,7 @@ The final setting, `$ref-policy`, maps to the global policy statements file for
 The `apis` folder contains a folder for each API in the service instance, which contains the following items.
 
 * `apis\<api name>\configuration.json` - this is the configuration for the API and contains information about the backend service URL and the operations. This is the same information that would be returned if you were to call [Get a specific API](https://docs.microsoft.com/rest/api/apimanagement/2019-01-01/apis/get) with `export=true` in `application/json` format.
-* `apis\<api name>\api.description.html` - this is the description of the API and corresponds to the `description` property of the [API entity](https://docs.microsoft.com/java/api/com.microsoft.azure.storage.table._entity_property).
+* `apis\<api name>\api.description.html` - this is the description of the API and corresponds to the `description` property of the [API entity](https://docs.microsoft.com/java/api/com.microsoft.azure.storage.table.entityproperty).
 * `apis\<api name>\operations\` - this folder contains `<operation name>.description.html` files that map to the operations in the API. Each file contains the description of a single operation in the API, which maps to the `description` property of the [operation entity](https://docs.microsoft.com/rest/api/visualstudio/operations/list#operationproperties) in the REST API.
 
 ### groups folder

articles/api-management/api-management-configuration-repository-git.md

@@ -42,7 +42,7 @@ The following list provides the data sources in Azure that you can use with Azur
 
     This link provides instructions on how to use the [Azure Event Hubs Spark connector](https://github.com/Azure/azure-event-hubs-spark) from Azure Databricks to access data in Azure Event Hubs.
 
-- [Azure SQL Data Warehouse](/azure/databricks/data/data-sources/azure/sql-data-warehouse)
+- [Azure SQL Data Warehouse](/azure/synapse-analytics/sql-data-warehouse/)
 
     This link provides instructions on how to use the Azure SQL Data Warehouse connector to connect from Azure Databricks.
 

articles/azure-databricks/databricks-connect-to-data-sources.md

@@ -18,7 +18,7 @@ ms.author: femila
 
 # Develop with Storage API on Azure Government
 
-Azure Government uses the same underlying technologies as commercial Azure, enabling you to use the development tools you’re already familiar with.
+Azure Government uses the same underlying technologies as commercial Azure, enabling you to use the development tools you're already familiar with.
 To use these services in Azure Government, you must define different endpoint mappings, as shown below for the Storage service. 
 
 If you don't have an Azure Government subscription, create a [free account](https://azure.microsoft.com/global-infrastructure/government/request/) before you begin.
@@ -35,7 +35,7 @@ If you don't have an Azure Government subscription, create a [free account](http
 ### Getting Started with Storage Explorer
 1. Open the Azure Storage Explorer desktop application.
 
-2. You'll be prompted to add an Azure account; in the dropdown choose the “Azure US Government” option:
+2. You'll be prompted to add an Azure account; in the dropdown choose the "Azure US Government" option:
 
     ![storage1](./media/documentation-government-get-started-connect-with-storage-img1.png)
 3. Sign in to your Azure Government account and you can see all of your resources. The Storage Explorer should look similar to the screenshot below. Click on your Storage Account to see the blob containers, file shares, Queues, and Tables. 
@@ -52,10 +52,10 @@ If you don't have an Azure Government subscription, create a [free account](http
 * Download Visual Studio 2019
 
 ### Getting Started with Storage API
-One important difference to note when connecting with the Storage API is that the URL for storage is different than the URL for storage in commercial Azure – specifically, the domain ends with “core.usgovcloudapi.net”, rather than “core.windows.net”.
+One important difference to note when connecting with the Storage API is that the URL for storage is different than the URL for storage in commercial Azure – specifically, the domain ends with "core.usgovcloudapi.net", rather than "core.windows.net".
 
 These endpoint differences must be taken into account when you connect to storage in Azure Government with C#.
-1. Go to the [Azure Government portal](https://portal.azure.us) and select your storage account and then click the “Access Keys” tab:
+1. Go to the [Azure Government portal](https://portal.azure.us) and select your storage account and then click the "Access Keys" tab:
 
     ![storage4](./media/documentation-government-get-started-connect-with-storage-img4.png)
 2. Copy/paste the storage account connection string.
@@ -64,13 +64,13 @@ These endpoint differences must be taken into account when you connect to storag
 1. Open up Visual Studio and create a new project. Add a reference to the [WindowsAzure.Storage NuGet package](https://www.nuget.org/packages/WindowsAzure.Storage/). This NuGet package contains classes we will need to connect to your storage account.
 
 2. Add these two lines of C# code to connect:
-	```cs
-	var credentials = new StorageCredentials(storageAccountName, storageAccountKey);
+    ```cs
+    var credentials = new StorageCredentials(storageAccountName, storageAccountKey);
 
     var storageAccount = new CloudStorageAccount(credentials, "core.usgovcloudapi.net", useHttps: true);   
     ```
 
-    -   Notice on the second line we had to use a [particular constructor for the CloudStorageAccount](https://docs.microsoft.com/java/api/com.microsoft.azure.storage._cloud_storage_account.cloudstorageaccount) – enabling us to explicitly pass in the endpoint suffix of “core.usgovcloudapi.net”. This constructor is the **only difference** your code requires to connect to storage in Azure Government as compared with commercial Azure.
+    -   Notice on the second line we had to use a [particular constructor for the CloudStorageAccount](https://docs.microsoft.com/java/api/com.microsoft.azure.storage.cloudstorageaccount.cloudstorageaccount) – enabling us to explicitly pass in the endpoint suffix of "core.usgovcloudapi.net". This constructor is the **only difference** your code requires to connect to storage in Azure Government as compared with commercial Azure.
 
 3. At this point, we can interact with storage as we normally would. For example, if we want to retrieve a specific record from our table storage we could do it like this:
 
@@ -109,50 +109,50 @@ These endpoint differences must be taken into account when you connect to storag
                 this.email = email;
             }
 
-    	}
+        }
     ``` 
 3. Create a "test" class where we'll access Azure Table Storage using the Azure Storage API. 
  Copy and paste the code below, and **paste** your Storage Account connection string into the storageConnectionString variable. 
 
     ```java
     import com.microsoft.azure.storage.*;
     import com.microsoft.azure.storage.table.*;
-	
+    
     public class test {
 
-	    public static final String storageConnectionString = //Paste in your Storage Account connection string
-
-	    public static void main(String[] args) {
-
-		try
-		{
-		    // Retrieve storage account from connection-string.
-		    CloudStorageAccount storageAccount =
-			CloudStorageAccount.parse(storageConnectionString);
-
-		    // Create the table client.
-		    CloudTableClient tableClient = storageAccount.createCloudTableClient();
-
-		    // Create the table if it doesn't exist.
-		    String tableName = "Contacts";
-		    CloudTable cloudTable = tableClient.getTableReference(tableName);
-		    cloudTable.createIfNotExists();
-		    // Create a new customer entity.
-		    CustomerEntity customer1 = new CustomerEntity("Brown", "Walter");
-		    customer1.setEmail("[email protected]");
-
-		    // Create an operation to add the new customer to the people table.
-		    TableOperation insertCustomer1 = TableOperation.insertOrReplace(customer1);
-
-		    // Submit the operation to the table service.
-		    cloudTable.execute(insertCustomer1);
-		}
-		catch (Exception e)
-		{
-		    // Output the stack trace.
-		    e.printStackTrace();
-		}
-	  }	
+        public static final String storageConnectionString = //Paste in your Storage Account connection string
+
+        public static void main(String[] args) {
+
+        try
+        {
+            // Retrieve storage account from connection-string.
+            CloudStorageAccount storageAccount =
+            CloudStorageAccount.parse(storageConnectionString);
+
+            // Create the table client.
+            CloudTableClient tableClient = storageAccount.createCloudTableClient();
+
+            // Create the table if it doesn't exist.
+            String tableName = "Contacts";
+            CloudTable cloudTable = tableClient.getTableReference(tableName);
+            cloudTable.createIfNotExists();
+            // Create a new customer entity.
+            CustomerEntity customer1 = new CustomerEntity("Brown", "Walter");
+            customer1.setEmail("[email protected]");
+
+            // Create an operation to add the new customer to the people table.
+            TableOperation insertCustomer1 = TableOperation.insertOrReplace(customer1);
+
+            // Submit the operation to the table service.
+            cloudTable.execute(insertCustomer1);
+        }
+        catch (Exception e)
+        {
+            // Output the stack trace.
+            e.printStackTrace();
+        }
+      }    
     }   
     ```
 
@@ -161,29 +161,29 @@ These endpoint differences must be taken into account when you connect to storag
 2. The following code below connects to Azure Blob Storage and creates a Container using the Azure Storage API. 
     **Paste** your Azure Storage account connection string into the storageConnectionString variable below. 
 
-	```javascript
-	var azure = require('azure-storage');
-	var storageConnectionString = //Paste Azure Storage connection string here
-	var blobSvc = azure.createBlobService(storageConnectionString);
-	blobSvc.createContainerIfNotExists('testing', function(error, result, response){
-	if(!error){
-	// Container exists and is private
-	}
-	});
+    ```javascript
+    var azure = require('azure-storage');
+    var storageConnectionString = //Paste Azure Storage connection string here
+    var blobSvc = azure.createBlobService(storageConnectionString);
+    blobSvc.createContainerIfNotExists('testing', function(error, result, response){
+    if(!error){
+    // Container exists and is private
+    }
+    });
     ```
 
 #### Python
 1. Download the [Azure Storage SDK for Python](https://github.com/Azure/azure-storage-python).
 2. When using the Storage SDK for Python to connect to Azure Government, you **must separately define an "endpoint_suffix" parameter**. 
     **Paste** in your Azure storage account name and key in the placeholders below.
 
-	```python
-	# Create the BlockBlockService that is used to call the Blob service for the storage account
-	block_blob_service = BlockBlobService(account_name='#your account name', account_key='#your account key', endpoint_suffix="core.usgovcloudapi.net") 
-	container_name ='ml-gov-demo'
-	generator = block_blob_service.list_blobs(container_name)
-	for blob in generator:
-		print(blob.name)
+    ```python
+    # Create the BlockBlockService that is used to call the Blob service for the storage account
+    block_blob_service = BlockBlobService(account_name='#your account name', account_key='#your account key', endpoint_suffix="core.usgovcloudapi.net") 
+    container_name ='ml-gov-demo'
+    generator = block_blob_service.list_blobs(container_name)
+    for blob in generator:
+        print(blob.name)
     ```
 
 #### PHP
@@ -199,7 +199,7 @@ These endpoint differences must be taken into account when you connect to storag
      > You can find these endpoints by navigating to your Storage Account from the [portal](https://portal.azure.us). 
      > **Paste** in your storage account name, key, and service endpoint in the `connectionString` variable. 
      >
-	
+    
      ```php
      <?php
      require_once "vendor/autoload.php";

articles/azure-government/documentation-government-get-started-connect-to-storage.md

@@ -68,7 +68,7 @@ These are the URLs for storage accounts in Azure Government:
 >
 >
 
-For more information on APIs, see the [Cloud Storage Account Constructor](https://docs.microsoft.com/java/api/com.microsoft.azure.storage._cloud_storage_account.cloudstorageaccount).
+For more information on APIs, see the [Cloud Storage Account Constructor](https://docs.microsoft.com/java/api/com.microsoft.azure.storage.cloudstorageaccount.cloudstorageaccount).
 
 The endpoint suffix to use in these overloads is *core.usgovcloudapi.net*.
 

articles/azure-government/documentation-government-services-storage.md

@@ -27,7 +27,7 @@ The ML pipelines you create are visible to the members of your Azure Machine Lea
 
 ML pipelines use remote compute targets for computation and the storage of the intermediate and final data associated with that pipeline. They can read and write data to and from supported [Azure Storage](https://docs.microsoft.com/azure/storage/) locations.
 
-If you don’t have an Azure subscription, create a free account before you begin. Try the [free or paid version of Azure Machine Learning](https://aka.ms/AMLFree).
+If you don't have an Azure subscription, create a free account before you begin. Try the [free or paid version of Azure Machine Learning](https://aka.ms/AMLFree).
 
 ## Prerequisites
 
@@ -82,7 +82,7 @@ def_blob_store.upload_files(
     overwrite=True)
 ```
 
-A pipeline consists of one or more steps. A step is a unit run on a compute target. Steps might consume data sources and produce “intermediate” data. A step can create data such as a model, a directory with model and dependent files, or temporary data. This data is then available for other steps later in the pipeline.
+A pipeline consists of one or more steps. A step is a unit run on a compute target. Steps might consume data sources and produce "intermediate" data. A step can create data such as a model, a directory with model and dependent files, or temporary data. This data is then available for other steps later in the pipeline.
 
 To learn more about connecting your pipeline to your data, see the articles [How to Access Data](how-to-access-data.md) and [How to Register Datasets](how-to-create-register-datasets.md). 
 
@@ -114,7 +114,7 @@ output_data1 = PipelineData(
 
 If you have tabular data stored in a file or set of files, a [TabularDataset](https://docs.microsoft.com/python/api/azureml-core/azureml.data.tabulardataset?view=azure-ml-py) is an efficient alternative to a `DataReference`. `TabularDataset` objects support versioning, diffs, and summary statistics. `TabularDataset`s are lazily evaluated (like Python generators) and it's efficient to subset them by splitting or filtering. The `FileDataset` class provides similar lazily-evaluated data representing one or more files. 
 
-You create a `TabularDataset` using methods like [from_delimited_files](https://docs.microsoft.com/python/api/azureml-core/azureml.data.dataset_factory.tabulardatasetfactory?view=azure-ml-py#from-delimited-files-path--validate-true--include-path-false--infer-column-types-true--set-column-types-none--separator------header-true--partition-format-none-).
+You create a `TabularDataset` using methods like [from_delimited_files](https://docs.microsoft.com/python/api/azureml-core/azureml.data.dataset_factory.tabulardatasetfactory?view=azure-ml-py#from-delimited-files-path--validate-true--include-path-false--infer-column-types-true--set-column-types-none--separator------header-true--partition-format-none--support-multi-line-false-).
 
 ```python
 from azureml.data import TabularDataset
@@ -385,7 +385,7 @@ When you first run a pipeline, Azure Machine Learning:
 * Downloads the Docker image for each step to the compute target from the container registry.
 * Mounts the datastore if a `DataReference` object is specified in a step. If mount is not supported, the data is instead copied to the compute target.
 * Runs the step in the compute target specified in the step definition. 
-* Creates artifacts, such as logs, stdout and stderr, metrics, and output specified by the step. These artifacts are then uploaded and kept in the user’s default datastore.
+* Creates artifacts, such as logs, stdout and stderr, metrics, and output specified by the step. These artifacts are then uploaded and kept in the user's default datastore.
 
 ![Diagram of running an experiment as a pipeline](./media/how-to-create-your-first-pipeline/run_an_experiment_as_a_pipeline.png)
 

articles/machine-learning/how-to-create-your-first-pipeline.md

@@ -88,7 +88,7 @@ By using Site Recovery, you can replicate and recover VMs between any two region
 
 ### Does Site Recovery require internet connectivity?
 
-No, Site Recovery doesn't require internet connectivity. But it does require access to Site Recovery URLs and IP ranges, as mentioned in [networking in Azure VM disaster recovery](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-about-networking#outbound-connectivity-for-ip-address-ranges).
+No, Site Recovery doesn't require internet connectivity. But it does require access to Site Recovery URLs and IP ranges, as mentioned in [networking in Azure VM disaster recovery](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-about-networking#outbound-connectivity-for-urls).
 
 ### Can I replicate an application that has a separate resource group for separate tiers?
 

articles/site-recovery/azure-to-azure-common-questions.md

@@ -76,7 +76,7 @@ We recommend creating a network service endpoint in your virtual network for "St
 
 ### Network connectivity
 
-For Site Recovery replication to work, it needs the VM to provide outbound connectivity to specific URLs or IP ranges. You might have your VM behind a firewall or use network security group (NSG) rules to control outbound connectivity. If so, you might experience issues. To make sure all the URLs are connected, see [Outbound connectivity for Site Recovery URLs](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-about-networking#outbound-connectivity-for-ip-address-ranges).
+For Site Recovery replication to work, it needs the VM to provide outbound connectivity to specific URLs or IP ranges. You might have your VM behind a firewall or use network security group (NSG) rules to control outbound connectivity. If so, you might experience issues. To make sure all the URLs are connected, see [Outbound connectivity for Site Recovery URLs](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-about-networking#outbound-connectivity-for-urls).
 
 ## Error ID 153006 - No app-consistent recovery point available for the VM in the past "X" minutes
 

articles/site-recovery/azure-to-azure-troubleshoot-replication.md

@@ -22,7 +22,7 @@ as a String) and **RegistrationKey** (provided as a
 [PSCredential](/dotnet/api/system.management.automation.pscredential)) to onboard with Azure
 Automation. For details about obtaining those values, see [Onboarding machines for management by
 Azure Automation State Configuration - Secure
-registration](/azure/automation/automation-dsc-onboarding#secure-registration).
+registration](/azure/automation/automation-dsc-onboarding#onboarding-securely-using-registration).
 
 > [!NOTE]
 > You might encounter slightly different schema examples. The change in schema occurred in the October 2016 release. For details, see [Update from a previous format](#update-from-a-previous-format).