Merge pull request #273501 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 4/26

Author: ttorble

articles/azure-signalr/signalr-howto-scale-signalr.md

@@ -95,7 +95,7 @@ For a table of service limits, quotas, and constraints in each tier, see [Signal
 
 
 ## Enhanced Large Instance Support with Premium_P2 SKU
-The new Premium_P2 SKU (currently in Preview) is designed to facilitate extensive scalability for high-demand scenarios.  This SKU allows scaling among 100, 200, 300, 400, 500, 600. 700, 800, 900, 1000 units for a single SignalR Service instance. This enhancement enables the handling of up to **one million** concurrent connections, catering to large-scale, real-time communication needs.
+The new Premium_P2 SKU is designed to facilitate extensive scalability for high-demand scenarios.  This SKU allows scaling among 100, 200, 300, 400, 500, 600. 700, 800, 900, 1000 units for a single SignalR Service instance. This enhancement enables the handling of up to **one million** concurrent connections, catering to large-scale, real-time communication needs.
 
 You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.
 
@@ -116,4 +116,4 @@ Autoscale is supported in Azure SignalR Service Premium Tier.
 Multiple endpoints are also supported for scaling, sharding, and cross-region scenarios.
 
 > [!div class="nextstepaction"]
-> [scale SignalR Service with multiple instances](./signalr-howto-scale-multi-instances.md)
+> [scale SignalR Service with multiple instances](./signalr-howto-scale-multi-instances.md)

articles/azure-web-pubsub/howto-scale-manual-scale.md

@@ -69,7 +69,7 @@ For a table of service limits, quotas, and constraints in each tier, see [Web Pu
 
 
 ## Enhanced large instance support with Premium_P2 SKU
-The new Premium_P2 SKU (currently in Preview) is designed to facilitate extensive scalability for high-demand scenarios.  This SKU allows scaling among 100, 200, 300, 400, 500, 600. 700, 800, 900, 1000 units for a single Web PubSub Service instance. This enhancement enables the handling of up to **one million** concurrent connections, catering to large-scale, real-time communication needs.
+The new Premium_P2 SKU is designed to facilitate extensive scalability for high-demand scenarios.  This SKU allows scaling among 100, 200, 300, 400, 500, 600. 700, 800, 900, 1000 units for a single Web PubSub Service instance. This enhancement enables the handling of up to **one million** concurrent connections, catering to large-scale, real-time communication needs.
 
 You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.
 
@@ -85,4 +85,4 @@ In this guide, you learned about how to scale single Web PubSub Service instance
 Autoscale is supported in Azure Web PubSub Service Premium Tier.
 
 > [!div class="nextstepaction"]
-> [Automatically scale units of an Azure Web PubSub Service](./howto-scale-autoscale.md)
+> [Automatically scale units of an Azure Web PubSub Service](./howto-scale-autoscale.md)

articles/backup/backup-mabs-install-azure-stack.md

@@ -1,14 +1,15 @@
 ---
-title: Install Azure Backup Server on Azure Stack
-description: In this article, learn how to use Azure Backup Server to protect or back up workloads in Azure Stack.
-ms.topic: conceptual
-ms.date: 04/20/2023
+title: Install Azure Backup Server on Azure Stack Hub
+description: In this article, learn how to use Azure Backup Server to protect or back up workloads in Azure Stack Hub.
+ms.topic: how-to
+ms.service: backup
+ms.date: 04/22/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
-# Install Azure Backup Server on Azure Stack
+# Install Azure Backup Server on Azure Stack Hub
 
-This article explains how to install Azure Backup Server on Azure Stack. With Azure Backup Server, you can protect Infrastructure as a Service (IaaS) workloads such as virtual machines running in Azure Stack. A benefit of using Azure Backup Server to protect your workloads is you can manage all workload protection from a single console.
+This article explains how to install Azure Backup Server on Azure Stack Hub. With Azure Backup Server, you can protect Infrastructure as a Service (IaaS) workloads such as virtual machines running in Azure Stack Hub. A benefit of using Azure Backup Server to protect your workloads is you can manage all workload protection from a single console.
 
 > [!NOTE]
 > To learn about security capabilities, refer to [Azure Backup security features documentation](backup-azure-security-feature.md).
@@ -17,15 +18,15 @@ This article explains how to install Azure Backup Server on Azure Stack. With Az
 
 ## Prerequisites for the Azure Backup Server environment
 
-Consider the recommendations in this section when installing Azure Backup Server in your Azure Stack environment. The Azure Backup Server installer checks that your environment has the necessary prerequisites, but you'll save time by preparing before you install.
+Consider the recommendations in this section when installing Azure Backup Server in your Azure Stack Hub environment. The Azure Backup Server installer checks that your environment has the necessary prerequisites, but you'll save time by preparing before you install.
 
 ### Determining size of virtual machine
 
-To run Azure Backup Server on an Azure Stack virtual machine, use size A2 or larger. For assistance in choosing a virtual machine size, download the [Azure Stack VM size calculator](https://www.microsoft.com/download/details.aspx?id=56832).
+To run Azure Backup Server on an Azure Stack Hub virtual machine, use size A2 or larger. For assistance in choosing a virtual machine size, download the [Azure Stack Hub VM size calculator](https://www.microsoft.com/download/details.aspx?id=56832).
 
-### Virtual Networks on Azure Stack virtual machines
+### Virtual Networks on Azure Stack Hub virtual machines
 
-All virtual machines used in an Azure Stack workload must belong to the same Azure virtual network and Azure Subscription.
+All virtual machines used in an Azure Stack Hub workload must belong to the same Azure virtual network and Azure Subscription.
 
 ### Azure Backup Server VM performance
 
@@ -36,25 +37,25 @@ If shared with other virtual machines, the storage account size and IOPS limits
 
 ### Configuring Azure Backup temporary disk storage
 
-Each Azure Stack virtual machine comes with temporary disk storage, which is available to the user as volume `D:\`. The local staging area needed by Azure Backup can be configured to reside in `D:\`, and the cache location can be placed on `C:\`. In this way, no storage needs to be carved away from the data disks attached to the Azure Backup Server virtual machine.
+Each Azure Stack Hub virtual machine comes with temporary disk storage, which is available to the user as volume `D:\`. The local staging area needed by Azure Backup can be configured to reside in `D:\`, and the cache location can be placed on `C:\`. In this way, no storage needs to be carved away from the data disks attached to the Azure Backup Server virtual machine.
 
 ### Storing backup data on local disk and in Azure
 
-Azure Backup Server stores backup data on Azure disks attached to the virtual machine, for operational recovery. Once the disks and storage space are attached to the virtual machine, Azure Backup Server manages storage for you. The amount of backup data storage depends on the number and size of disks attached to each [Azure Stack virtual machine](/azure-stack/user/azure-stack-storage-overview). Each size of Azure Stack VM has a maximum number of disks that can be attached to the virtual machine. For example, A2 is four disks. A3 is eight disks. A4 is 16 disks. Again, the size and number of disks determines the total backup storage pool.
+Azure Backup Server stores backup data on Azure disks attached to the virtual machine, for operational recovery. Once the disks and storage space are attached to the virtual machine, Azure Backup Server manages storage for you. The amount of backup data storage depends on the number and size of disks attached to each [Azure Stack Hub virtual machine](/azure-stack/user/azure-stack-storage-overview). Each size of Azure Stack Hub VM has a maximum number of disks that can be attached to the virtual machine. For example, A2 is four disks. A3 is eight disks. A4 is 16 disks. Again, the size and number of disks determines the total backup storage pool.
 
 > [!IMPORTANT]
 > You should **not** retain operational recovery (backup) data on Azure Backup Server-attached disks for more than five days.
 >
 
-Storing backup data in Azure reduces backup infrastructure on Azure Stack. If data is more than five days old, it should be stored in Azure.
+Storing backup data in Azure reduces backup infrastructure on Azure Stack Hub. If data is more than five days old, it should be stored in Azure.
 
 To store backup data in Azure, create or use a Recovery Services vault. When preparing to back up the Azure Backup Server workload, you [configure the Recovery Services vault](backup-azure-microsoft-azure-backup.md#create-a-recovery-services-vault). Once configured, each time a backup job runs, a recovery point is created in the vault. Each Recovery Services vault holds up to 9999 recovery points. Depending on the number of recovery points created, and how long they're retained, you can retain backup data for many years. For example, you could create monthly recovery points, and retain them for five years.
 
 ### Scaling deployment
 
 If you want to scale your deployment, you have the following options:
 
-- Scale up - Increase the size of the Azure Backup Server virtual machine from A series to D series, and increase the local storage [per the Azure Stack virtual machine instructions](/azure-stack/user/azure-stack-manage-vm-disks).
+- Scale up - Increase the size of the Azure Backup Server virtual machine from A series to D series, and increase the local storage [per the Azure Stack Hub virtual machine instructions](/azure-stack/user/azure-stack-manage-vm-disks).
 - Offload data - send older data to Azure and retain only the newest data on the storage attached to the Azure Backup Server.
 - Scale out - Add more Azure Backup Servers to protect the workloads.
 
@@ -66,9 +67,9 @@ If you want to scale your deployment, you have the following options:
 
 The Azure Backup Server virtual machine must be joined to a domain. A domain user with administrator privileges must install Azure Backup Server on the virtual machine.
 
-## Using an IaaS VM in Azure Stack
+## Using an IaaS VM in Azure Stack Hub
 
-When choosing a server for Azure Backup Server, start with a Windows Server 2022 Datacenter or Windows Server 2019 Datacenter gallery image. The article, [Create your first Windows virtual machine in the Azure portal](../virtual-machines/windows/quick-create-portal.md?toc=/azure/virtual-machines/windows/toc.json), provides a tutorial for getting started with the recommended virtual machine. The recommended minimum requirements for the server virtual machine (VM) should be: A2 Standard with two cores and 3.5-GB RAM.
+When choosing a server for Azure Backup Server, start with a Windows Server 2022 Datacenter or Windows Server 2019 Datacenter gallery image. The article, [Create your first Windows virtual machine in the Azure portal](../virtual-machines/windows/quick-create-portal.md?toc=/azure/virtual-machines/windows/toc.json), provides a tutorial for getting started with the recommended virtual machine. The recommended minimum requirements for the server virtual machine (VM) should be: A2 Standard with two cores and 3.5-GB RAM. Use DPM\MABS [capacity planner](https://www.microsoft.com/download/details.aspx?id=54301) to get the appropriate RAM size and accordingly choose the IaaS VM size.
 
 Protecting workloads with Azure Backup Server has many nuances. The [protection matrix for MABS](./backup-mabs-protection-matrix.md) helps explain these nuances. Before deploying the machine, read this article completely.
 
@@ -99,7 +100,7 @@ To edit the storage replication setting:
 
 There are two ways to download the Azure Backup Server installer. You can download the Azure Backup Server installer from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=55269). You can also download Azure Backup Server installer while you're configuring a Recovery Services vault. The following steps walk you through downloading the installer from the Azure portal while configuring a Recovery Services vault.
 
-1. From your Azure Stack virtual machine, [sign in to your Azure subscription in the Azure portal](https://portal.azure.com/).
+1. From your Azure Stack Hub virtual machine, [sign in to your Azure subscription in the Azure portal](https://portal.azure.com/).
 2. In the left-hand menu, select **All Services**.
 
     ![Choose the All Services option in main menu](./media/backup-mabs-install-azure-stack/click-all-services.png)
@@ -144,7 +145,7 @@ There are two ways to download the Azure Backup Server installer. You can downlo
 
 ## Extract Azure Backup Server install files
 
-After you've downloaded all files to your Azure Stack virtual machine, go to the download location. The first phase of installing Azure Backup Server is to extract the files.
+After you've downloaded all files to your Azure Stack Hub virtual machine, go to the download location. The first phase of installing Azure Backup Server is to extract the files.
 
 ![Download MABS installer](./media/backup-mabs-install-azure-stack/download-mabs-installer.png)
 

articles/backup/tutorial-backup-vm-at-scale.md

@@ -1,15 +1,15 @@
 ---
 title: Tutorial - Back up multiple Azure virtual machines by using Azure Backup
 description: In this tutorial, learn how to create a Recovery Services vault, define a backup policy, and simultaneously back up multiple virtual machines.
-ms.date: 02/26/2024
+ms.date: 04/23/2024
 ms.topic: tutorial
 ms.custom: mvc, engagement-fy24
 ms.service: backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
 
-# Tutotial: Back up multiple virtual machines by using the Azure portal 
+# Tutorial: Back up multiple virtual machines by using the Azure portal 
 
 This tutorial describes how to back up multiple virtual machines by using the Azure portal .
 

articles/confidential-computing/index.yml

@@ -28,7 +28,7 @@ landingContent:
             url: overview.md
           - text: What products are available?
             url: overview-azure-products.md
-          - text: Choose your confidential computing offering
+          - text: What can I use this for?
             url: use-cases-scenarios.md 
       - linkListType: quickstart
         links:

articles/container-registry/container-registry-tutorial-sign-build-push.md

@@ -41,16 +41,16 @@ In this tutorial:
     cp ./notation /usr/local/bin
     ```
 
-2. Install the Notation Azure Key Vault plugin `azure-kv` v1.0.2 on a Linux amd64 environment.
+2. Install the Notation Azure Key Vault plugin `azure-kv` v1.1.0 on a Linux amd64 environment.
 
     > [!NOTE]
     > The URL and SHA256 checksum for the Notation Azure Key Vault plugin can be found on the plugin's [release page](https://github.com/Azure/notation-azure-kv/releases).
 
     ```bash
-    notation plugin install --url https://github.com/Azure/notation-azure-kv/releases/download/v1.0.2/notation-azure-kv_1.0.2_linux_amd64.tar.gz --sha256sum f2b2e131a435b6a9742c202237b9aceda81859e6d4bd6242c2568ba556cee20e
+    notation plugin install --url https://github.com/Azure/notation-azure-kv/releases/download/v1.1.0/notation-azure-kv_1.1.0_linux_amd64.tar.gz --sha256sum 2fc959bf850275246b044203609202329d015005574fabbf3e6393345e49b884
     ```
 
-3. List the available plugins and confirm that the `azure-kv` plugin with version `1.0.2` is included in the list. 
+3. List the available plugins and confirm that the `azure-kv` plugin with version `1.1.0` is included in the list. 
 
     ```bash
     notation plugin ls
@@ -200,6 +200,28 @@ The following steps show how to create a self-signed certificate for testing pur
     ```bash
     notation sign --signature-format cose --id $KEY_ID --plugin azure-kv --plugin-config self_signed=true $IMAGE
     ```
+
+    To authenticate with AKV, by default, the following credential types if enabled will be tried in order:
+ 
+    - [Environment credential](/dotnet/api/azure.identity.environmentcredential)
+    - [Workload identity credential](/dotnet/api/azure.identity.workloadidentitycredential)
+    - [Managed identity credential](/dotnet/api/azure.identity.managedidentitycredential)
+    - [Azure CLI credential](/dotnet/api/azure.identity.azureclicredential)
+    
+    If you want to specify a credential type, use an additional plugin configuration called `credential_type`. For example, you can explicitly set `credential_type` to `azurecli` for using Azure CLI credential, as demonstrated below:
+    
+    ```bash
+    notation sign --signature-format cose --id $KEY_ID --plugin azure-kv --plugin-config self_signed=true --plugin-config credential_type=azurecli $IMAGE
+    ```
+
+    See below table for the values of `credential_type` for various credential types.
+
+    | Credential type              | Value for `credential_type` |
+    | ---------------------------- | -------------------------- |
+    | Environment credential       | `environment`              |
+    | Workload identity credential | `workloadid`               |
+    | Managed identity credential  | `managedid`                |
+    | Azure CLI credential         | `azurecli`                 |
     
 5. View the graph of signed images and associated signatures.
 

articles/container-registry/container-registry-tutorial-sign-trusted-ca.md

@@ -53,16 +53,16 @@ In this article:
     cp ./notation /usr/local/bin
     ```
 
-2. Install the Notation Azure Key Vault plugin `azure-kv` v1.0.2 on a Linux amd64 environment.
+2. Install the Notation Azure Key Vault plugin `azure-kv` v1.1.0 on a Linux amd64 environment.
 
     > [!NOTE]
     > The URL and SHA256 checksum for the Notation Azure Key Vault plugin can be found on the plugin's [release page](https://github.com/Azure/notation-azure-kv/releases).
 
     ```bash
-    notation plugin install --url https://github.com/Azure/notation-azure-kv/releases/download/v1.0.2/notation-azure-kv_1.0.2_linux_amd64.tar.gz --sha256sum f2b2e131a435b6a9742c202237b9aceda81859e6d4bd6242c2568ba556cee20e
+    notation plugin install --url https://github.com/Azure/notation-azure-kv/releases/download/v1.1.0/notation-azure-kv_1.1.0_linux_amd64.tar.gz --sha256sum 2fc959bf850275246b044203609202329d015005574fabbf3e6393345e49b884
     ```
 
-3. List the available plugins and confirm that the `azure-kv` plugin with version `1.0.2` is included in the list.
+3. List the available plugins and confirm that the `azure-kv` plugin with version `1.1.0` is included in the list.
     
     ```bash
     notation plugin ls
@@ -219,6 +219,28 @@ To import the certificate:
    notation sign --signature-format cose $IMAGE --id $KEY_ID --plugin azure-kv --plugin-config ca_certs=<ca_bundle_file> 
    ```
 
+   To authenticate with AKV, by default, the following credential types if enabled will be tried in order:
+ 
+   - [Environment credential](/dotnet/api/azure.identity.environmentcredential)
+   - [Workload identity credential](/dotnet/api/azure.identity.workloadidentitycredential)
+   - [Managed identity credential](/dotnet/api/azure.identity.managedidentitycredential)
+   - [Azure CLI credential](/dotnet/api/azure.identity.azureclicredential)
+    
+   If you want to specify a credential type, use an additional plugin configuration called `credential_type`. For example, you can explicitly set `credential_type` to `azurecli` for using Azure CLI credential, as demonstrated below:
+    
+   ```bash
+   notation sign --signature-format cose --id $KEY_ID --plugin azure-kv --plugin-config credential_type=azurecli $IMAGE
+   ```
+
+   See below table for the values of `credential_type` for various credential types.
+
+   | Credential type              | Value for `credential_type` |
+   | ---------------------------- | -------------------------- |
+   | Environment credential       | `environment`              |
+   | Workload identity credential | `workloadid`               |
+   | Managed identity credential  | `managedid`                |
+   | Azure CLI credential         | `azurecli`                 |
+
 6. View the graph of signed images and associated signatures. 
 
     ```bash