Merge pull request #278279 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)

Author: Taojunshen

articles/ai-services/openai/assistants-reference-messages.md

@@ -36,7 +36,7 @@ Create a message.
 
 |Name | Type | Required | Description |
 |---  |---   |---       |---          |
-| `role` | string | Required | The role of the entity that is creating the message. Can be `user` or `assistant`. `assistant` indicates the message is sent by an actual user and should be used in most cases to represent user-generated messages. `assistant` indicates the message is generated by the assistant. Use this value to insert messages from the assistant into the conversation. |
+| `role` | string | Required | The role of the entity that is creating the message. Can be `user` or `assistant`. `user` indicates the message is sent by an actual user and should be used in most cases to represent user-generated messages. `assistant` indicates the message is generated by the assistant. Use this value to insert messages from the assistant into the conversation. |
 | `content` | string | Required | The content of the message. |
 | `file_ids` | array | Optional | A list of File IDs that the message should use. There can be a maximum of 10 files attached to a message. Useful for tools like retrieval and code_interpreter that can access and use files. |
 | `metadata` | map | Optional | Set of 16 key-value pairs that can be attached to an object. This can be useful for storing additional information about the object in a structured format. Keys can be a maximum of 64 characters long and values can be a maximum of 512 characters long. |
@@ -371,7 +371,7 @@ Represents a message within a thread.
 | `object` | string  |The object type, which is always thread.message.|
 | `created_at` | integer  |The Unix timestamp (in seconds) for when the message was created.|
 | `thread_id` | string  |The thread ID that this message belongs to.|
-| `role` | string  |The entity that produced the message. One of user or assistant.|
+| `role` | string  |The entity that produced the message. One of `user` or `assistant`.|
 | `content` | array  |The content of the message in array of text and/or images.|
 | `assistant_id` | string or null  |If applicable, the ID of the assistant that authored this message.|
 | `run_id` | string or null  |If applicable, the ID of the run associated with the authoring of this message.|

articles/aks/outbound-rules-control-egress.md

@@ -60,7 +60,7 @@ The following network and FQDN/application rules are required for an AKS cluster
 |----------------------------------|-----------------|----------|
 | **`*.hcp.<location>.azmk8s.io`** | **`HTTPS:443`** | Required for Node <-> API server communication. Replace *\<location\>* with the region where your AKS cluster is deployed. This is required for clusters with *konnectivity-agent* enabled. Konnectivity also uses Application-Layer Protocol Negotiation (ALPN) to communicate between agent and server. Blocking or rewriting the ALPN extension will cause a failure. This isn't required for [private clusters][private-clusters]. |
 | **`mcr.microsoft.com`**          | **`HTTPS:443`** | Required to access images in Microsoft Container Registry (MCR). This registry contains first-party images/charts (for example, coreDNS, etc.). These images are required for the correct creation and functioning of the cluster, including scale and upgrade operations.  |
-| **`*.data.mcr.microsoft.com`**   | **`HTTPS:443`** | Required for MCR storage backed by the Azure content delivery network (CDN). |
+| **`*.data.mcr.microsoft.com`**, **`mcr-0001.mcr-msedge.net`**   | **`HTTPS:443`** | Required for MCR storage backed by the Azure content delivery network (CDN). |
 | **`management.azure.com`**       | **`HTTPS:443`** | Required for Kubernetes operations against the Azure API. |
 | **`login.microsoftonline.com`**  | **`HTTPS:443`** | Required for Microsoft Entra authentication. |
 | **`packages.microsoft.com`**     | **`HTTPS:443`** | This address is the Microsoft packages repository used for cached *apt-get* operations.  Example packages include Moby, PowerShell, and Azure CLI. |

articles/azure-resource-manager/management/tag-support.md

@@ -418,7 +418,7 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | billingAccounts / appliedReservationOrders | No | No |
 > | billingAccounts / associatedTenants | No | No |
 > | billingAccounts / billingPermissions | No | No |
-> | billingAccounts / billingProfiles | No | No |
+> | billingAccounts / billingProfiles | Yes | Yes |
 > | billingAccounts / billingProfiles / billingPermissions | No | No |
 > | billingAccounts / billingProfiles / billingRoleAssignments | No | No |
 > | billingAccounts / billingProfiles / billingRoleDefinitions | No | No |
@@ -429,7 +429,7 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | billingAccounts / billingProfiles / invoices | No | No |
 > | billingAccounts / billingProfiles / invoices / pricesheet | No | No |
 > | billingAccounts / billingProfiles / invoices / transactions | No | No |
-> | billingAccounts / billingProfiles / invoiceSections | No | No |
+> | billingAccounts / billingProfiles / invoiceSections | Yes | Yes |
 > | billingAccounts / billingProfiles / invoiceSections / billingPermissions | No | No |
 > | billingAccounts / billingProfiles / invoiceSections / billingRoleAssignments | No | No |
 > | billingAccounts / billingProfiles / invoiceSections / billingRoleDefinitions | No | No |

articles/machine-learning/how-to-managed-network.md

@@ -1111,6 +1111,7 @@ The Azure Machine Learning managed VNet feature is free. However, you're charged
 * Using FQDN outbound rules increases the cost of the managed VNet because FQDN rules use Azure Firewall. For more information, see [Pricing](#pricing).
 * FQDN outbound rules only support ports 80 and 443.
 * If your compute instance is in a managed network and is configured for no public IP, use the `az ml compute connect-ssh` command to connect to it using SSH.
+* When using Managed Vnet, you can't deploy compute resources inside your custom Vnet. Compute resources can only be created inside the managed Vnet.
 
 ### Migration of compute resources