Merge pull request #292008 from MicrosoftDocs/main

12/16/2024 AM Publish

Author: Taojunshen

articles/azure-cache-for-redis/cache-how-to-premium-vnet.md

@@ -28,6 +28,8 @@ ms.date: 12/12/2024
   - potential data loss
   - failure of management operations like scaling
   - intermittent or complete SSL/TLS failures
+  - failure to apply updates, including important security and reliability improvements
+    
   - in the most severe scenarios, loss of availability
 - VNet injected caches are only available for Premium-tier Azure Cache for Redis, not other tiers.
 - When using a VNet injected cache, you must change your VNet to cache dependencies such as Certificate Revocation Lists/Public Key Instructure, Azure Key Vault, Azure Storage, Azure Monitor, and more.

articles/azure-resource-manager/bicep/bicep-extension.md

@@ -16,7 +16,7 @@ This article describes how to use Bicep extensions.
 The syntax for importing Bicep extensions is:
 
 ```bicep
-extionsion <extension-name>
+extension <extension-name>
 ```
 
 The syntax for importing Bicep extensions, which require configuration is:
@@ -35,4 +35,4 @@ For examples, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md)
 - To learn about Bicep functions, see [Bicep functions](./bicep-functions.md).
 - To learn how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 - To go through a Kubernetes extension tutorial, see [Quickstart: Deploy Azure applications to Azure Kubernetes Services by using the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
-- To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).
+- To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).

articles/business-continuity-center/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.topic: landing-page
   author: AbhishekMallick-MS
   ms.author: v-abhmallick
-  ms.date: 11/19/2024
+  ms.date: 12/16/2024
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
@@ -31,10 +31,34 @@ landingContent:
           - text: Azure Business Continuity center support matrix
             url: business-continuity-center-support-matrix.md
 
+  # Card (optional)
+  - title: Manage data protection
+    linkLists:
+      - linkListType: quickstart
+        links:
+          - text: Understand the protection estate
+            url: quick-understand-protection-estate.md
+      - linkListType: tutorial
+        links:
+          - text: Configure protection for data sources
+            url: tutorial-configure-protection-datasource.md
+          - text: Recover deleted items
+            url: tutorial-recover-deleted-item.md
+          - text: Configure and view reports
+            url: tutorial-reporting-for-data-insights.md
+
   # Card (optional)
   - title: Monitor protection
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: Monitor protection summary
             url: tutorial-monitor-protection-summary.md
+
+  # Card (optional)
+  - title: Azure Business Continuity Center Copilot (preview)
+    linkLists:
+      - linkListType: tutorial
+        links:
+          - text: Manage BCDR estate (preview)
+            url: tutorial-manage-data-using-copilot.md

articles/cloud-services/cloud-services-troubleshoot-common-issues-which-cause-roles-recycle.md

@@ -24,7 +24,7 @@ If a role in your application relies on any assembly that isn't part of the .NET
 
 Before you build and package your application, verify the following statements are true:
 
-* If using Visual studio, make sure the **Copy Local** property is set to **True** for each referenced assembly in your project that isn't part of the Azure SDK or the .NET Framework.
+* If using Visual Studio, make sure the **Copy Local** property is set to **True** for each referenced assembly in your project that isn't part of the Azure SDK or the .NET Framework.
 * Make sure the web.config file doesn't reference any unused assemblies in the compilation element.
 * The **Build Action** of every .cshtml file is set to **Content**. This setting ensures that the files appear correctly in the package and enables other referenced files to appear in the package.
 

articles/communication-services/concepts/voice-video-calling/pre-call-diagnostics.md

@@ -11,7 +11,7 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ---
 
