Merge branch 'main' into incub3

Author: ankitaduttaMSFT

.openpublishing.redirection.json

@@ -2595,6 +2595,11 @@
       "redirect_url": "/azure/azure-maps/zoom-levels-and-tile-grid",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/managed-grafana/how-to-sync-teams-with-azure-ad-groups.md",
+      "redirect_url": "managed-grafana/how-to-sync-teams-with-entra-groups",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/media-services/azure-media-player/azure-media-player-license.md",
       "redirect_url": "/legal/azure-media-player/azure-media-player-license",

articles/automation/troubleshoot/change-tracking.md

@@ -136,7 +136,6 @@ Here are possible causes specific to this issue:
 Verify that the daemon for the Log Analytics agent for Linux (**omsagent**) is running on your machine. Run the following query in the Log Analytics workspace that's linked to your Automation account.
 
 ```loganalytics
-Copy
 Heartbeat
 | summarize by Computer, Solutions
 ```

articles/communication-services/concepts/best-practices.md

@@ -24,10 +24,9 @@ This article provides information about best practices related to the Azure Comm
 [!INCLUDE [Native](includes/best-practices-native.md)]
 ::: zone-end
 
-## Next steps
-For more information, see the following articles:
+## Related content
 
 - [Improve and manage call quality](./voice-video-calling/manage-call-quality.md)
-- [Call Diagnostics](./voice-video-calling/call-diagnostics.md)
+- [Use Call Diagnostics to diagnose call problems](./voice-video-calling/call-diagnostics.md)
 - [Add voice calling to your app](../quickstarts/voice-video-calling/getting-started-with-calling.md)
-- [Use the UI Library for enhance calling experiences](./ui-library/ui-library-overview.md)
+- [Use the UI Library for enhanced calling experiences](./ui-library/ui-library-overview.md)

articles/communication-services/concepts/includes/best-practices-native.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Communication Services - best practices for Calling Native SDK
-description: Learn more about Azure Communication Service best practices for Calling Native SDK.
+description: Learn about Azure Communication Services best practices for the Calling Native SDK.
 author: garchiro7
 manager: chpalmer
 services: azure-communication-services
@@ -11,47 +11,47 @@ ms.topic: include
 ms.service: azure-communication-services
 ---
 
-## Azure Communication Services native SDK best practices
+## Best practices for the Azure Communication Services Calling Native SDK
 
-This section provides information about best practices associated with the Azure Communication Services voice and video calling native SDK.
+This section provides information about best practices associated with the Azure Communication Services Calling Native SDK for voice and video calling.
 
-## Supported platforms
+### Supported platforms
 
-Here are the minimum OS platform requirements to ensure optimal functionality of the Calling Native SDKs.
+Here are the minimum OS platform requirements to ensure optimal functionality of the Calling Native SDK.
 
-### [iOS](#tab/ios)
+#### [iOS](#tab/ios)
 
-- Support for iOS 10.0+ at build time, and iOS 12.0+ at run time.
-- Xcode 12.0+.
-- Support for **iPadOS** 13.0+.
+- Support for iOS 10.0+ at build time and iOS 12.0+ at runtime
+- Xcode 12.0+
+- Support for iPadOS 13.0+
 
-### [Android](#tab/android)
+#### [Android](#tab/android)
 
-- Support for Android API Level 21 or Higher.
-- Support for Java 7 or higher.
-- Support for Android Studio 2.0.
+- Support for Android API Level 21 or higher
+- Support for Java 7 or later
+- Support for Android Studio 2.0
 
