Merge branch 'main' into release-aio-m3

Author: v-alje

articles/api-management/api-management-policies.md

@@ -133,8 +133,8 @@ More information about policies:
 |---------|---------|---------|---------|---------|--------|
 |  [Trace](trace-policy.md) | Adds custom traces into the [request tracing](./api-management-howto-api-inspector.md) output in the test console, Application Insights telemetries, and resource logs. | Yes | Yes<sup>1</sup> | Yes | Yes |
 |  [Emit metrics](emit-metric-policy.md) | Sends custom metrics to Application Insights at execution. | Yes | Yes | Yes | Yes |
-|  [Emit Azure OpenAI token metrics](azure-openai-emit-token-metric-policy.md) | Sends metrics to Application Insights for consumption of large language model tokens through Azure OpenAI service APIs. | Yes | Yes | No | No |
-|  [Emit large language model API token metrics](llm-emit-token-metric-policy.md) | Sends metrics to Application Insights for consumption of large language model (LLM) tokens through LLM APIs. | Yes | Yes | No | No |
+|  [Emit Azure OpenAI token metrics](azure-openai-emit-token-metric-policy.md) | Sends metrics to Application Insights for consumption of large language model tokens through Azure OpenAI service APIs. | Yes | Yes | No | Yes |
+|  [Emit large language model API token metrics](llm-emit-token-metric-policy.md) | Sends metrics to Application Insights for consumption of large language model (LLM) tokens through LLM APIs. | Yes | Yes | No | Yes |
 
 
 <sup>1</sup> In the V2 gateway, the `trace` policy currently does not add tracing output in the test console.

articles/automation/how-to/region-mappings.md

@@ -10,7 +10,8 @@ ms.custom: references_regions
 # Supported regions for linked Log Analytics workspace
 
 > [!NOTE]
