Skip to content

Commit 68cb9f5

Browse files
authored
Merge branch 'MicrosoftDocs:main' into main
2 parents 9a13386 + 059b785 commit 68cb9f5

333 files changed

Lines changed: 6696 additions & 3334 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.publish.config.json

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@
7070
},
7171
{
7272
"path_to_root": "azure_cli_scripts",
73-
"url": "https://github.com/ggailey777/azure-cli-samples",
73+
"url": "https://github.com/Azure-Samples/azure-cli-samples",
7474
"branch": "master",
7575
"branch_mapping": {}
7676
},
@@ -236,6 +236,12 @@
236236
"branch": "main",
237237
"branch_mapping": {}
238238
},
239+
{
240+
"path_to_root": "functions-flex-azure-files-samples",
241+
"url": "https://github.com/Azure-Samples/Azure-Functions-Flex-Consumption-with-Azure-Files-OS-Mount-Samples",
242+
"branch": "main",
243+
"branch_mapping": {}
244+
},
239245
{
240246
"path_to_root": "functions-quickstart-java-azd",
241247
"url": "https://github.com/Azure-Samples/azure-functions-java-flex-consumption-azd",

articles/active-directory-b2c/add-password-change-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,12 @@ ms.custom: sfi-image-nochange
2626

2727
[!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
2828

29-
You can configure Azure Active Directory B2C (Azure AD B2C) so that a user who is signed in with a local account can change their password without using email verification to prove their identity.
29+
You can configure Azure Active Directory B2C (Azure AD B2C) to allow users who are signed in with a local account to change their password without using email verification to prove their identity.
3030

3131
The password change flow involves the following steps:
3232

3333
1. The user signs in to their local account. If the session is still active, Azure AD B2C authorizes the user and skips to the next step.
34-
1. In **Old password**, the user verifies their old password. In **New password**, they create and confirm their new password.
34+
1. In **Old password**, the user verifies their current password. In **New password**, they create and confirm their new password.
3535

3636
![Screenshot that shows two numbered dialogs for making a password change.](./media/add-password-change-policy/password-change-flow.png)
3737

articles/active-directory-b2c/add-profile-editing-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ If you haven't already done so, [register a web application in Azure Active Dire
4444

4545
## Create a profile editing user flow
4646

47-
If you want to enable users to edit their profile in your application, you use a profile editing user flow.
47+
To enable users to edit their profile in your application, use a profile editing user flow.
4848

4949
1. In the menu of the Azure AD B2C tenant overview page, select **User flows**, and then select **New user flow**.
5050
1. On the **Create a user flow** page, select the **Profile editing** user flow.

articles/api-center/agent-to-agent-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure API Center provides a centralized platform for discovering, registering, a
2525

2626
**Governance and Security**: Addresses shadow IT and uncontrolled AI tool adoption by providing a governed channel for accessing AI agents, improving security and compliance.
2727

28-
**Integration with API Management**: AI agents can be placed behind an API Management gateway for private endpoints, enhanced security, and controlled access.
28+
**Integration with API Management**: AI agents can be placed behind an API Management gateway for private endpoints, enhanced security, and controlled access. A2A agent APIs in a linked API Management instance synchronize automatically to API Center.
2929

3030
**Customizable Metadata**: Organizations can define and store relevant metadata for each registered AI agent, facilitating filtering and searching.
3131

articles/api-center/synchronize-api-management-apis.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Although you can use the Azure CLI to [import](import-api-management-apis.md) AP
2525

2626
When you integrate an API Management instance as an API source, the following happens:
2727

28-
1. All APIs, and optionally API definitions (specs), from the API Management instance are added to the API center inventory. MCP servers in API Management are included in the APIs added to the inventory.
28+
1. All APIs, and optionally API definitions (specs), from the API Management instance are added to the API center inventory. MCP servers and A2A agent APIs in API Management are included in the APIs added to the inventory.
2929
1. You configure an [environment](key-concepts.md#environment) of type *Azure API Management* in the API center.
3030
1. An associated [deployment](key-concepts.md#deployment) is created for each synchronized API definition from API Management.
3131

articles/api-management/api-management-howto-use-managed-service-identity.md

Lines changed: 30 additions & 31 deletions
Large diffs are not rendered by default.

articles/api-management/cors-policy.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,12 +82,16 @@ The `cors` policy adds cross-origin resource sharing (CORS) support to an operat
8282
|----------|-----------------|--------------|-------------|
8383
|header|Specifies a header name.|At least one `header` element is required in `allowed-headers` if that section is present.|N/A|
8484

85+
The value `*` indicates all headers.
86+
8587
### expose-headers elements
8688

8789
|Name|Description|Required|Default|
8890
|----------|-----------------|--------------|-------------|
8991
|header|Specifies a header name.|At least one `header` element is required in `expose-headers` if that section is present.|N/A|
9092

93+
The value `*` indicates all headers.
94+
9195
## Usage
9296

9397
- [**Policy sections:**](./api-management-howto-policies.md#understanding-policy-configuration) inbound

articles/api-management/export-api-postman.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To enhance development of your APIs, you can export an API fronted in API Manage
4848

4949
API developers can rapidly iterate on API changes by using Postman's API testing, monitoring, and development capabilities.
5050

51-
APIs developed in Postman can then be exported and imported back into API Management as API revisions. This enables you to develop APIs in Postman and then deploy them to API Management for runtime access and management. [Learn more](https://learning.postman.com/docs/designing-and-developing-your-api/deploying-an-api/deploying-an-api-azure/)
51+
APIs developed in Postman can then be exported and imported back into API Management as API revisions. This enables you to develop APIs in Postman and then deploy them to API Management for runtime access and management. For more information, see [Deploy to Azure API Management from the Postman API Builder](https://learning.postman.com/v11/docs/integrations/available-integrations/azure-api-management/deploying-an-api-azure).
5252

5353

5454
> [!CAUTION]

0 commit comments

Comments
 (0)