Merge pull request #308732 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-25 06:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -990,6 +990,11 @@
       "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-configure-compute",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/databox-online/azure-stack-edge-deploy-aks-on-azure-stack-edge.md",
+      "redirect_url": "/articles/databox-online/azure-stack-edge-gpu-kubernetes-workload-management",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/databox-online/azure-stack-edge-system-requirements.md",
       "redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-system-requirements",

articles/backup/azure-data-lake-storage-backup-support-matrix.md

@@ -26,7 +26,7 @@ Vaulted backups of Azure Data Lake Storage are available in the following region
 
 | Availability type | Region |
 | --- | --- |
-| **General availability** | East Asia, France South, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India. |
+| **General availability** | Central US, East Asia, France South, Germany West Central, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India. |
 | **Preview** | Australia East, Central India, Central US, East US, East US 2, Germany West Central, North Central US, North Europe, South India, Southeast Asia, West Central US, West US, West US 2, West US 3. |
 
 ## Supported storage accounts
@@ -70,7 +70,7 @@ Azure Data Lake Storage protection has the following supported and unsupported s
   - Soft Delete: Objects can still be soft-deleted as expected.
   - Undelete: Restore from soft-deleted state is not supported while Vaulted Backup is active. Undelete will only work if Vaulted Backup is disabled first. Re-enabling Vaulted Backup after disabling will trigger a full backup.
 - Storage accounts upgraded from FNS to HNS are not supported for backup.
-- SFTP-enabled & NFS accounts are not supported for backup. Backup jobs may stall if SFTP-uploaded blobs encountered.
+- SFTP- and NFS-enabled accounts aren’t supported for Vaulted Backup. Backup jobs on these accounts fail or hang when processing blobs uploaded via SFTP.
 - $web container cannot be restored as $web on the target. Use the renameTo option and restore it with a different container name.
 - $root container can be restored as $root on the target only if $root does not already exist there. If it already exists, use the renameTo option and restore it with a different container name.
 

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

@@ -57,14 +57,25 @@ end
 
 4. Open the `.xcworkspace` with Xcode.
 
-### Using XCFramework directly
+### Using Swift Package Manager [Recommended]
+
+Swift Package Manager is now the recommended installation method for the Azure Communication Calling SDK. CocoaPods support is being deprecated and will be removed in future versions.
+If you prefer to use Swift Package Manager, you can add the Azure Communication Calling SDK directly to your Xcode project.
+
+Installation Steps
+1. In Xcode, go to File > Add Package Dependencies...
+2. Enter the following repository URL: [https://github.com/Azure/SwiftPM-AzureCommunicationCalling](https://github.com/Azure/SwiftPM-AzureCommunicationCalling)
+3. For Dependency Rule, select Exact Version and enter: 2.17.0-beta.3
+4. Click Add Package
+5. Select the AzureCommunicationCalling product and add it to your target
 
-If you aren't using `CocoaPods` as a dependency manager, you can directly download the `AzureCommunicationCalling.xcframework` directly from our [release page](https://github.com/Azure/Communication/releases). 
 
-Is important to know that `AzureCommunicationCalling` has a dependency on [`AzureCommunicationCommon`](https://github.com/Azure/azure-sdk-for-ios/tree/main/sdk/communication/AzureCommunicationCommon) so you need to install it as well in your project. 
+### Using XCFramework directly
+
+If you aren't using CocoaPods or Swift Package Manager, you can directly download the AzureCommunicationCalling.xcframework from our release page.
 
 >[!NOTE]
- > Although [`AzureCommunicationCommon`](https://github.com/Azure/azure-sdk-for-ios/tree/main/sdk/communication/AzureCommunicationCommon) is a pure swift package, you cannot install it using [`Swift Package Manager`](https://www.swift.org/package-manager/) to use it with `AzureCommunicationCalling` because the latter is an Objective-C framework and [`Swift Package Manager`](https://www.swift.org/package-manager/) deliberately do not support Swift ObjC interface headers by design which means is not possible to work together with `AzureCommunicationCalling` if installed using [`Swift Package Manager`](https://www.swift.org/package-manager/). You would have to either install via another dependency manager or generate a `xcframework` from [`AzureCommunicationCommon`](https://github.com/Azure/azure-sdk-for-ios/tree/main/sdk/communication/AzureCommunicationCommon) sources and import into your project.
+ > Keep in mind that AzureCommunicationCalling has a dependency on AzureCommunicationCommon, so you need to install both in your project. You would need to generate an xcframework from AzureCommunicationCommon sources and import it into your project.
 
 ### Request access to the microphone and camera
 

articles/databox-online/TOC.yml

@@ -331,10 +331,6 @@
         href: azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning.md
       - name: GPU extension issues
         href: azure-stack-edge-gpu-troubleshoot-virtual-machine-gpu-extension-installation.md
-  - name: Azure Kubernetes service
-    items:
-    - name: Deploy AKS on Azure Stack Edge
-      href: azure-stack-edge-deploy-aks-on-azure-stack-edge.md
   - name: Kubernetes
     items:
     - name: What is Kubernetes?
@@ -497,7 +493,9 @@
         href: azure-stack-edge-contact-microsoft-support.md
   - name: Shared release notes
     items:
-    - name: 2506 - Current
+    - name: 2510 - Current
+      href: azure-stack-edge-gpu-2510-release-notes.md
+    - name: "2506"
       href: azure-stack-edge-gpu-2506-release-notes.md
     - name: "2501"
       href: azure-stack-edge-gpu-2501-release-notes.md