Skip to content

Commit 1bb058b

Browse files
authored
Merge branch 'main' into pjw/second-pure
2 parents d194412 + 30f7aea commit 1bb058b

File tree

709 files changed

+8936
-21517
lines changed

Some content is hidden

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

709 files changed

+8936
-21517
lines changed

.openpublishing.redirection.json

Lines changed: 41 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6739,10 +6739,50 @@
67396739
"redirect_url": "/dotnet/maui/data-cloud/push-notifications",
67406740
"redirect_document_id": false
67416741
},
6742+
{
6743+
"source_path": "articles/work-with-styx-objects-and-indicators.md",
6744+
"redirect_url": "/azure/sentinel/work-with-styx-objects-indicators",
6745+
"redirect_document_id": false
6746+
},
67426747
{
67436748
"source_path": "articles/storage/files/geo-redundant-storage-for-large-file-shares.md",
67446749
"redirect_url": "/azure/storage/files/files-redundancy",
67456750
"redirect_document_id": false
6746-
}
6751+
},
6752+
{
6753+
"source_path": "articles/defender-for-iot/organizations/extra-deploy-enterprise-iot.md",
6754+
"redirect_url": "/azure/defender-for-iot/organizations/eiot-defender-for-endpoint",
6755+
"redirect_document_id": false
6756+
},
6757+
{
6758+
"source_path": "articles/sentinel/work-with-styx-objects-indicators.md",
6759+
"redirect_url": "/azure/sentinel/work-with-stix-objects-indicators",
6760+
"redirect_document_id": false
6761+
},
6762+
{
6763+
"source_path_from_root": "/articles/azure-functions/migration.md",
6764+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
6765+
"redirect_document_id": false
6766+
},
6767+
{
6768+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-assess.md",
6769+
"redirect_url": "/azure/azure-functions/migration/assess-lambda-workloads",
6770+
"redirect_document_id": false
6771+
},
6772+
{
6773+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-discover.md",
6774+
"redirect_url": "/azure/azure-functions/migration/discover-lambda-workloads",
6775+
"redirect_document_id": false
6776+
},
6777+
{
6778+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-migrate.md",
6779+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads",
6780+
"redirect_document_id": false
6781+
},
6782+
{
6783+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-overview.md",
6784+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
6785+
"redirect_document_id": false
6786+
},
67476787
]
67486788
}

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ You need to deploy an app, which serves as your external app. Your custom policy
9393
"requestId": "requestId",
9494
"userMessage" : "The access code you entered is incorrect. Please try again.",
9595
"developerMessage" : `The provided code ${req.body.accessCode} does not match the expected code for user.`,
96-
"moreInfo" :"https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
96+
"moreInfo" :"https://learn.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
9797
};
9898
res.status(409).send(errorResponse);
9999
}
@@ -138,7 +138,7 @@ You need to deploy an app, which serves as your external app. Your custom policy
138138
"requestId": "requestId",
139139
"userMessage": "The access code you entered is incorrect. Please try again.",
140140
"developerMessage": "The provided code 54321 does not match the expected code for user.",
141-
"moreInfo": "https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
141+
"moreInfo": "https://learn.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
142142
}
143143
```
144144
Your REST service can return HTTP 4xx status code, but the value of `status` in the JSON response must be `409`.

articles/active-directory-b2c/service-limits.md

Lines changed: 50 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -183,48 +183,63 @@ As a protection for our customers, Microsoft places some restrictions on telepho
183183

184184
| Region Code | Region Name | Limit per tenant per 60 minutes | Limit per tenant per 24 hours |
185185
|:----------- |:---------------------------------------------- |:------------------------------- | :----------------------------------------|
186-
| 228 | Togo | 10 | 30 |
187-
| 257 | Uzbek | 10 | 30 |
188-
| 970 | State of Plaestine | 10 | 30 |
189-
| 249 | Sudan | 10 | 30 |
190-
| 226 | Burina Faso | 10 | 30 |
191-
| 252 | Somalia | 10 | 30 |
192-
| 501 | Belize | 10 | 30 |
193-
| 855 | Cambodia | 50 | 200 |
194-
| 84 | Vietnam | 150 | 500 |
195-
| 94 | Sri Lanka | 100 | 500 |
196-
| 63 | Philippines | 50 | 200 |
197-
| 62 | Indonesia | 50 | 200 |
198-
| 7 | Russia | 100 | 1000 |
199-
| 258 | Mozambique | 50 | 200 |
200-
| 92 | Pakistan | 100 | 1000 |
201-
| 994 | Azerbaijan | 50 | 200 |
202-
| 880 | Bangladesh | 50 | 200 |
203186
| 20 | Egypt | 50 | 200 |
204-
| 260 | Zambia | 50 | 200 |
205-
| 502 | Guatemala | 10 | 50
206-
| 255 | Tanzania | 10 | 50
207-
| 261 | Madagascar | 10 | 30
208-
| 998 | Uzbekistan | 10 | 30
209-
| 223 | Mali | 20 | 100
210-
| 52 | Mexico | 100 | 500
211-
| 60 | Malaysia | 50 | 200 |
212-
| 221 | Senegal | 10 | 30 |
187+
| 211 | South Sudan | 10 | 30 |
188+
| 212 | Morocco | 20 | 100 |
213189
| 216 | Tunisia | 20 | 100 |
214-
| 503 | El Salvador | 10 | 30 |
190+
| 221 | Senegal | 10 | 30 |
191+
| 223 | Mali | 20 | 100 |
192+
| 224 | Guinea | 20 | 100 |
193+
| 225 | Ivory Coast| 10 | 30 |
194+
| 226 | Burina Faso | 10 | 30 |
195+
| 228 | Togo | 10 | 30 |
196+
| 233 | Ghana| 10 | 30 |
215197
| 234 | Nigeria | 20 | 100 |
198+
| 236 | Central African Republic  | 10 | 30 |
199+
| 238 | Cape Verde | 10 | 30 |
200+
| 249 | Sudan | 10 | 30 |
201+
| 251 | Ethiopia  | 10 | 30 |
202+
| 252 | Somalia | 10 | 30 |
203+
| 255 | Tanzania | 10 | 50 |
204+
| 256 | Uganda | 20 | 100 |
205+
| 257 | Uzbek | 10 | 30 |
206+
| 258 | Mozambique| 50 | 200 |
207+
| 260 | Zambia | 50 | 200 |
208+
| 261 | Madagascar | 10 | 30 |
209+
| 263 | Zimbabwe | 10 | 30 |
210+
| 265 | Malawi  | 10 | 30 |
211+
| 375 | Belarus   | 10 | 30 |
216212
| 386 | Slovenia | 10 | 50 |
213+
| 501 | Belize| 10 | 30 |
214+
| 502 | Guatemala | 10 | 50
215+
| 503 | El Salvador | 10 | 30 |
216+
| 52 | Mexico | 100 | 500
217+
| 58 | Venezuela| 10 | 30 |
217218
| 591 | Bolivia | 10 | 30 |
218-
| 263 | Zimbabwe | 10 | 30 |
219-
| 261 | Madagascar | 10 | 30 |
220-
| 995 | Georgia | 10 | 30 |
221-
| 993 | Turkmenistan | 10 | 30 |
222-
| 256 | Uganda | 20 | 100 |
223-
| 212 | Moroccoa | 20 | 100 |
219+
| 60 | Malaysia | 50 | 200 |
220+
| 62 | Indonesia | 50 | 200 |
221+
| 63 | Philippines | 50 | 200 |
222+
| 670 | East Timor (Timor-Leste)  | 10 | 30 |
223+
| 7 | Russia | 100 | 1000 |
224+
| 84 | Vietnam | 150 | 500 |
225+
| 855 | Cambodia | 50 | 200 |
224226
| 856 | Laos | 50 | 200 |
225-
| 224 | Guinea | 20 | 100 |
227+
| 880 | Bangladesh | 50 | 200 |
228+
| 92 | Pakistan| 100 | 1000 |
229+
| 93 | Afghanistan  | 10 | 30 |
230+
| 94 | Sri Lanka | 100 | 500 |
231+
| 95 | Myanmar (Burma) | 10 | 30 |
232+
| 961 | Lebanon  | 10 | 30 |
233+
| 967 | Yemen |10 | 30 |
234+
| 970 | State of Palestine| 10 | 30 |
235+
| 972 | Israel  | 50 | 200 |
236+
| 976 | Mongolia  | 10 | 30 |
226237
| 992 | Tajikistan | 10 | 30 |
227-
| 238 | Cape Verde | 10 | 30 |
238+
| 993 | Turkmenistan | 10 | 30 |
239+
| 994 | Azerbaijan | 50 | 200 |
240+
| 995 | Georgia | 10 | 30 |
241+
| 996 | Kyrgyzstan  | 10 | 30 |
242+
| 998 | Uzbekistan | 10 | 30
228243

229244
## Next steps
230245

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 02/04/2025
4+
ms.date: 04/01/2025
55
ms.service: azure-active-directory
66
ms.subservice: b2c
77
ms.topic: whats-new
@@ -17,6 +17,11 @@ manager: CelesteDG
1717

1818
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
1919

20+
## March 2025
21+
22+
### Updated articles
23+
- [Error codes: Azure Active Directory B2C](error-codes.md) - Updated error messages
24+
2025
## February 2025
2126

2227
### Updated articles
@@ -32,9 +37,3 @@ Welcome to what's new in Azure Active Directory B2C documentation. This article
3237

3338
- [Azure Active Directory B2C service limits and restrictions](service-limits.md) - Updated limits
3439

35-
## December 2024
36-
37-
### Updated articles
38-
39-
- [Tutorial: Configure Nok Nok S3 Authentication Suite with Azure AD B2C for FIDO passkey authentication](partner-nok-nok.md) - Updated scenarios
40-

articles/api-management/api-management-authenticate-authorize-azure-openai.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Options to authenticate and authorize to Azure OpenAI APIs using Az
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: concept-article
8-
ms.date: 01/23/2025
8+
ms.date: 04/01/2025
99
ms.author: danlep
1010
ms.collection: ce-skilling-ai-copilot
1111
---
@@ -101,6 +101,9 @@ Following are steps to configure your API Management instance to use a managed i
101101
</set-header>
102102
```
103103

