Skip to content

Commit 2b5a66d

Browse files
authored
Merge pull request #288670 from MicrosoftDocs/main
10/17/2024 PM Publish
2 parents 4f0aaa1 + cda6a4c commit 2b5a66d

File tree

37 files changed

+72
-50
lines changed

37 files changed

+72
-50
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,8 +133,8 @@ More information about policies:
133133
|---------|---------|---------|---------|---------|--------|
134134
| [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 |
135135
| [Emit metrics](emit-metric-policy.md) | Sends custom metrics to Application Insights at execution. | Yes | Yes | Yes | Yes |
136-
| [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 |
137-
| [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 |
136+
| [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 |
137+
| [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 |
138138

139139

140140
<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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@ ms.custom: references_regions
1010
# Supported regions for linked Log Analytics workspace
1111

1212
> [!NOTE]
13-
> 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.
13+
> - 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).
14+
> - 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.
1415
1516
[!INCLUDE [./log-analytics-retirement-announcement.md](../includes/log-analytics-retirement-announcement.md)]
1617

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ The `feature_flags` provided to `FeatureManager` can either be the `AzureAppConf
179179

180180
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.
181181

182-
The following snippet demonstrates how to add a customized feature filter `MyCriteriaFilter`.
182+
The following snippet demonstrates how to add a customized feature filter `MyCustomFilter`.
183183

184184
```python
185185
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
280280

281281
```python
282282
# Directly specifying the user
283-
feature_manager = FeatureManager(feature_flags, "test_user")
283+
result = is_enabled(feature_flags, "test_user")
284284

285285
# Using a TargetingContext
286-
feature_manager = FeatureManager(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
286+
result = is_enabled(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
287287
```
288288

289289
### Targeting exclusion

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

Lines changed: 8 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -2,23 +2,19 @@
22
title: Azure Communication Services troubleshooting VoIP call quality
33
titleSuffix: An Azure Communication Services concept article
44
description: Learn how to troubleshoot web VoIP call quality with Azure Communication Services.
5-
author: Cardiohater1
6-
ms.author: drohmetra
7-
manager: dacarte
5+
author: sloanster
6+
ms.author: micahvivion
87

98
services: azure-communication-services
10-
ms.date: 3/6/2024
9+
ms.date: 10/17/2024
1110
ms.topic: conceptual
1211
ms.service: azure-communication-services
1312
ms.subservice: calling
1413
---
1514

16-
1715
# Troubleshoot VoIP call quality
1816

19-
This article describes how to troubleshoot and improve web Voice over Internet Protocol (VoIP) call quality in Azure Communication Services.
20-
21-
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.
17+
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.
2218

2319
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.
2420

@@ -54,7 +50,7 @@ When a caller or callee reports audio interference or background noise on a call
5450

5551
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).
5652

57-
## Pre-call checkups
53+
## Precall checkups
5854

5955
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:
6056

@@ -90,18 +86,14 @@ If you tried all the previous actions and still face quality problems, [create a
9086

9187
## End of Call Survey
9288

93-
Enable the End of Call Survey feature to give Azure Communication Services users the option to submit qualitative feedback about their call experience.
89+
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.
9490

9591
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).
9692

9793
## Related content
98-
94+
- 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).
95+
- 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.
9996
- 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).
100-
101-
- 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.
102-
10397
- 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).
104-
10598
- For more information about preparing your network or your customer's network, see [Network recommendations](network-requirements.md).
106-
10799
- 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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -329,7 +329,7 @@ const localVideoStreams = call.localVideoStreams;
329329

330330
## Manage chat thread
331331
>[!IMPORTANT]
332-
> 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.
332+
> 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.
333333
334334
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.
335335

@@ -346,12 +346,12 @@ If Teams user stops call recording, the recording is placed into the chat associ
346346

