Merge pull request #266214 from mohitp930/mp2132024-validation-bulk

v-dirichards · web-flow · commit 614520294ea0 · 2024-03-05T16:49:45.000-06:00
Bulk - Fix validation issues
diff --git a/articles/azure-government/documentation-government-csp-list.md b/articles/azure-government/documentation-government-csp-list.md
@@ -469,6 +469,7 @@ Below you can find a list of all the authorized Cloud Solution Providers (CSPs),
 |[VVL Systems & Consulting, LLC](https://www.vvlsystems.com/)|
 |[Vistronix, LLC (ASRC Federal)](https://www.asrcfederal.com/asrc-federal-vistronix-cio-sp3/)|
 |[Vology Inc.](https://www.vology.com/)|
+|[VPLS](https://www.vpls.com/)|
 |[vSolvIT](https://www.vsolvit.com/)|
 |[Warren Averett Technology Group](https://warrenaverett.com/warren-averett-technology-group/)|
 |[Wintellisys, Inc.](https://wintellisys.com)|
@@ -486,7 +487,7 @@ Below you can find a list of all the authorized Cloud Solution Providers (CSPs),
 |[ZL Technologies Inc.](https://www.zlti.com/)|
 |[Zolon Tech](https://www.zolontech.com/)|
 |[Zones Inc](https://www.zones.com/site/home/index.html)|
-|[ZR Systems Group LLC](https://zrsystems.com)|
+
 
 
 ## Approved indirect providers
diff --git a/articles/communication-services/concepts/credentials-best-practices.md b/articles/communication-services/concepts/credentials-best-practices.md
@@ -5,7 +5,7 @@ author: petrsvihlik
 manager: soricos
 services: azure-communication-services
 
-ms.author: petrsvihlik
+ms.author: soricos
 ms.date: 01/30/2022
 ms.topic: conceptual
 ms.service: azure-communication-services
diff --git a/articles/communication-services/quickstarts/rooms/join-rooms-call.md b/articles/communication-services/quickstarts/rooms/join-rooms-call.md
@@ -6,7 +6,7 @@ services: azure-communication-services
 author: mrayyan
 manager: alexokun
 
-ms.author: t-siddiquim
+ms.author: alexokun
 ms.date: 07/20/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
diff --git a/articles/communication-services/samples/calling-hero-sample.md b/articles/communication-services/samples/calling-hero-sample.md
@@ -6,7 +6,7 @@ author: ddematheu2
 manager: chpalm
 services: azure-communication-services
 
-ms.author: ektrishi
+ms.author: chpalm
 ms.date: 06/30/2021
 ms.topic: overview
 ms.service: azure-communication-services
diff --git a/articles/machine-learning/prompt-flow/how-to-monitor-generative-ai-applications.md b/articles/machine-learning/prompt-flow/how-to-monitor-generative-ai-applications.md
@@ -4,7 +4,7 @@ titleSuffix: Azure Machine Learning
 description: Monitor the safety and quality of generative AI applications deployed to production on Azure Machine Learning.
 services: machine-learning
 author: buchananwp
-ms.author: willalpine
+ms.author: scottpolly
 ms.service: machine-learning
 ms.subservice: prompt-flow
 ms.reviewer: scottpolly
diff --git a/articles/private-5g-core/supi-concealment.md b/articles/private-5g-core/supi-concealment.md
@@ -93,9 +93,9 @@ The home network private keys are stored in Azure Key Vault.
 
 ## Create a user-assigned managed identity
 
-1. [Create a user-assigned managed identity](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity). Make a note of its UAMI resource ID.
+1. [Create a user-assigned managed identity](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp#create-a-user-assigned-managed-identity). Make a note of its UAMI resource ID.
 
-1. [Assign Key Vault Secrets User access](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/howto-assign-access-portal) to the Key Vault for the managed identity.
+1. [Assign Key Vault Secrets User access](/entra/identity/managed-identities-azure-resources/howto-assign-access-portal) to the Key Vault for the managed identity.
 
 1. Go to the **Mobile Network** resource in the portal and select **Identity** from the left-hand **Settings** menu. Select **Add** to add the user-assigned managed identity to the mobile network.
 
diff --git a/articles/sentinel/data-connectors/argos-cloud-security.md b/articles/sentinel/data-connectors/argos-cloud-security.md
@@ -87,7 +87,7 @@ Enter the information into the [ARGOS Sentinel](https://app.argos-security.io/ac
 
 New detections will automatically be forwarded.
 
-[Learn more about the integration](https://www.argos-security.io/resources#integrations)
+[Learn more about the integration](https://argos-security.io/2021/11/23/how-to-integrate-with-microsoft-sentinel-siem/)
 
 
 
diff --git a/articles/sentinel/data-connectors/cisco-stealthwatch.md b/articles/sentinel/data-connectors/cisco-stealthwatch.md
@@ -10,7 +10,7 @@ ms.author: cwatson
 
 # Cisco Stealthwatch connector for Microsoft Sentinel
 
-The [Cisco Stealthwatch](https://www.cisco.com/c/en/us/products/security/stealthwatch/index.html) data connector provides the capability to ingest [Cisco Stealthwatch events](https://www.cisco.com/c/dam/en/us/td/docs/security/stealthwatch/management_console/securit_events_alarm_categories/SW_7_2_1_Security_Events_and_Alarm_Categories_DV_1_0.pdf) into Microsoft Sentinel.
+The [Cisco Stealthwatch](https://www.cisco.com/c/en/us/products/security/stealthwatch/index.html) data connector provides the capability to ingest Cisco Stealthwatch events into Microsoft Sentinel.
 
 ## Connector attributes
 
diff --git a/articles/sentinel/data-connectors/symantec-vip.md b/articles/sentinel/data-connectors/symantec-vip.md
@@ -72,7 +72,7 @@ Configure the facilities you want to collect and their severities.
 
 3. Configure and connect the Symantec VIP
 
-[Follow these instructions](https://help.symantec.com/cs/VIP_EG_INSTALL_CONFIG/VIP/v134652108_v128483142/Configuring-syslog) to configure the Symantec VIP Enterprise Gateway to forward syslog. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.
+Configure the Symantec VIP Enterprise Gateway to forward syslog. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.
 
 
 
diff --git a/articles/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-functions.md b/articles/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-functions.md
@@ -10,14 +10,14 @@ ms.author: cwatson
 
 # Zero Networks Segment Audit (Function) (using Azure Functions) connector for Microsoft Sentinel
 
-The [Zero Networks Segment](https://zeronetworks.com/product/) Audit data connector provides the capability to ingest Audit events into Microsoft Sentinel through the REST API. Refer to API guide for more information. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
+The [Zero Networks Segment](https://zeronetworks.com/zero-networks-connect) Audit data connector provides the capability to ingest Audit events into Microsoft Sentinel through the REST API. Refer to API guide for more information. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
 
 ## Connector attributes
 
 | Connector attribute | Description |
 | --- | --- |
 | **Application settings** | APIToken<br/>WorkspaceID<br/>WorkspaceKey<br/>logAnalyticsUri (optional)<br/>uri<br/>tableName |
-| **Azure function app code** | https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/ZeroNetworks/SegmentFunctionConnector/AzureFunction_ZeroNetworks_Segment_Audit.zip |
+| **Azure function app code** | [Zero Networks Segment Audit (Function) (using Azure Functions) connector for Microsoft Sentinel](/azure/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-functions) |
 | **Log Analytics table(s)** | ZNSegmentAudit_CL<br/> |
 | **Data collection rules support** | Not currently supported |
 | **Supported by** | [Zero Networks](https://zeronetworks.com) |
@@ -85,7 +85,7 @@ Use the following step-by-step instructions to deploy the Zero Networks Segment
 
 > **NOTE:** You will need to [prepare VS code](/azure/azure-functions/functions-create-first-function-powershell#prerequisites) for Azure function development.
 
-1. Download the [Azure Function App](https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/ZeroNetworks/SegmentFunctionConnector/AzureFunction_ZeroNetworks_Segment_Audit.zip) file. Extract archive to your local development computer.
+1. Download the [Azure Function App](/azure/sentinel/data-connectors/zero-networks-segment-audit-function-using-azure-functions) file. Extract archive to your local development computer.
 2. Start VS Code. Choose File in the main menu and select Open Folder.
 3. Select the top level folder from extracted files.
 4. Choose the Azure icon in the Activity bar, then in the **Azure: Functions** area, choose the **Deploy to function app** button.
diff --git a/articles/site-recovery/site-recovery-iis.md b/articles/site-recovery/site-recovery-iis.md
@@ -106,7 +106,7 @@ If the connection string refers to the database virtual machine by using an IP a
 </configuration>
 ```
 
-To update the connection string in the web tier, add an [IIS connection update script](https://gallery.technet.microsoft.com/Update-IIS-connection-2579aadc) after Group 3 in the recovery plan.
+To update the connection string in the web tier, add an IIS connection update script after Group 3 in the recovery plan.
 
 #### Site bindings for the application
 Every site consists of binding information. The binding information includes the type of binding, the IP address at which the IIS server listens to the requests for the site, the port number, and the host names for the site. During the failover, you might need to update these bindings if there's a change in the IP address that's associated with them.
diff --git a/articles/site-recovery/site-recovery-runbook-automation.md b/articles/site-recovery/site-recovery-runbook-automation.md
@@ -188,9 +188,7 @@ In this example, a script takes the input of a Network Security Group (NSG) and
     }
     ```
 
-For each recovery plan, create independent variables so that you can reuse the script. Add a prefix by using the recovery plan name. 
-
-For a complete, end-to-end script for this scenario, review [this script](https://gallery.technet.microsoft.com/Add-Public-IP-and-NSG-to-a6bb8fee).
+For each recovery plan, create independent variables so that you can reuse the script. Add a prefix by using the recovery plan name.
 
 ### Use a complex variable to store more information
 
@@ -263,7 +261,6 @@ To deploy sample scripts to your Automation account, select the **Deploy to Azur
 - Learn about:
     - [Running failovers](site-recovery-failover.md)
 - Review:
-    -  [Azure Automation sample scripts](https://gallery.technet.microsoft.com/scriptcenter/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=SC%20Automation%20Product%20Team&f%5B0%5D.Text=SC%20Automation%20Product%20Team).
     - [A few tasks you might want to run during an Azure Site Recovery DR](https://github.com/WernerRall147/RallTheory/tree/main/AzureSiteRecoveryDRRunbooks).
 
 
diff --git a/articles/storage/queues/security-recommendations.md b/articles/storage/queues/security-recommendations.md
@@ -13,7 +13,7 @@ ms.custom: security-recommendations
 
 # Security recommendations for Queue Storage
 
-This article contains security recommendations for Queue Storage. Implementing these recommendations will help you fulfill your security obligations as described in our shared responsibility model. For more information on what Microsoft does to fulfill service provider responsibilities, see [Shared responsibilities for cloud computing](https://gallery.technet.microsoft.com/Shared-Responsibilities-81d0ff91/file/225366/1/Shared%20Responsibility%20for%20Cloud%20Computing-2019-10-25.pdf).
+This article contains security recommendations for Queue Storage. Implementing these recommendations will help you fulfill your security obligations as described in our shared responsibility model.
 
 Some of the recommendations included in this article can be automatically monitored by Microsoft Defender for Cloud. Microsoft Defender for Cloud is the first line of defense in protecting your resources in Azure. For information on Microsoft Defender for Cloud, see [What is Microsoft Defender for Cloud?](../../defender-for-cloud/defender-for-cloud-introduction.md).
 
diff --git a/articles/virtual-machines/linux/migrate-to-premium-storage-using-azure-site-recovery.md b/articles/virtual-machines/linux/migrate-to-premium-storage-using-azure-site-recovery.md
@@ -190,7 +190,7 @@ Site Recovery will create a VM instance whose type is the same as or similar to
 
 1. **Configure replicated VMs to the availability set if applicable**. Site Recovery does not support migrating VMs along with the availability set. Depending on the deployment of your replicated VM, do one of the following:
    * For a VM created through the classic deployment model: Add the VM to the availability set in the Azure portal. For detailed steps, go to [Add an existing virtual machine to an availability set](/previous-versions/azure/virtual-machines/linux/classic/configure-availability-classic).
-   * For a VM created through the Resource Manager deployment model: Save your configuration of the VM and then delete and re-create the VMs in the availability set. To do so, use the script at [Set Azure Resource Manager VM Availability Set](https://gallery.technet.microsoft.com/Set-Azure-Resource-Manager-f7509ec4). Before you run this script, check its limitations and plan your downtime.
+   * For a VM created through the Resource Manager deployment model: Save your configuration of the VM and then delete and re-create the VMs in the availability set.
 
 2. **Delete old VMs and disks**. Make sure that the Premium disks are consistent with source disks and that the new VMs perform the same function as the source VMs. Delete the VM and delete the disks from your source storage accounts in the Azure portal. If there's a problem in which the disk is not deleted even though you deleted the VM, see [Troubleshoot storage resource deletion errors](/troubleshoot/azure/virtual-machines/storage-resource-deletion-errors).
 
diff --git a/articles/virtual-machines/linux/tutorial-config-management.md b/articles/virtual-machines/linux/tutorial-config-management.md
@@ -111,7 +111,7 @@ To create a new update deployment, select **Schedule update deployment**. The **
 | Maintenance window |Number of minutes set for updates. The value can't be less than 30 minutes and no more than 6 hours |
 | Reboot control| Determines how reboots should be handled. Available options are:</br>Reboot if required (Default)</br>Always reboot</br>Never reboot</br>Only reboot - will not install updates|
 
-Update Deployments can also be created programmatically. To learn how to create an Update Deployment with the REST API, see [Software Update Configurations - Create](/rest/api/automation/softwareupdateconfigurations/create). There is also a sample runbook that can be used to create a weekly Update Deployment. To learn more about this runbook, see [Create a weekly update deployment for one or more VMs in a resource group](https://gallery.technet.microsoft.com/scriptcenter/Create-a-weekly-update-2ad359a1).
+Update Deployments can also be created programmatically. To learn how to create an Update Deployment with the REST API, see [Software Update Configurations - Create](/rest/api/automation/softwareupdateconfigurations/create). There is also a sample runbook that can be used to create a weekly Update Deployment.
 
 After you have completed configuring the schedule, click **Create** button and you return to the status dashboard.
 Notice that the **Scheduled** table shows the deployment schedule you created.
diff --git a/articles/virtual-machines/windows/migrate-to-premium-storage-using-azure-site-recovery.md b/articles/virtual-machines/windows/migrate-to-premium-storage-using-azure-site-recovery.md
@@ -192,7 +192,7 @@ Site Recovery will create a VM instance whose type is the same as or similar to
 
 1. **Configure replicated VMs to the availability set if applicable**. Site Recovery does not support migrating VMs along with the availability set. Depending on the deployment of your replicated VM, do one of the following:
    * For a VM created through the classic deployment model: Add the VM to the availability set in the Azure portal. For detailed steps, go to [Add an existing virtual machine to an availability set](/previous-versions/azure/virtual-machines/linux/classic/configure-availability-classic).
-   * For a VM created through the Resource Manager deployment model: Save your configuration of the VM and then delete and re-create the VMs in the availability set. To do so, use the script at [Set Azure Resource Manager VM Availability Set](https://gallery.technet.microsoft.com/Set-Azure-Resource-Manager-f7509ec4). Before you run this script, check its limitations and plan your downtime.
+   * For a VM created through the Resource Manager deployment model: Save your configuration of the VM and then delete and re-create the VMs in the availability set.
 
 2. **Delete old VMs and disks**. Make sure that the Premium disks are consistent with source disks and that the new VMs perform the same function as the source VMs. Delete the VM and delete the disks from your source storage accounts in the Azure portal. If there's a problem in which the disk is not deleted even though you deleted the VM, see [Troubleshoot storage resource deletion errors](/troubleshoot/azure/virtual-machines/storage-resource-deletion-errors).
 
diff --git a/articles/virtual-machines/windows/tutorial-config-management.md b/articles/virtual-machines/windows/tutorial-config-management.md
@@ -120,7 +120,7 @@ To schedule a new update deployment for the VM, select **Schedule update deploym
 
 After you have finished configuring the schedule, click **Create** to return to the status dashboard. The **Scheduled** table shows the deployment schedule you created.
 
-You can also create update deployments programmatically. To learn how to create an update deployment with the REST API, see [Software Update Configurations - Create](/rest/api/automation/softwareupdateconfigurations/create). There's also a sample runbook that you can use to create a weekly update deployment. To learn more about this runbook, see [Create a weekly update deployment for one or more VMs in a resource group](https://gallery.technet.microsoft.com/scriptcenter/Create-a-weekly-update-2ad359a1).
+You can also create update deployments programmatically. To learn how to create an update deployment with the REST API, see [Software Update Configurations - Create](/rest/api/automation/softwareupdateconfigurations/create). There's also a sample runbook that you can use to create a weekly update deployment.
 
 ### View results of an update deployment
 

Original file line number	Diff line number	Diff line change
`@@ -87,7 +87,7 @@ Enter the information into the [ARGOS Sentinel](https://app.argos-security.io/ac`
`87`	`87`
`88`	`88`	`New detections will automatically be forwarded.`
`89`	`89`
`90`		`-[Learn more about the integration](https://www.argos-security.io/resources#integrations)`
	`90`	`+[Learn more about the integration](https://argos-security.io/2021/11/23/how-to-integrate-with-microsoft-sentinel-siem/)`
`91`	`91`
`92`	`92`
`93`	`93`
Original file line number	Diff line number	Diff line change
`@@ -72,7 +72,7 @@ Configure the facilities you want to collect and their severities.`
`72`	`72`
`73`	`73`	`3. Configure and connect the Symantec VIP`
`74`	`74`
`75`		`-[Follow these instructions](https://help.symantec.com/cs/VIP_EG_INSTALL_CONFIG/VIP/v134652108_v128483142/Configuring-syslog) to configure the Symantec VIP Enterprise Gateway to forward syslog. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.`
	`75`	`+Configure the Symantec VIP Enterprise Gateway to forward syslog. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address.`
`76`	`76`
`77`	`77`
`78`	`78`