Skip to content

Commit 40486f6

Browse files
authored
Merge pull request #268106 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 7606a88 + 0ca27fb commit 40486f6

File tree

5 files changed

+9
-8
lines changed

5 files changed

+9
-8
lines changed

articles/ai-services/openai/concepts/understand-embeddings.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.custom:
1515

1616
# Understand embeddings in Azure OpenAI Service
1717

18-
An embedding is a special format of data representation that machine learning models and algorithms can easily use. The embedding is an information dense representation of the semantic meaning of a piece of text. Each embedding is a vector of floating-point numbers, such that the distance between two embeddings in the vector space is correlated with semantic similarity between two inputs in the original format. For example, if two texts are similar, then their vector representations should also be similar. Embeddings power vector similarity search in Azure Databases such as [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
18+
An embedding is a special format of data representation that machine learning models and algorithms can easily use. The embedding is an information dense representation of the semantic meaning of a piece of text. Each embedding is a vector of floating-point numbers, such that the distance between two embeddings in the vector space is correlated with semantic similarity between two inputs in the original format. For example, if two texts are similar, then their vector representations should also be similar. Embeddings power vector similarity search in Azure Databases such as [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md) , [Azure SQL Database](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications?view=azuresql&preserve-view=true#vector-search) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
1919

2020
## Embedding models
2121

@@ -38,4 +38,4 @@ An alternative method of identifying similar documents is to count the number of
3838
## Next steps
3939

4040
* Learn more about using Azure OpenAI and embeddings to perform document search with our [embeddings tutorial](../tutorials/embeddings.md).
41-
* Store your embeddings and perform vector (similarity) search using [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md), [Azure Cosmos DB for NoSQL](../../../cosmos-db/rag-data-openai.md) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).
41+
* Store your embeddings and perform vector (similarity) search using [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md), [Azure Cosmos DB for NoSQL](../../../cosmos-db/rag-data-openai.md) , [Azure SQL Database](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications?view=azuresql&preserve-view=true#vector-search) or [Azure Database for PostgreSQL - Flexible Server](../../../postgresql/flexible-server/how-to-use-pgvector.md).

articles/ai-services/openai/tutorials/embeddings.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ Learn more about Azure OpenAI's models:
5252
* Store your embeddings and perform vector (similarity) search using your choice of Azure service:
5353
* [Azure AI Search](../../../search/vector-search-overview.md)
5454
* [Azure Cosmos DB for MongoDB vCore](../../../cosmos-db/mongodb/vcore/vector-search.md)
55+
* [Azure SQL Database](/azure/azure-sql/database/ai-artificial-intelligence-intelligent-applications?view=azuresql&preserve-view=true#vector-search)
5556
* [Azure Cosmos DB for NoSQL](../../../cosmos-db/vector-search.md)
5657
* [Azure Cosmos DB for PostgreSQL](../../../cosmos-db/postgresql/howto-use-pgvector.md)
5758
* [Azure Cache for Redis](../../../azure-cache-for-redis/cache-tutorial-vector-similarity.md)

articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,17 +43,17 @@ Sign in to the Azure portal with this [Preview link](https://aka.ms/expressroute
4343

4444
1. Select the **Subscription** and **Resource Group** for the circuit. Then select the type of **Resiliency** for your setup.
4545

46-
**Maximum Resiliency (Recommended)** - This option provides the highest level of resiliency for your ExpressRoute circuit. It provides two ExpressRoute circuits with local redundancy in two different ExpressRoute locations.
46+
**Maximum Resiliency (Recommended)** - This option provides the highest level of resiliency for your ExpressRoute connectivity. It provides two ExpressRoute circuits with local redundancy in two different ExpressRoute locations.
4747

4848
> [!NOTE]
49-
> Provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for mission-critical and production workloads.
49+
> Maximum Resiliency provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for all critical and production workloads.
5050
5151
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of maximum resiliency for an ExpressRoute connection.":::
5252

5353
**Standard Resiliency** - This option provides a single ExpressRoute circuit with local redundancy at a single ExpressRoute location.
5454

5555
> [!NOTE]
56-
> Doesn't provide protection against location wide outages. This option is recommended for development/test environment and non-production workloads.
56+
> Standard Resiliency does not provide protection against location wide outages. This option is suitable for non-critical and non-production workloads.
5757
5858
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of standard resiliency for an ExpressRoute connection.":::
5959

articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,14 +77,14 @@ This article helps you create a connection to link a virtual network (virtual ne
7777
**Maximum resiliency (Recommended)** - This option provides the highest level of resiliency to your virtual network. It provides two redundant connections from the virtual network gateway to two different ExpressRoute circuits in different ExpressRoute locations.
7878

7979
> [!NOTE]
80-
> Provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for mission-critical and production workloads.
80+
> Maximum Resiliency provides maximum protection against location wide outages and connectivity failures in an ExpressRoute location. This option is strongly recommended for all critical and production workloads.
8181
8282
:::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of a virtual network gateway connected to two different ExpressRoute circuits.":::
8383

8484
**Standard resiliency** - This option provides a single redundant connection from the virtual network gateway to a single ExpressRoute circuit.
8585

8686
> [!NOTE]
87-
> Doesn't provide protection against location wide outages. This option is recommended for development/testing environment and non-production workloads.
87+
> Standard Resiliency does not provide protection against location wide outages. This option is suitable for non-critical and non-production workloads.
8888
8989
:::image type="content" source="./media/expressroute-howto-linkvnet-portal-resource-manager/standard-resiliency.png" alt-text="Diagram of a virtual network gateway connected to a single ExpressRoute circuit.":::
9090

articles/expressroute/expressroute-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Each ExpressRoute circuit consists of two connections to two Microsoft Enterpris
4848

4949
### Resiliency
5050

51-
Microsoft offers multiple ExpressRoute peering locations in many geopolitical regions. To ensure maximum resiliency, Microsoft recommends that you connect to two ExpressRoute circuits in two peering locations. For non-production development and test work loads, you can achieve standard resiliency by connecting to a single ExpressRoute circuit that offers redundant connections within a single peering location. The Azure portal provides a guided experience to help you create a resilient ExpressRoute configuration. For Azure PowerShell, CLI, ARM template, Terraform, and Bicep, maximum resiliency can be achieved by creating a second ExpressRoute circuit in a different ExpressRoute location and establishing a connection to it. For more information, see [Create maximum resiliency with ExpressRoute](expressroute-howto-circuit-portal-resource-manager.md?pivots=expressroute-preview).
51+
Microsoft offers multiple ExpressRoute peering locations in many geopolitical regions. To ensure maximum resiliency, Microsoft recommends that you connect to two ExpressRoute circuits in two peering locations. For non-production and non-critical workloads, you can achieve standard resiliency by connecting to a single ExpressRoute circuit that offers redundant connections within a single peering location. The Azure portal provides a guided experience to help you create a resilient ExpressRoute configuration. For Azure PowerShell, CLI, ARM template, Terraform, and Bicep, maximum resiliency can be achieved by creating a second ExpressRoute circuit in a different ExpressRoute location and establishing a connection to it. For more information, see [Create maximum resiliency with ExpressRoute](expressroute-howto-circuit-portal-resource-manager.md?pivots=expressroute-preview).
5252

5353
:::image type="content" source="./media/expressroute-howto-circuit-portal-resource-manager/maximum-resiliency.png" alt-text="Diagram of maximum resiliency for an ExpressRoute connection.":::
5454

0 commit comments

Comments
 (0)