347347
Recommendations for the management of chat ID:
348348
- Escalation of the 1:1 phone call by adding another phone participant:
349-
* 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.
349+
* 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.
350350
```js
351351
addParticipant(participant: MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)
352352
```
353353
- Start group call with single Microsoft 365 user and multiple phone participants:
354-
* 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.
354+
* 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.
355355
```js
356356
startCall(MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)[])
357357
```
@@ -361,4 +361,4 @@ Recommendations for the management of chat ID:
361361
```js
362362
startCall(MicrosoftTeamsUserIdentifier | PhoneNumberIdentifier | MicrosoftTeamsAppIdentifier | UnknownIdentifier)[])
363363
```
364-
* 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)
364+
* 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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ Sometimes, you might want to define a relationship without a specific target, so
166166

167167
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.
168168

169-
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-27" highlight="20-25":::
169+
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-30" highlight="22-27":::
170170

171171
### Properties of relationships
172172

@@ -186,7 +186,7 @@ For a comprehensive list of the fields that may appear as part of a component, s
186186

187187
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.
188188

189-
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="15-19, 28-41":::
189+
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" highlight="18-22, 31-47":::
190190

191191
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.
192192

@@ -212,7 +212,7 @@ The following example re-imagines the Home model from the earlier DTDL example a
212212

213213
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:
214214

215-
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-9" highlight="6":::
215+
:::code language="json" source="~/digital-twins-docs-samples-getting-started/models/advanced-home-example/IRoom.json" range="2-10" highlight="9":::
216216

217217
Once inheritance is applied, the extending interface exposes all properties from the entire inheritance chain.
218218

articles/expressroute/expressroute-locations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The following table shows locations by service provider. If you want to view ava
104104
| **[FarEasTone](https://www.fetnet.net/corporate/en/Enterprise.html)** | &check; | &check; | Taipei |
105105
| **[Fastweb](https://www.fastweb.it/grandi-aziende/dati-voce/scheda-prodotto/fast-company/)** | &check; |&check; | Milan |
106106
| **[Fibrenoire](https://fibrenoire.ca/en/services/cloudextn-2/)** | &check; | &check; | Montreal<br/>Quebec City<br/>Toronto2 |
107-
| **[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* |
107+
| **[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* |
108108
| **[GBI](https://www.gbiinc.com/microsoft-azure/)** | &check; | &check; | Dubai2<br/>Frankfurt |
109109
| **[GÉANT](https://www.geant.org/Networks)** | &check; | &check; | Amsterdam<br/>Amsterdam2<br/>Dublin<br/>Frankfurt<br/>Madrid2<br/>Marseille |
110110
| **[GlobalConnect](https://www.globalconnect.no/)** | &check; | &check; | Amsterdam<br/>Copenhagen<br/>Oslo<br/>Stavanger<br/>Stockholm |

articles/iot-operations/manage-layered-network/concept-iot-operations-in-layered-network.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.topic: concept-article
88
ms.date: 11/29/2023
99

1010
#CustomerIntent: As an operator, I want to learn about the architecture of Azure IoT Operations in a Purdue Network environment and how does Layered Network Managment support this scenario.
11+
ms.service: azure-iot-operations
1112
---
1213

1314
# How does Azure IoT Operations Preview work in layered network?

articles/iot-operations/manage-layered-network/howto-configure-aks-edge-essentials-layered-network.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ ms.custom:
1010
ms.date: 07/02/2024
1111

1212
#CustomerIntent: As an operator, I want to Azure Arc enable AKS Edge Essentials clusters using Layered Network Management so that I have secure isolate devices.
13+
ms.service: azure-iot-operations
1314
---
1415

1516
# Configure Layered Network Management Preview to use Azure IoT Operations Preview in an isolated network

articles/iot-operations/manage-layered-network/howto-configure-l3-cluster-layered-network.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.custom: ignite-2023, devx-track-azurecli
99
ms.date: 07/02/2024
1010

1111
#CustomerIntent: As an operator, I want to configure Layered Network Management so that I have secure isolate devices.
12+
ms.service: azure-iot-operations
1213
---
1314

1415
# Configure level 3 cluster in an isolated network with Azure IoT Layered Network Management Preview

0 commit comments

Comments
 (0)