104+
> [!TIP]
105+
> An alternative to using the `authentication-managed-identity` and `set-header` policies shown in this example is to configure a [backend](backends.md) resource that directs API requests to the Azure OpenAI Service endpoint. In the backend configuration, enable managed identity authentication to the Azure OpenAI Service. Azure API Management automates these steps when importing an API directly from Azure OpenAI Service. For more information, see [Import API from Azure OpenAI Service](azure-openai-api-from-specification.md#option-1-import-api-from-azure-openai-service).
106+
104107
## OAuth 2.0 authorization using identity provider
105108

106109
To enable more fine-grained access to OpenAPI APIs by particular users or clients, you can preauthorize access to the Azure OpenAI API using OAuth 2.0 authorization with Microsoft Entra ID or another identity provider. For background, see [Protect an API in Azure API Management using OAuth 2.0 authorization with Microsoft Entra ID](api-management-howto-protect-backend-with-aad.md).

articles/api-management/azure-openai-api-from-specification.md

Lines changed: 24 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: azure-api-management
55
author: dlepow
66
ms.author: danlep
77
ms.topic: how-to
8-
ms.date: 01/23/2025
8+
ms.date: 04/01/2025
99
ms.collection: ce-skilling-ai-copilot
1010
ms.custom: template-how-to, build-2024
1111
---
@@ -29,6 +29,10 @@ Learn more about managing AI APIs in API Management:
2929
- An Azure OpenAI resource with a model deployed. For more information about model deployment, see the [resource deployment guide](/azure/ai-services/openai/how-to/create-resource).
3030

3131
Make a note of the ID (name) of the deployment. You'll need it when you test the imported API in API Management.
32+
33+
> [!NOTE]
34+
> API Management policies such as [azure-openai-token-limit](azure-openai-token-limit-policy.md) and [azure-openai-emit-token-metric](azure-openai-emit-token-metric-policy.md) are supported for certain API endpoints exposed through specific Azure OpenAI Service models. For more information, see [Supported Azure OpenAI Service models](azure-openai-token-limit-policy.md#supported-azure-openai-service-models).
35+
3236
- Permissions to grant access to the Azure OpenAI resource from the API Management instance.
3337

3438
## Option 1. Import API from Azure OpenAI Service
@@ -39,11 +43,11 @@ You can import an Azure OpenAI API directly from Azure OpenAI Service to API Man
3943

4044
When you import the API, API Management automatically configures:
4145

42-
* Operations for each of the Azure OpenAI [REST API endpoints](/azure/ai-services/openai/reference).
46+
* Operations for each of the Azure OpenAI [REST API endpoints](/azure/ai-services/openai/reference)
4347
* A system-assigned identity with the necessary permissions to access the Azure OpenAI resource.
44-
* A [backend](backends.md) resource and [set-backend-service](set-backend-service-policy.md) policy that direct API requests to the Azure OpenAI Service endpoint.
45-
* An [authentication-managed-identity](authentication-managed-identity-policy.md) policy that can authenticate to the Azure OpenAI resource using the instance's system-assigned identity.
46-
* (optionally) Policies to help you monitor and manage token consumption by the Azure OpenAI API.
48+
* A [backend](backends.md) resource and a [set-backend-service](set-backend-service-policy.md) policy that direct API requests to the Azure OpenAI Service endpoint.
49+
* Authentication to the Azure OpenAI backend using the instance's system-assigned managed identity.
50+
* (optionally) Policies to help you monitor and manage the Azure OpenAI API.
4751

4852
To import an Azure OpenAI API to API Management:
4953

@@ -55,14 +59,19 @@ To import an Azure OpenAI API to API Management:
5559

5660
1. On the **Basics** tab:
5761
1. Select the Azure OpenAI resource that you want to import.
58-
1. Optionally select an **Azure OpenAI API version**. If you don't select one, the latest production-ready REST API version is used by default.
62+
1. Optionally select an **Azure OpenAI API version**. If you don't select one, the latest production-ready REST API version is used by default. Make a note of the version you selected. You'll need it to test the API.
5963
1. Enter a **Display name** and optional **Description** for the API.
6064
1. In **Base URL**, append a path that your API Management instance uses to access the Azure OpenAI API endpoints. If you enable **Ensure OpenAI SDK compatibility** (recommended), `/openai` is automatically appended to the base URL.
6165

6266
For example, if your API Management gateway endpoint is `https://contoso.azure-api.net`, set a **Base URL** similar to `https://contoso.azure-api.net/my-openai-api/openai`.
6367
1. Optionally select one or more products to associate with the API. Select **Next**.
64-
1. On the **Policies** tab, optionally enable policies to monitor and manage Azure OpenAI API token consumption.
65-
If selected, enter settings or accept defaults that define the `azure-openai-token-limit` and `azure-openai-emit-token-metric` policies for your API. You can also set or update the policy configuration later. Select **Review + Create**.
68+
1. On the **Policies** tab, optionally enable policies to monitor and manage Azure OpenAI API token consumption. You can also set or edit policies later.
69+
70+
If selected, enter settings or accept defaults that define the following policies (see linked articles for prerequisites and configuration details):
71+
* [Manage token consumption](azure-openai-token-limit-policy.md)
72+
* [Track token usage](azure-openai-emit-token-metric-policy.md)
73+
74+
Select **Review + Create**.
6675
1. After settings are validated, select **Create**.
6776

6877
## Option 2. Add an OpenAPI specification to API Management
@@ -71,13 +80,13 @@ Alternatively, manually download the OpenAPI specification for the Azure OpenAI
7180

7281
### Download the OpenAPI specification
7382

74-
Download the OpenAPI specification for the Azure OpenAI REST API, such as the [2024-02-01 GA version](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/AzureOpenAI/inference/stable/2024-02-01/inference.json).
83+
Download the OpenAPI specification for the Azure OpenAI REST API, such as the [2024-10-21 GA version](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/AzureOpenAI/inference/stable/2024-10-21/inference.json).
7584

7685
1. In a text editor, open the specification file that you downloaded.
7786
1. In the `servers` element in the specification, substitute the name of your Azure OpenAI Service endpoint in the placeholder values of `url` and `default` endpoint in the specification. For example, if your Azure OpenAI Service endpoint is `contoso.openai.azure.com`, update the `servers` element with the following values:
7887

79-
* url: `https://contoso.openai.azure.com/openai`
80-
* default endpoint: `contoso.openai.azure.com`
88+
* **url**: `https://contoso.openai.azure.com/openai`
89+
* **default** endpoint: `contoso.openai.azure.com`
8190

8291
```json
8392
[...]
@@ -93,7 +102,7 @@ Download the OpenAPI specification for the Azure OpenAI REST API, such as the [2
93102
],
94103
[...]
95104
```
96-
1. Make a note of the value of the API `version` in the specification. You'll need it to test the API. Example: `2024-02-01`.
105+
1. Make a note of the value of the API `version` in the specification. You'll need it to test the API. Example: `2024-10-21`.
97106

98107
### Add OpenAPI specification to API Management
99108

@@ -113,7 +122,7 @@ If you added the Azure OpenAI API from its OpenAPI specification, you need to co
113122

114123
## Test the Azure OpenAI API
115124

116-
To ensure that your Azure OpenAI API is working as expected, test it in the API Management test console. You need to supply a model deployment ID (name) configured in the Azure OpenAI resource to test the API.
125+
To ensure that your Azure OpenAI API is working as expected, test it in the API Management test console. You need to supply a model deployment ID (name) configured in the Azure OpenAI resource and the API version to test the API.
117126

118127
1. Select the API you created in the previous step.
119128
1. Select the **Test** tab.
@@ -128,7 +137,8 @@ To ensure that your Azure OpenAI API is working as expected, test it in the API
128137
> In the test console, API Management automatically populates an **Ocp-Apim-Subscription-Key** header, and configures the subscription key of the built-in [all-access subscription](api-management-subscriptions.md#all-access-subscription). This key enables access to every API in the API Management instance. Optionally display the **Ocp-Apim-Subscription-Key** header by selecting the "eye" icon next to the **HTTP Request**.
129138
1. Select **Send**.
130139

131-
When the test is successful, the backend responds with a successful HTTP response code and some data. Appended to the response is token usage data to help you monitor and manage your Azure OpenAI API consumption.
140+
When the test is successful, the backend responds with a successful HTTP response code and some data. Appended to the response is token usage data to help you monitor and manage your Azure OpenAI API token consumption.
141+
132142
:::image type="content" source="media/azure-openai-api-from-specification/api-response-usage.png" alt-text="Screenshot of token usage data in API response in the portal." :::
133143

134144
## Caching policies for Azure OpenAI APIs
@@ -138,5 +148,4 @@ In addition to the `azure-openai-token-limit` and `azure-openai-emit-token-metri
138148
* `azure-openai-semantic-cache-store`
139149
* `azure-openai-semantic-cache-lookup`
140150

141-
142151
[!INCLUDE [api-management-define-api-topics.md](../../includes/api-management-define-api-topics.md)]

0 commit comments

Comments
 (0)