-> Start/Stop VMs v1 is retired and we recommend you to start using [Start/Stop VMs v2](../../azure-functions/start-stop-vms/overview.md) which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance.
+> - Automation Update Management has retired on **31 August 2024** and we recommend that you use Azure Update Manager. Follow the guidelines for [migration from Automation Update Management to Azure Update Manager](../../update-manager/migration-overview.md).
+> - Start/Stop VMs v1 is retired and we recommend you to start using [Start/Stop VMs v2](../../azure-functions/start-stop-vms/overview.md) which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance.
 
 [!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
 

articles/azure-app-configuration/feature-management-python-reference.md

@@ -179,7 +179,7 @@ The `feature_flags` provided to `FeatureManager` can either be the `AzureAppConf
 
 Creating a feature filter provides a way to enable features based on criteria that you define. To implement a feature filter, the `FeatureFilter` interface must be implemented. `FeatureFilter` has a single method named `evaluate`. When a feature specifies that it can be enabled for a feature filter, the `evaluate` method is called. If `evaluate` returns `true`, it means the feature should be enabled.
 
-The following snippet demonstrates how to add a customized feature filter `MyCriteriaFilter`.
+The following snippet demonstrates how to add a customized feature filter `MyCustomFilter`.
 
 ```python
 feature_manager = FeatureManager(feature_flags, feature_filters=[MyCustomFilter()])
@@ -280,10 +280,10 @@ Either a user can be specified directly in the `is_enabled` call or a `Targeting
 
 ```python
 # Directly specifying the user
-feature_manager = FeatureManager(feature_flags, "test_user")
+result = is_enabled(feature_flags, "test_user")
 
 # Using a TargetingContext
-feature_manager = FeatureManager(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
+result = is_enabled(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
 ```
 
 ### Targeting exclusion

articles/communication-services/concepts/voice-video-calling/troubleshoot-web-voip-quality.md

@@ -2,23 +2,19 @@
 title: Azure Communication Services troubleshooting VoIP call quality
 titleSuffix: An Azure Communication Services concept article
 description: Learn how to troubleshoot web VoIP call quality with Azure Communication Services.
-author: Cardiohater1
-ms.author: drohmetra
-manager: dacarte
+author: sloanster
+ms.author: micahvivion
 
 services: azure-communication-services
-ms.date: 3/6/2024
+ms.date: 10/17/2024
 ms.topic: conceptual
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
-
 # Troubleshoot VoIP call quality 
 
-This article describes how to troubleshoot and improve web Voice over Internet Protocol (VoIP) call quality in Azure Communication Services.
-
-Voice and video calling experiences are an essential communication tool for businesses, organizations, and individuals in today's world. However, customers can experience quality problems. Four network parameters can affect quality in calls: available bandwidth, round-trip time (RTT), packet loss, and jitter.
+This article describes how to troubleshoot and improve web Voice over Internet Protocol (VoIP) call quality in Azure Communication Services. Voice and video calling experiences are an essential communication tool for businesses, organizations, and individuals in today's world. However, customers can experience quality problems. Four network parameters can affect quality in calls: available bandwidth, round-trip time (RTT), packet loss, and jitter.
 
 If quality problems arise with VoIP calling in Azure Communication Services, follow the troubleshooting guidance in this article to ensure the best-possible user experience.
 
@@ -54,7 +50,7 @@ When a caller or callee reports audio interference or background noise on a call
 
 Also, make sure that the application you're using for web calling is hosted on the latest SDK. For more information, see [Azure Communication Services Calling Web (JavaScript) SDK - Release History](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md).
 
-## Pre-call checkups
+## Precall checkups
 
 When you're using the internet at various locations, you experience different internet speeds. Factors like the following examples can affect internet speed and reliability:
 
@@ -90,18 +86,14 @@ If you tried all the previous actions and still face quality problems, [create a
 
 ## End of Call Survey
 
-Enable the End of Call Survey feature to give Azure Communication Services users the option to submit qualitative feedback about their call experience.
+Enable the End of Call Survey feature to give Azure Communication Services users the option to submit qualitative feedback about their call experience. By enabling end of call survey you can learn more about end users calling experience and get insight of how you might improve that experience.
 
 For more information, see [End of Call Survey overview](end-of-call-survey-concept.md) and the related tutorial [Use the End of Call Survey to collect user feedback](../../tutorials/end-of-call-survey-tutorial.md).
 
 ## Related content
-
+- For detailed deep dive inspection on how to trouble shoot call quality and reliability see [here](../../resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/overview.md).
+- For information about Calling SDK error codes, see [Troubleshooting in Azure Communication Services](../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md). Use these codes to help determine why a call ended and how to mitigate the issue.
 - For information about using Call Quality Dashboard (CQD) to view interoperability call logs, see [Use CQD to manage call and meeting quality in Microsoft Teams](/microsoftteams/quality-of-experience-review-guide).
-
-- For information about Calling SDK error codes, see [Troubleshooting in Azure Communication Services](../../resources/troubleshooting/voice-video-calling/troubleshooting-codes.md). Use these codes to help determine why a call ended.
-
 - To ensure smooth functioning of the application and provide better user experience, app developers should follow a checklist. For more information, see the blog post [Checklist for advanced calling experiences in web browsers](https://techcommunity.microsoft.com/t5/azure-communication-services/checklist-for-advanced-calling-experiences-in-web-browsers/ba-p/3266312).
-
 - For more information about preparing your network or your customer's network, see [Network recommendations](network-requirements.md).
-
 - For best practices regarding Azure Communication Services web calling, see [Best practices: Azure Communication Services calling SDKs](../best-practices.md).

articles/communication-services/how-tos/cte-calling-sdk/includes/manage-calls/manage-calls-web.md

@@ -329,7 +329,7 @@ const localVideoStreams = call.localVideoStreams;
 
 ## Manage chat thread
 >[!IMPORTANT]
-> The optional Chat ID is only available in [1.29.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.29.1) or later of the Calling SDK for JavaScript. If you're using an earlier version, ensure you provide a unique thread ID manually.
+> The optional chat ID is only available in [1.29.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.29.1) or later of the Calling SDK for JavaScript. If you're using an earlier version, ensure you provide a unique chat ID manually.
 
 Providing a chat ID is optional for making group calls and adding participants to existing calls. Associated chat and call have a separate list of participants. Before adding participants to the call, add the user to the chat to provide the best user experience and satisfy information barrier requirements. Adding a user to the call without adding the user to the chat can result in exceptions if an information barrier is set up.
 
@@ -346,12 +346,12 @@ If Teams user stops call recording, the recording is placed into the chat associ
 
 Recommendations for the management of chat ID:
 - Escalation of the 1:1 phone call by adding another phone participant:
-  * Method `addParticipant` allows you to provide optional parameter thread ID. If the parameter isn't provided, then a new group chat is created, and all participants are added to the call and chat participants list. If the parameter is provided, then Teams users can see ongoing call associated to this group chat in Teams app. You can create new group chat via Graph API.
+  * Method `addParticipant` allows you to provide optional parameter chat ID. If the parameter isn't provided, then a new group chat is created, and all participants are added to the call and chat participants list. If the parameter is provided, then Teams users can see ongoing call associated to this group chat in Teams app. You can create new group chat via Graph API.
     ```js
     addParticipant(participant: MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)
     ```
 - Start group call with single Microsoft 365 user and multiple phone participants:
-  * Method `startCall` API allows you to start a group call with multiple participants and optionally provide thread ID. If the parameter isn't provided, then a new group chat is created, and all Microsoft 365 participants are added to the call and chat participants list. If the parameter is provided, then Teams users can see ongoing call associated to this group chat in Teams app. You can create new group chat via Graph API.
+  * Method `startCall` API allows you to start a group call with multiple participants and optionally provide chat ID. If the parameter isn't provided, then a new group chat is created, and all Microsoft 365 participants are added to the call and chat participants list. If the parameter is provided, then Teams users can see ongoing call associated to this group chat in Teams app. You can create new group chat via Graph API.
     ```js
     startCall(MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)[])
     ```
@@ -361,4 +361,4 @@ Recommendations for the management of chat ID:
     ```js
     startCall(MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)[])
     ```
-  * If desired, the developer can provide a unique thread ID to start the group call or add participants. In this case, the ACS Calling SDK will use the given thread ID to create the group call. A chat thread is created for the Teams users and this thread is associated to the group call for users in Teams app. This allows them to chat during the call. Chat thread management can be done via [Graph API](/graph/api/group-post-threads)
+  * If desired, the developer can provide a unique chat ID to start the group call or add participants. In this case, the ACS Calling SDK will use the given chat ID to create the group call. A chat thread is created for the Teams users and this thread is associated to the group call for users in Teams app. This allows them to chat during the call. Chat thread management can be done via [Graph API](/graph/api/group-post-threads)

articles/digital-twins/concepts-models.md

@@ -166,7 +166,7 @@ Sometimes, you might want to define a relationship without a specific target, so
 
 Here's an example of a relationship on a DTDL model that doesn't have a target. In this example, the relationship is for defining what sensors a Room might have, and the relationship can connect to any type.
 
-:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-27" highlight="20-25":::
+:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-30" highlight="22-27":::
 
 ### Properties of relationships
 
@@ -186,7 +186,7 @@ For a comprehensive list of the fields that may appear as part of a component, s
 
 Here's a basic example of a component on a DTDL model. This example shows a Room model that makes use of a thermostat model as a component.
 
-:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="15-19, 28-41":::
+:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="18-22, 31-47":::
 
 If other models in this solution should also contain a thermostat, they can reference the same thermostat model as a component in their own definitions, just like Room does.
 
@@ -212,7 +212,7 @@ The following example re-imagines the Home model from the earlier DTDL example a
 
 In this case, Core contributes an ID and name to Home. Other models can also extend the Core model to get these properties as well. Here's a Room model extending the same parent interface:
 
-:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-9" highlight="6":::
+:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-10" highlight="9":::
 
 Once inheritance is applied, the extending interface exposes all properties from the entire inheritance chain.
 

articles/expressroute/expressroute-locations.md

@@ -104,7 +104,7 @@ The following table shows locations by service provider. If you want to view ava
 | **[FarEasTone](https://www.fetnet.net/corporate/en/Enterprise.html)** | ✓ | ✓ | Taipei |
 | **[Fastweb](https://www.fastweb.it/grandi-aziende/dati-voce/scheda-prodotto/fast-company/)** | ✓ |✓ | Milan |
 | **[Fibrenoire](https://fibrenoire.ca/en/services/cloudextn-2/)** | &check; | &check; | Montreal<br/>Quebec City<br/>Toronto2 |
-| **[Flo Networks](https://flo.net/)** | &check; | &check; | Dallas<br/>Los Angeles<br/>Miami<br/>Queretaro(Mexico City)<br/>Sao Paulo<br/>Washington DC **Locations are listed under Neurtrona Networks and Transtelco as providers for circuit creation* |
+| **[Flo Networks](https://flo.net/)** | &check; | &check; | Dallas<br/>Los Angeles<br/>Miami<br/>Queretaro(Mexico City)<br/>Sao Paulo<br/>Washington DC<br/>**Locations are listed under Neurtrona Networks and Transtelco as providers for circuit creation* |
 | **[GBI](https://www.gbiinc.com/microsoft-azure/)** | &check; | &check; | Dubai2<br/>Frankfurt |
 | **[GÉANT](https://www.geant.org/Networks)** | &check; | &check; | Amsterdam<br/>Amsterdam2<br/>Dublin<br/>Frankfurt<br/>Madrid2<br/>Marseille |
 | **[GlobalConnect](https://www.globalconnect.no/)** | &check; | &check; | Amsterdam<br/>Copenhagen<br/>Oslo<br/>Stavanger<br/>Stockholm | 

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

@@ -17,6 +17,18 @@ ms.author: kavitagaddam
 
 Azure API for FHIR® provides a fully managed deployment of the Microsoft FHIR Server for Azure. The server is an implementation of the [FHIR](https://hl7.org/fhir) standard. This document provides details about the features and enhancements made to Azure API for FHIR.
 
+## **October 2024**
+
+### FHIR service
+
+**Bug fixes**
+
+- Export Validation: An issue was identified where exports proceeded despite invalid search parameters. We're introducing a change that prevents exports under these conditions. This feature is currently behind a strict validation flag and will become the default behavior on or after October 30.
+- Search Parameter Inclusion: We resolved an issue where additional search parameters (for instance, `_include`, `_has`) didn't return all expected results, sometimes omitting the next link.
+- Export Job Execution: A rare occurrence of `System.ObjectDisposedException` during export job completion has been addressed by preventing premature exits.
+- HTTP Status Code Update: The HTTP status code for invalid parameters during `$reindex` job creation is now updated to 400, ensuring better error handling.
+- Search Parameter Cleanup: A fix has been implemented to ensure complete cleanup of search parameters in the database when triggered with delete API calls, addressing issues related to incomplete deletions.
+
 ## **August 2024**
 
 ### FHIR service

articles/healthcare-apis/includes/rest-api-bundle-common.md

@@ -76,5 +76,5 @@ Transaction bundles don't support:
 Batch and transaction bundles are executed serially in the FHIR service. To improve performance and throughput, we enabled parallel processing of bundles.
 
 To use parallel batch bundle processing:
-- Set header `x-bundle-processing-logic` value to 1parallel`.
+- Set header `x-bundle-processing-logic` value to `parallel`.
 - Ensure there's no overlapping resource ID that executes on DELETE, POST, PUT, or PATCH operations in the same bundle.