Skip to content

Commit 2238cf1

Browse files
Merge pull request #54214 from PhilKang0704/2026_4-Monthly-broken-links-fix-pk-803
2026_4-Monthly-broken-links-fix-pk-803
2 parents 8cd977e + b507efc commit 2238cf1

5 files changed

Lines changed: 4 additions & 5 deletions

File tree

learn-pr/wwl-data-ai/build-backends-azure-functions/includes/7-exercise-create-mcp-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ The Model Context Protocol (MCP) is an open standard that defines how AI agents
33
In this exercise, you create an Azure Functions project with the MCP extension, define tool trigger functions for document processing, configure the MCP server settings, and test the server locally by connecting to it from GitHub Copilot in agent mode.
44

55
> [!NOTE]
6-
> This exercise uses the Azure Functions MCP extension, which is actively evolving. Visit the [Azure Functions MCP extension documentation](/azure/azure-functions/functions-bindings-mcp-trigger) for the most up-to-date setup instructions, API surface, and configuration options.
6+
> This exercise uses the Azure Functions MCP extension, which is actively evolving. Visit the [Azure Functions MCP extension documentation](/azure/azure-functions/functions-bindings-mcp-tool-trigger) for the most up-to-date setup instructions, API surface, and configuration options.
77
88
Tasks performed in this exercise:
99

learn-pr/wwl-data-ai/build-query-azure-database-postgresql/includes/2-explore-azure-database-postgresql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,4 +64,4 @@ When configuring Azure Database for PostgreSQL for your application, consider th
6464
- [Azure Database for PostgreSQL documentation](/azure/postgresql/)
6565
- [Service overview](/azure/postgresql/flexible-server/service-overview)
6666
- [Compute and storage options](/azure/postgresql/flexible-server/concepts-compute-storage)
67-
- [High availability concepts](/azure/postgresql/flexible-server/concepts-high-availability)
67+
- [High availability concepts](/azure/postgresql/high-availability/concepts-high-availability)

learn-pr/wwl-data-ai/event-driven-workflows-event-grid/includes/4-delivery-retry-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Event Grid delivers events by sending an HTTP POST request to the subscriber's e
66

77
Event Grid delivers one event at a time by default, with the payload as an array containing a single event. This default behavior ensures that each event is independently acknowledged and retried. For high-throughput AI workloads, you can enable output batching to group multiple events per delivery request, which reduces HTTP overhead and improves throughput.
88

9-
Event Grid provides at-least-once delivery, which means that subscribers might receive the same event more than once. This guarantee matters for AI pipelines because it means your handler endpoints must be [idempotent](/azure/architecture/building-blocks/idempotency). Use the event `id` field to detect and deduplicate repeated deliveries. For example, if your inference service receives the same event twice, it should check whether it already processed a result for that event ID before starting a new inference run.
9+
Event Grid provides at-least-once delivery, which means that subscribers might receive the same event more than once. This guarantee matters for AI pipelines because it means your handler endpoints must be idempotent. Use the event `id` field to detect and deduplicate repeated deliveries. For example, if your inference service receives the same event twice, it should check whether it already processed a result for that event ID before starting a new inference run.
1010

1111
## Examine the retry schedule and error handling
1212

learn-pr/wwl-data-ai/implement-vector-search-azure-cosmos-db/includes/3-execute-vector-similarity-queries.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -192,4 +192,3 @@ query = """
192192

193193
- [VectorDistance function reference](/azure/cosmos-db/nosql/query/vectordistance)
194194
- [Vector search in Azure Cosmos DB for NoSQL](/azure/cosmos-db/nosql/vector-search)
195-
- [Query items in Azure Cosmos DB for NoSQL using Python](/azure/cosmos-db/nosql/how-to-python-query-items)

learn-pr/wwl-data-ai/optimize-query-performance-azure-cosmos-db/includes/5-reduce-ru-costs-strategic-indexing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,4 +234,4 @@ This empirical approach validates that your indexing strategy achieves the expec
234234

235235
- [Indexing metrics in Azure Cosmos DB](/azure/cosmos-db/nosql/query-metrics)
236236
- [Optimize request cost in Azure Cosmos DB](/azure/cosmos-db/optimize-cost-reads-writes)
237-
- [Best practices for Azure Cosmos DB indexing](/azure/cosmos-db/nosql/best-practice-query#indexing-policy)
237+
- [Best practices for Azure Cosmos DB indexing](/azure/cosmos-db/index-policy)

0 commit comments

Comments
 (0)