Skip to content

Commit d2e017a

Browse files
authored
Merge branch 'main' into 2Apr-video-references
2 parents 09f562a + 2afe30c commit d2e017a

1,370 files changed

Lines changed: 27701 additions & 17687 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.openpublishing.redirection.json

Lines changed: 146 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,140 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/healthcare-apis/iot/concepts-machine-learning.md",
5+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-machine-learning",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/healthcare-apis/iot/concepts-power-bi.md",
10+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-power-bi",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/healthcare-apis/iot/concepts-teams.md",
15+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/concepts-teams",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/healthcare-apis/iot/configure-metrics.md",
20+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/configure-metrics",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/healthcare-apis/iot/deploy-arm-template.md",
25+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-arm-template",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md",
30+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/healthcare-apis/iot/deploy-choose-method.md",
35+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-choose-method",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/healthcare-apis/iot/deploy-json-powershell-cli.md",
40+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-json-powershell-cli",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/healthcare-apis/iot/deploy-manual-portal.md",
45+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/deploy-manual-portal",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/healthcare-apis/iot/device-messages-through-iot-hub.md",
50+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/device-messages-through-iot-hub",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/healthcare-apis/iot/frequently-asked-questions.md",
55+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/frequently-asked-questions",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/healthcare-apis/iot/get-started.md",
60+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/get-started",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/healthcare-apis/iot/git-projects.md",
65+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/git-projects",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md",
70+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-enable-diagnostic-settings",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md",
75+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-calculatedcontent-templates",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/healthcare-apis/iot/how-to-use-custom-functions.md",
80+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-custom-functions",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md",
85+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "articles/healthcare-apis/iot/how-to-use-mapping-debugger.md",
90+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-mapping-debugger",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md",
95+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "articles/healthcare-apis/iot/index.yml",
100+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/index",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md",
105+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "articles/healthcare-apis/iot/overview-of-device-mapping.md",
110+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-device-mapping",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md",
115+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path": "articles/healthcare-apis/iot/overview-of-samples.md",
120+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview-of-samples",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path": "articles/healthcare-apis/iot/overview.md",
125+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/overview",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path": "articles/healthcare-apis/iot/troubleshoot-errors-deployment.md",
130+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-deployment",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path": "articles/healthcare-apis/iot/troubleshoot-errors-logs.md",
135+
"redirect_url": "/previous-versions/azure/healthcare-apis/iot/troubleshoot-errors-logs",
136+
"redirect_document_id": false
137+
},
3138
{
4139
"source_path": "articles/sentinel/datalake/sentinel-mcp-chatgpt-connector.md",
5140
"redirect_url": "/azure/sentinel/datalake/sentinel-mcp-chatgpt-claude-connector",
@@ -516,6 +651,11 @@
516651
"redirect_url": "/azure/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-billing",
517652
"redirect_document_id": false
518653
},
654+
{
655+
"source_path": "articles/azure-functions/durable/durable-task-scheduler/quickstart-work-item-filtering-durable-task.md",
656+
"redirect_url": "/azure/durable-task/scheduler/quickstart-work-item-filtering-durable-task",
657+
"redirect_document_id": false
658+
},
519659
{
520660
"source_path": "articles/azure-functions/durable/durable-functions-cloud-backup.md",
521661
"redirect_url": "/azure/azure-functions/durable/durable-functions-fan-in-fan-out",
@@ -531,6 +671,11 @@
531671
"redirect_url": "/azure/azure-functions/durable/durable-functions-human-interaction",
532672
"redirect_document_id": false
533673
},
674+
{
675+
"source_path": "articles/azure-functions/durable/tutorial-durable-text-analysis-azure-files.md",
676+
"redirect_url": "/azure/azure-functions/durable-functions/tutorial-durable-text-analysis-azure-files",
677+
"redirect_document_id": false
678+
},
534679
{
535680
"source_path": "articles/expressroute/expressroute-troubleshooting-arp-resource-manager.md",
536681
"redirect_url": "/troubleshoot/azure/expressroute/expressroute-troubleshooting-arp-resource-manager",
@@ -7572,6 +7717,6 @@
75727717
"source_path": "articles/certification/edge-secured-core-get-certified.md",
75737718
"redirect_url": "/azure/certification/requirements-edge-secured-core",
75747719
"redirect_document_id": false
7575-
},
7720+
}
75767721
]
75777722
}

articles/active-directory-b2c/partner-onfido.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ REST API settings:
113113
#### Upload your files
114114

115115
1. Store the UI folder files in your blob container.
116-
2. [Use Azure Storage Explorer to manage Azure Managed Disks](/azure/virtual-machines/disks-use-storage-explorer-managed-disks) and access permissions.
116+
2. [Use Azure Storage Explorer to manage Azure managed disks](/azure/virtual-machines/disks-use-storage-explorer-managed-disks) and access permissions.
117117

118118
### Configure Azure AD B2C
119119

3.95 KB
Loading
15.2 KB
Loading
-41.9 KB
Loading

articles/api-center/register-discover-mcp-server.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about how Azure API Center can be a centralized registry for
44

55
ms.service: azure-api-center
66
ms.topic: concept-article
7-
ms.date: 02/20/2026
7+
ms.date: 04/02/2026
88