-We highly recommend identifying and validating your scenario by visiting the supported [Android platforms](../sdk-options.md?#android-platform-support)
+We highly recommend that you identify and validate your scenario by using the information in [Android platform support](../sdk-options.md?#android-platform-support).
 
-### [Windows](#tab/windows)
+#### [Windows](#tab/windows)
 
-- Support for UWP (Universal Windows Platform).
-- Support for WinUI 3.
+- Support for Universal Windows Platform (UWP)
+- Support for WinUI 3
 
 ---
 
-## App request device permissions
+### Verify device permissions for app requests
 
-To use the Calling Native SDKs for making or receiving calls, it's necessary to authorize each platform to access device resources. As a developer, you should prompt the user for access and ensure that are enabled. The consumer authorizes these access rights, so verify that they have been granted permission previously.
+To use the Calling Native SDK for making or receiving calls, consumers need to authorize each platform to access device resources. As a developer, you must prompt the user for access and ensure that permissions are enabled. The consumer authorizes these access rights, so verify that they currently have the required permissions.
 
-### [iOS](#tab/ios)
+#### [iOS](#tab/ios)
 
-- `NSMicrophoneUsageDescription` for microphone access.
-- `NSCameraUsageDescription` for camera access.
+- `NSMicrophoneUsageDescription` for microphone access
+- `NSCameraUsageDescription` for camera access
 
-### [Android](#tab/android)
+#### [Android](#tab/android)
 
-In the Application Manifest (`app/src/main/AndroidManifest.xml`). Verify the following lines:
+In the application manifest (`app/src/main/AndroidManifest.xml`), verify the following lines:
 
 ```xml
     <uses-permission android:name="android.permission.INTERNET" />
@@ -64,54 +64,60 @@ In the Application Manifest (`app/src/main/AndroidManifest.xml`). Verify the fol
     <uses-permission android:name="android.permission.FOREGROUND_SERVICE_MICROPHONE" />
 ```
 
-### [Windows](#tab/windows)
+#### [Windows](#tab/windows)
 
 Go to `Package.appxmanifest` and select capabilities:
 
-- `Internet (Client)` & `Internet (Client & Server)` for network access.
-- `Microphone` to access the audio feed of the microphone.
-- `Webcam` to access the video feed of the camera.
+- `Internet (Client)` and `Internet (Client & Server)` for network access
+- `Microphone` to access the audio feed of the microphone
+- `Webcam` to access the video feed of the camera
 
 ---
 
-## Configure the logs
+### Configure the logs
 
-Implementing **logging** as per the [logs file retrieval tutorial](../../tutorials/log-file-retrieval-tutorial.md) is more critical than ever. Detailed logs help in diagnosing issues specific to device models or OS versions that meet the minimum SDK criteria. We encourage to the developers that start configuring the Logs API without the logs the Microsoft Support team **won't be able** to help debug and troubleshoot the calls.
+Implementing logging as described in the [tutorial about retrieving log files](../../tutorials/log-file-retrieval-tutorial.md) is more critical than ever. Detailed logs help in diagnosing problems specific to device models or OS versions that meet the minimum SDK criteria. We encourage developers to configure logs by using the Logs API. Without the logs, the Microsoft support team can't help debug and troubleshoot the calls.
 
-## Track Call ID
+### Track CallID
 
-**`CallID`** is the unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call, in Most cases you use it to review the logs and  Microsoft Support team ask for it to help troubleshoot the calls. You **should** track the `CallID` in your telemetry that you configure in your app, you can follow the guidelines in the [troubleshooting guide](../troubleshooting-info.md) to understand how to retrieve it for each platform.
+`CallID` is the unique ID for a call. It identifies correlated events from all of the participants and endpoints that connect during a single call. In most cases, you use it to review the logs. The Microsoft Support team asks for it to help troubleshoot the calls.
 
-## Subscribe to UFD (User Facing Diagnostics) and media quality statistics
+You should track the `CallID` value in the telemetry that you configure in your app. To understand how to retrieve the value for each platform, follow the guidelines in the [troubleshooting guide](../troubleshooting-info.md).
 
-- [User Facing Diagnostics (UFD)](../voice-video-calling/user-facing-diagnostics.md) that can be used to examine various properties of a call to determine what the issue might be during the call that affects your customers.
-- [Media quality statistics](../voice-video-calling/media-quality-sdk.md) examine the low-level audio, video, and screen-sharing quality metrics for incoming and outgoing call metrics. We recommend that you collect the data and send it to your pipeline ingestion after your call ends.
+### Subscribe to User Facing Diagnostics and media quality statistics
 
-## Error Handling
+You can use these Azure Communication Services features to help improve the user experience:
 
-If there are any errors during the call or implementation, the methods return error objects containing error codes. It's crucial to use these error objects for proper error handling and to display alerts. The call states also return error codes to help identify the reason behind call failure. You can refer to [the troubleshooting guide](../troubleshooting-info.md), to resolve any issues.
+- [User Facing Diagnostics](../voice-video-calling/user-facing-diagnostics.md): Examine properties of a call to determine the cause of problems that affect your customers.
+- [Media quality statistics](../voice-video-calling/media-quality-sdk.md): Examine the low-level audio, video, and screen-sharing quality metrics for incoming and outgoing call metrics. We recommend that you collect the data and send it to your pipeline ingestion after a call ends.
 
-### Managing Video Streams
+### Manage error handling
 
-Make sure to dispose of the `VideoStreamRendererView` when the video is no longer displayed on the UI. Use `VideoStreamType` to determine the type of the stream.
+If there are any errors during the call or implementation, the methods return error objects that contain error codes. It's crucial to use these error objects for proper error handling and to display alerts. The call states also return error codes to help identify the reasons behind call failures. You can refer to the [troubleshooting guide](../troubleshooting-info.md) to resolve any problems.
 
-## General memory management
+### Manage video streams
 
-**Preallocate Resources**. Initialize your calling client and any necessary resources during your app's startup phase rather than on demand. This approach reduces latency when starting a call.
+Be sure to dispose of `VideoStreamRendererView` when the UI no longer displays the video. Use `VideoStreamType` to determine the type of the stream.
 
-**Dispose Properly**. Ensure that all call objects are correctly disposed of after use to free up system resources and avoid memory leaks. Make sure to unsubscribe from *events* preventing memory leaks.
+### Conduct general memory management
 
-## Camera or microphone being used by another process
+**Preallocate resources**. Initialize your calling client and any necessary resources during your app's startup phase rather than on demand. This approach reduces latency in starting a call.
 
-It's important to note that on mobile devices if multiple processes try to access the camera or microphone at the same time, the first process to request access will take control of the device. As a result, the second process will immediately lose access to it.
+**Dispose properly**. Dispose of all call objects after use, to free up system resources and avoid memory leaks. Be sure to unsubscribe from *events* that might cause memory leaks.
 
-## Optimize the APP size using UI Library
+### Consider how processes access the camera or microphone
 
-Optimizing the size of libraries in software development is crucial for several reasons, particularly as applications become increasingly complex, and resource-intensive.
+On mobile devices, if multiple processes try to access the camera or microphone at the same time, the first process to request access takes control of the device. As a result, the second process immediately loses access to it.
 
-Application Performance: Smaller libraries reduce the amount of code that must be loaded, parsed, and executed by an application. This can significantly enhance the startup time and overall performance of your application, especially on devices with limited resources.
+### Optimize library size
 
-Memory Usage: By minimizing library size, you can decrease the runtime memory footprint of an application. This is important for mobile devices, where memory is often constrained. Lower memory usage can lead to fewer system crashes and better multitasking performance.
+Optimizing the size of libraries in software development is crucial for the following reasons, particularly as applications become more complex and resource intensive:
+
+- **Application performance**: Smaller libraries reduce the amount of code that an application must load, parse, and execute. This reduction can significantly enhance the startup time and overall performance of your application, especially on devices that have limited resources.
+
+- **Memory usage**: By minimizing library size, you can decrease the runtime memory footprint of an application. This decrease is important for mobile devices, where memory is often constrained. Lower memory usage can lead to fewer system crashes and better multitasking performance.
+
+For more information, see:
 
 - [UI Library for iOS](https://github.com/Azure/communication-ui-library-ios/wiki/Calling-Composite-Demo-Application-Size)
 - [UI Library for Android](https://github.com/Azure/communication-ui-library-android/wiki/Calling-Composite-Demo-Application-Size)