Merge pull request #275658 from mohitp930/mp5162024-validation

Bulk update: Global effort to fix validation errors

Author: JamesJBarnett

.openpublishing.publish.config.json

@@ -135,9 +135,9 @@
       "branch_mapping": {}
     },
     {
-      "path_to_root": "ms-identity-dotnetcore-b2c-account-management",
+      "path_to_root": "ms-identity-dotnetcore-b2c-account-management-archive",
       "url": "https://github.com/Azure-Samples/ms-identity-dotnetcore-b2c-account-management",
-      "branch": "master",
+      "branch": "archive",
       "branch_mapping": {}
     },
     {

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-java-pivot.md

@@ -65,7 +65,7 @@ For OpenAI, use the following settings:
 | `OPENAI_API_KEY` | @Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/) |
 | `OPENAI_MODEL_NAME` | @Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/) |
 
-Once your app settings are saved, you can access the app settings in your code by referencing them in your application. Add the following code in the *[Application.java](http://Application.java)* file:
+Once your app settings are saved, you can access the app settings in your code by referencing them in your application. Add the following code in the *Application.java `http://Application.java`* file:
 
 For Azure OpenAI:
 
@@ -131,7 +131,7 @@ OpenAIClient client = new OpenAIClientBuilder()
     .buildClient();
 ```
 
-Once added, you see the following imports are added to the [Application.java](http://Application.java) file:
+Once added, you see the following imports are added to the Application.java `http://Application.java` file:
 
 ```java
 import com.azure.ai.openai.OpenAIClient;

articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-python-pivot.md

@@ -118,7 +118,7 @@ For OpenAI, use the following:
 |-|-|-|
 | `OPENAI_API_KEY` | @Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/) |
 
-Once your app settings are saved, you can [access the app settings](https://www.notion.so/Creating-Intelligent-App-on-App-Service-Python-757641ec4eda4dde88c9cad02d542170?pvs=21) in your code by referencing them in your application. Add the following to the *[app.py](http://app.py) file:*
+Once your app settings are saved, you can access the app settings in your code by referencing them in your application. Add the following to the *app.py `http://app.py` file:*
 
 For Azure OpenAI:
 ```python
@@ -147,7 +147,7 @@ To install LangChain, navigate to your application using Command Line or PowerSh
 pip install langchain-openai
 ```
 
-Once the package is installed, you can import and use LangChain. Update the *[app.py](http://app.py)* file with the following code:
+Once the package is installed, you can import and use LangChain. Update the * app.py `http://app.py`* file with the following code:
 
 ```python
 import os
@@ -160,7 +160,7 @@ from langchain_openai import AzureOpenAI~~
 
 ```
 
-After LangChain is imported into our file, you can add the code that will call to OpenAI with the LangChain invoke chat method. Update *[app.py](http://app.py)* to include the following code:
+After LangChain is imported into our file, you can add the code that will call to OpenAI with the LangChain invoke chat method. Update *app.py `http://app.py`* to include the following code:
 
 For Azure OpenAI, use the following code:
 

articles/app-service/troubleshoot-intermittent-outbound-connection-errors.md

@@ -98,7 +98,7 @@ Although PHP doesn't support connection pooling, you can try using persistent da
 
 * Other data Sources
 
-   * [PHP Connection Management](https://www.php.net/manual/en/pdo.connections.php)
+   * [PHP Connection Management](https://www.php.net/manual/pdo.connections.php)
 
 #### Python
 

articles/azure-vmware/configure-windows-server-failover-cluster.md

@@ -145,7 +145,7 @@ The following activities aren't supported and might cause WSFC node failover:
 ## Related information
 
 - [Failover Clustering in Windows Server](/windows-server/failover-clustering/failover-clustering-overview)
-- [Guidelines for Microsoft Clustering on vSphere (1037959) (vmware.com)](https://kb.vmware.com/s/article/1037959)
+- [Guidelines for Microsoft Clustering on vSphere (1037959) (vmware.com)](https://knowledge.broadcom.com/external/article?legacyId=1037959)
 - [About Setup for Failover Clustering and Microsoft Cluster Service (vmware.com)](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.mscs.doc/GUID-1A2476C0-CA66-4B80-B6F9-8421B6983808.html)
 - [vSAN 6.7 U3 - WSFC with Shared Disks & SCSI-3 Persistent Reservations (vmware.com)](https://blogs.vmware.com/virtualblocks/2019/08/23/vsan67-u3-wsfc-shared-disksupport/)
 - [Azure VMware Solution limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-vmware-solution-limits)

articles/cosmos-db/global-dist-under-the-hood.md

@@ -64,7 +64,7 @@ The service allows you to configure your Azure Cosmos DB databases with either a
 
 ## Conflict resolution
 
-Our design for the update propagation, conflict resolution, and causality tracking is inspired from the prior work on [epidemic algorithms](https://www.kth.se/social/upload/51647982f276546170461c46/4-gossip.pdf) and the [Bayou](https://people.cs.umass.edu/~mcorner/courses/691M/papers/terry.pdf) system. While the kernels of the ideas have survived and provide a convenient frame of reference for communicating the Azure Cosmos DB’s system design, they have also undergone significant transformation as we applied them to the Azure Cosmos DB system. This was needed, because the previous systems were designed neither with the resource governance nor with the scale at which Azure Cosmos DB needs to operate, nor to provide the capabilities (for example, bounded staleness consistency) and the stringent and comprehensive SLAs that Azure Cosmos DB delivers to its customers.  
+Our design for the update propagation, conflict resolution, and causality tracking is inspired from the prior work on [epidemic algorithms](https://www.kth.se/social/upload/51647982f276546170461c46/4-gossip.pdf) and the Bayou system. While the kernels of the ideas have survived and provide a convenient frame of reference for communicating the Azure Cosmos DB’s system design, they have also undergone significant transformation as we applied them to the Azure Cosmos DB system. This was needed, because the previous systems were designed neither with the resource governance nor with the scale at which Azure Cosmos DB needs to operate, nor to provide the capabilities (for example, bounded staleness consistency) and the stringent and comprehensive SLAs that Azure Cosmos DB delivers to its customers.  
 
 Recall that a partition-set is distributed across multiple regions and follows Azure Cosmos DB s (multi-region writes) replication protocol to replicate the data among the physical partitions comprising a given partition-set. Each physical partition (of a partition-set) accepts writes and serves reads typically to the clients that are local to that region. Writes accepted by a physical partition within a region are durably committed and made highly available within the physical partition before they are acknowledged to the client. These are tentative writes and are propagated to other physical partitions within the partition-set using an anti-entropy channel. Clients can request either tentative or committed writes by passing a request header. The anti-entropy propagation (including the frequency of propagation) is dynamic, based on the topology of the partition-set, regional proximity of the physical partitions, and the consistency level configured. Within a partition-set, Azure Cosmos DB follows a primary commit scheme with a dynamically selected arbiter partition. The arbiter selection is dynamic and is an integral part of the reconfiguration of the partition-set based on the topology of the overlay. The committed writes (including multi-row/batched updates) are guaranteed to be ordered. 
 

articles/postgresql/flexible-server/concepts-connection-libraries.md

@@ -29,7 +29,7 @@ Most language client libraries used to connect to Azure Database for PostgreSQL
 | Ruby | [Pg gem](https://deveiate.org/code/pg/) | Ruby Interface | [Download](https://rubygems.org/downloads/pg-0.20.0.gem) |
 | Go | [Package pq](https://godoc.org/github.com/lib/pq) | Pure Go postgres driver | [Install](https://github.com/lib/pq/blob/master/README.md) |
 | C\#/ .NET | [Npgsql](https://www.npgsql.org/) | ADO.NET Data Provider | [Download](https://dotnet.microsoft.com/download) |
-| ODBC | [psqlODBC](https://odbc.postgresql.org/) | ODBC Driver | [Download](https://www.postgresql.org/ftp/odbc/versions/) |
+| ODBC | [psqlODBC](https://odbc.postgresql.org/) | ODBC Driver | [Download](https://www.postgresql.org/ftp/odbc/releases/) |
 | C | [libpq](https://www.postgresql.org/docs/current/static/libpq.html) | Primary C language interface | Included |
 | C++ | [libpqxx](http://pqxx.org/) | New-style C++ interface | [Download](https://pqxx.org/libpqxx/) |
 

articles/postgresql/single-server/concepts-connection-libraries.md

@@ -30,7 +30,7 @@ Most language client libraries used to connect to PostgreSQL server are external
 | Ruby | [Pg gem](https://deveiate.org/code/pg/) | Ruby Interface | [Download](https://rubygems.org/downloads/pg-0.20.0.gem) |
 | Go | [Package pq](https://godoc.org/github.com/lib/pq) | Pure Go postgres driver | [Install](https://github.com/lib/pq/blob/master/README.md) |
 | C\#/ .NET | [Npgsql](https://www.npgsql.org/) | ADO.NET Data Provider | [Download](https://dotnet.microsoft.com/download) |
-| ODBC | [psqlODBC](https://odbc.postgresql.org/) | ODBC Driver | [Download](https://www.postgresql.org/ftp/odbc/versions/) |
+| ODBC | [psqlODBC](https://odbc.postgresql.org/) | ODBC Driver | [Download](https://www.postgresql.org/ftp/odbc/releases/) |
 | C | [libpq](https://www.postgresql.org/docs/9.6/static/libpq.html) | Primary C language interface | Included |
 | C++ | [libpqxx](http://pqxx.org/) | New-style C++ interface | [Download](https://pqxx.org/libpqxx/) |
 

articles/remote-rendering/overview/system-requirements.md

@@ -130,7 +130,7 @@ The following software must be installed:
 * [Visual Studio tools for Mixed Reality](/windows/mixed-reality/install-the-tools). Specifically, the following *Workload* installations are mandatory:
   * **Desktop development with C++**
   * **Universal Windows Platform (UWP) development** 
-* **Windows SDK 10.0.18362.0** [(download)](https://developer.microsoft.com/windows/downloads/windows-10-sdk)
+* **Windows SDK 10.0.18362.0** [(download)](https://developer.microsoft.com/windows/downloads/windows-sdk/)
 * To work with the samples repository:
   * **Git** [(download)](https://git-scm.com/downloads)
   * **Git LFS plugin** [(download)](https://git-lfs.github.com/)

articles/remote-rendering/quickstarts/native-cpp/hololens/deploy-native-cpp-openxr-tutorial.md

@@ -26,7 +26,7 @@ To get access to the Azure Remote Rendering service, you first need to [create a
 
 The following software must be installed:
 
-* Windows SDK 10.0.18362.0 [(download)](https://developer.microsoft.com/windows/downloads/windows-10-sdk)
+* Windows SDK 10.0.18362.0 [(download)](https://developer.microsoft.com/windows/downloads/windows-sdk/)
 * The latest version of Visual Studio 2022 [(download)](https://visualstudio.microsoft.com/vs/)
 * [Visual Studio tools for Mixed Reality](/windows/mixed-reality/install-the-tools). Specifically, the following *Workload* installations are mandatory:
   * **Desktop development with C++**