99
ms.collection: ce-skilling-ai-copilot
1010
ms.update-cycle: 180-days
@@ -126,6 +126,7 @@ To build MCP servers by using Azure compute services and register them in your A
126126
Set up your [API Center portal](set-up-api-center-portal.md) so that developers and other stakeholders in your organization can discover MCP servers in your API inventory. From the API Center portal, users can do the following:
127127
- Browse and filter MCP servers in the inventory.
128128
- For remote MCP servers, view details such as the URL endpoint of the MCP server and API definition, and install the MCP server in their Visual Studio Code environment.
129+
- A built-in MCP Inspector tool allows users to test MCP server endpoints and view the responses directly in the portal. On the **Options** tab of an MCP server details page, select **View documentation** to access the MCP Inspector.
129130

130131
:::image type="content" source="media/register-discover-mcp-server/mcp-server-portal-small.png" lightbox="media/register-discover-mcp-server/mcp-server-portal.png" alt-text="Screenshot of MCP server in API Center portal.":::
131132

articles/api-center/set-up-api-center-portal.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: How to set up the API Center portal, a managed website that enables
44

55
ms.service: azure-api-center
66
ms.topic: how-to
7-
ms.date: 02/25/2026
7+
ms.date: 04/02/2026
88
ms.update-cycle: 180-days
99

1010
ms.custom:
@@ -19,7 +19,7 @@ This article shows you how to set up and customize the *API Center portal* (prev
1919
The API Center portal supports and streamlines the work of developers who use and create APIs within your organization. Users with access can:
2020

2121
* **Search for APIs** by name or use AI-assisted semantic search.
22-
* **Filter APIs** by type or lifecycle stage.
22+
* **Filter APIs** by type, lifecycle stage, and other properties.
2323
* **View API details and definitions** including endpoints, methods, parameters, and response formats.
2424
* **Download API definitions** to their computer or open in Visual Studio Code.
2525
* **Try out APIs** with API key or OAuth 2.0 authentication.
@@ -66,6 +66,9 @@ After configuring access, open the API Center portal by selecting **View API Cen
6666

6767
By default, the portal home page is publicly reachable. If Microsoft Entra ID is configured for access, users must select **Sign-in** to access APIs. See [Enable sign-in to portal by Microsoft Entra users and groups](#enable-sign-in) for details on configuring user access.
6868

69+
* Add filters on the home page to display assets of certain types or that match certain metadata values.
70+
* Select an API or other registered asset to view its details, such as endpoints, methods, parameters, and response formats. You can also download API definitions or open them in Visual Studio Code.
71+
6972
<a id="enable-sign-in"></a>
7073
## Enable sign-in to portal by Microsoft Entra users and groups
7174

articles/api-management/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -745,7 +745,7 @@
745745
href: breaking-changes/git-configuration-retirement-march-2025.md
746746
- name: Direct management API retirement (March 2025)
747747
href: breaking-changes/direct-management-api-retirement-march-2025.md
748-
- name: Managed certificates suspension (August 2025 - March 2026)
748+
- name: Managed certificates suspension (August 2025 - June 2026)
749749
href: breaking-changes/managed-certificates-suspension-august-2025.md
750750
- name: ADAL-based identity provider retirement (September 2025)
751751
href: breaking-changes/identity-provider-adal-retirement-sep-2025.md

articles/api-management/api-management-capacity.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,7 +170,8 @@ Use capacity metrics for making decisions whether to scale an API Management ins
170170
+ Ignore sudden spikes that are most likely not related to an increase in load (see [Capacity metric behavior](#capacity-metric-behavior) section for explanation).
171171
+ As a general rule, upgrade or scale your instance when a capacity metric value exceeds **60% - 70%** for a long period of time (for example, 30 minutes). Different values may work better for your service or scenario.
172172
+ If your instance or workspace gateway is configured with only 1 unit, upgrade or scale it when a capacity metric value exceeds **40%** for a long period. This recommendation is based on the need to reserve capacity for guest OS updates in the underlying service platform.
173-
+ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric.
173+
+ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric.
174+
+ For classic tiers, discard the most recent 1‑minute data point when reading raw Azure API Management capacity metrics because the derived value can be invalid if source data isn’t available at aggregation time; do not base operational or scaling decisions on 1‑minute values — for autoscaling use average aggregation windows of 30 minutes or longer, evaluate sustained conditions before scaling, and annotate dashboards to exclude the final 1‑minute point so trends reflect reliable data.
174175

175176
> [!TIP]
176177
> If you are able to estimate your traffic beforehand, test your API Management instance or workspace gateway on workloads you expect. You can increase the request load gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.

articles/api-management/api-management-region-availability.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Information in the following table is updated regularly. Capacity availability i
5050
| South Africa North ||| | |
5151
| South Central US ||| | |
5252
| South India ||| | |
53-
| Sweden Central ||| | |
53+
| Sweden Central ||| | |
5454
| South India ||| | |
5555
| Switzerland North ||| | |
5656
| UAE North ||| | |
@@ -59,6 +59,7 @@ Information in the following table is updated regularly. Capacity availability i
5959
| West Europe ||| ||
6060
| West US ||| ||
6161
| West US 2 ||| | |
62+
| West US 3 | || | |
6263

6364
¹ New instance creation temporarily unavailable. See the capacity limitation note above.
6465

0 commit comments

Comments
 (0)