-# Pre-call diagnostic
+# Pre-call diagnostic overview
 
 [!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
 

articles/communication-services/quickstarts/voice-video-calling/get-started-pre-call-diagnostics.md

@@ -0,0 +1,50 @@
+---
+title: Quickstart - Add pre-call diagnostics to your app
+titleSuffix: An Azure Communication Services quickstart
+description: This quickstart describes how to add pre-call diagnostics capabilities to your app using Azure Communication Services.
+author: yassirbisteni
+manager: bobgao
+ms.author: yassirb
+ms.date: 12/12/2024
+ms.topic: quickstart
+ms.service: azure-communication-services
+ms.subservice: calling
+zone_pivot_groups: acs-plat-web-windows-android-ios
+ms.custom: mode-other, devx-track-js
+---
+
+# Quickstart: Add pre-call diagnostics to your app
+
+::: zone pivot="platform-web"
+[!INCLUDE [Pre-call diagnostics with JavaScript](./includes/pre-call-diagnostics/pre-call-diagnostics-javascript.md)]
+::: zone-end
+
+::: zone pivot="platform-windows"
+[!INCLUDE [Pre-call diagnostics with Windows](./includes/pre-call-diagnostics/pre-call-diagnostics-windows.md)]
+::: zone-end
+
+::: zone pivot="platform-android"
+[!INCLUDE [Pre-call diagnostics with Android](./includes/pre-call-diagnostics/pre-call-diagnostics-android.md)]
+::: zone-end
+
+::: zone pivot="platform-ios"
+[!INCLUDE [Pre-call diagnostics with iOS](./includes/pre-call-diagnostics/pre-call-diagnostics-ios.md)]
+::: zone-end
+
+## Pricing
+
+When the pre-call diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of pre-call diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
+
+## Next steps
+
+- [Check your network condition with the diagnostics tool](../../concepts/developer-tools/network-diagnostic.md).
+- [Explore User-Facing Diagnostic APIs](../../concepts/voice-video-calling/user-facing-diagnostics.md).
+- [Enable Media Quality Statistics in your application](../../concepts/voice-video-calling/media-quality-sdk.md).
+- [Consume call logs with Azure Monitor](../../concepts/analytics/logs/voice-and-video-logs.md).
+
+## Related articles
+
+- Check out the [calling hero sample](../../samples/calling-hero-sample.md).
+- Get started with the [UI Library](../../concepts/ui-library/ui-library-overview.md).
+- Learn about [Calling SDK capabilities](./getting-started-with-calling.md?pivots=platform-web).
+- Learn more about [how calling works](../../concepts/voice-video-calling/about-call-types.md).

articles/communication-services/quickstarts/voice-video-calling/get-started-raw-media-access.md

@@ -36,7 +36,12 @@ ms.custom: mode-other, devx-track-js
 
 ## Next steps
 
-For more information, see the following articles:
+- [Check your network condition with the diagnostics tool](../../concepts/developer-tools/network-diagnostic.md)
+- [Explore User-Facing Diagnostic APIs](../../concepts/voice-video-calling/user-facing-diagnostics.md)
+- [Enable Media Quality Statistics in your application](../../concepts/voice-video-calling/media-quality-sdk.md)
+- [Consume call logs with Azure Monitor](../../concepts/analytics/logs/voice-and-video-logs.md)
+
+## Related articles
 
 - Check out the [calling hero sample](../../samples/calling-hero-sample.md).
 - Get started with the [UI Library](../../concepts/ui-library/ui-library-overview.md).

articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-android.md

@@ -0,0 +1,77 @@
+---
+title: Azure Communication Services pre-call diagnostics
+titleSuffix: An Azure Communication Services concept document
+description: Overview of the pre-call diagnostic API feature.
+author: yassirbisteni
+manager: bobgao
+services: azure-communication-services
+ms.author: yassirb
+ms.date: 12/12/2024
+ms.topic: conceptual
+ms.service: azure-communication-services
+---
+
+## Pre-call diagnostics
+
+[!INCLUDE [Public Preview Disclaimer](../../../../includes/public-preview-include.md)]
+
+The pre-call API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../../../support.md) about which platforms you want to see pre-call diagnostics enabled.
+
+### Pre-call diagnostics access
+
+To access pre-call diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
+
+```java
+String acsToken = "";
+try
+{
+    CommunicationTokenCredential credential = new CommunicationTokenCredential(acsToken);
+    CallClient callClient = new CallClient();
+
+    PreCallDiagnosticsCallClientFeature preCallDiagnosticsFeature = callClient.feature(Features.PRE_CALL_DIAGNOSTICS);
+
+    preCallDiagnosticsFeature.addOnDiagnosticsReadyListener(this::OnPreCallDiagnosticsReady);
+    preCallDiagnosticsFeature.startTest(context, credential);
+}
+catch (Exception ex) { }
+```
+
+Once it finishes running, developers can access the result object.
+
+### Diagnostic results
+
+Pre-call diagnostics return a full diagnostic of the device including details like availability and compatibility, call quality statistics, and in-call diagnostics. The results are returned as a `PreCallDiagnosticsReadyEvent` object.
+
+```java
+public void OnPreCallDiagnosticsReady(PreCallDiagnosticsReadyEvent args)
+{
+    PreCallDiagnostics diagnostics = args.getDiagnostics();
+    MediaStatisticsReport mediaStatsReport = diagnostics.getMediaStatisticsReport();
+
+    OutgoingMediaStatistics outgoingStatsList = mediaStatsReport.getOutgoingStatistics();
+    if (outgoingStatsList != null)
+    {
+        List<OutgoingVideoStatistics> videoStatsList = outgoingStatsList.getVideoStatistics();
+        List<OutgoingScreenShareStatistics> screenShareStatsList = outgoingStatsList.getScreenShareStatistics();
+        List<OutgoingAudioStatistics> audioStatsList = outgoingStatsList.getAudioStatistics();
+    }
+
+    IncomingMediaStatistics incomingStatsList = mediaStatsReport.getIncomingStatistics();
+    if (incomingStatsList != null)
+    {
+        List<IncomingVideoStatistics> videoStatsList = incomingStatsList.getVideoStatistics();
+        List<IncomingScreenShareStatistics> screenShareStatsList = incomingStatsList.getScreenShareStatistics();
+        List<IncomingAudioStatistics> audioStatsList = incomingStatsList.getAudioStatistics();
+    }
+}
+```
+
+You can access individual result objects using the `PreCallDiagnosticsReadyEvent` type. Results for individual tests are returned when completed with many of the test results being available immediately. The results might take up to 1 minute as the test validates the quality of the video and audio.
+
+### Device permissions
+
+The permission check determines whether video and audio devices are available from a permissions perspective. Provides `boolean` value for `audio` and `video` devices. 
+
+```java
+List<DevicePermissionType> permissionList = preCallDiagnosticsFeature.getDevicePermissions(context);
+```

articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-ios.md

@@ -0,0 +1,102 @@
+---
+title: Azure Communication Services pre-call diagnostics
+titleSuffix: An Azure Communication Services concept document
+description: Implement the pre-call diagnostic API feature.
+author: yassirbisteni
+manager: bobgao
+services: azure-communication-services
+ms.author: ybisteni
+ms.date: 11/11/2024
+ms.topic: conceptual
+ms.service: azure-communication-services
+---
+
+## Implement pre-call diagnostics with iOS
+
+[!INCLUDE [Public Preview Disclaimer](../../../../includes/public-preview-include.md)]
+
+The pre-call API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../../../support.md) about which platforms you want to see pre-call diagnostics enabled.
+
+### Pre-call diagnostics access
+
+To access pre-call diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
+
+```swift
+let acsToken: String;
+do
+{
+    let options = CommunicationTokenRefreshOptions(initialToken: acsToken,
+                                                    refreshProactively: true,
+                                                    tokenRefresher: tokenRefresher)
+    credentials = try CommunicationTokenCredential(withOptions: options)
+}
+catch
+{
+    return nil
+}
+
+let options = CallClientOptions()
+callClient = CallClient(options: options)
+
+preCallDiagnosticsFeature = callClient.feature(Features.preCallDiagnostics)
+
+preCallDiagnosticsCallClientFeatureObserver = PreCallDiagnosticsCallClientFeatureObserver(view: self)
+preCallDiagnosticsFeature.delegate = preCallDiagnosticsCallClientFeatureObserver
+preCallDiagnosticsFeature.startTest(credentials, withCompletionHandler: { error in
+
+})
+
+class PreCallDiagnosticsCallClientFeatureObserver: NSObject, PreCallDiagnosticsCallClientFeatureDelegate
+{
+    private var view: HomeView
+
+    init(view: HomeView)
+    {
+        self.view = view
+    }
+    
+    func diagnosticsCallClientFeature(_ preCallDiagnosticsCallClientFeature: PreCallDiagnosticsCallClientFeature, 
+                                      didDiagnosticsReady args: PreCallDiagnosticsReadyEventArgs)
+    {
+        view.onPreCallDiagnosticsReady(args: args)
+    }
+}
+```
+
+Once it finishes running, developers can access the result object.
+
+### Diagnostic results
+
+Pre-call diagnostics returns a full diagnostic of the device including details like availability and compatibility, call quality statistics, and in-call diagnostics. The results are returned as a `PreCallDiagnosticsReadyEvent` object.
+
+```swift
+func onPreCallDiagnosticsReady(args: PreCallDiagnosticsReadyEventArgs) -> Void
+{
+    let diagnostics = args.diagnostics
+    let mediaStatsReport = diagnostics.mediaStatisticsReport;
+
+    if let outgoingStatsList = mediaStatsReport.outgoingStatistics
+    {
+        let videoStatsList = outgoingStatsList.videoStatistics;
+        let screenShareStatsList = outgoingStatsList.screenShareStatistics;
+        let audioStatsList = outgoingStatsList.audioStatistics;
+    }
+
+    if let incomingStatsList = mediaStatsReport.incomingStatistics
+    {
+        let videoStatsList = incomingStatsList.videoStatistics;
+        let screenShareStatsList = incomingStatsList.screenShareStatistics;
+        let audioStatsList = incomingStatsList.audioStatistics;
+    }
+}
+```
+
+You can access individual result objects using the `PreCallDiagnosticsReadyEvent` type. Results for individual tests are returned as they're completed with many of the test results being available immediately. The results might take up to 1 minute as the test validates the quality of the video and audio.
+
+#### Device permissions
+
+The permission check determines whether video and audio devices are available from a permissions perspective. Provides `boolean` value for `audio` and `video` devices. 
+
+```swift
+let permissionList = preCallDiagnosticsFeature?.devicePermissions()
+```