Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into pauljewell-copy-blob

Author: pauljewellmsft

articles/active-directory/standards/index.yml

@@ -6,8 +6,8 @@ summary: Azure and Azure Active Directory offer compliance certifications. Learn
 metadata:
   title: Implement identity standards with Azure Active Directory
   description: "Azure and Azure Active Directory offer compliance certifications. Learn to configure your environment to meet governmental and industry standards."
-  manager: mtillman
-  ms.author: baselden
+  manager: martinco
+  ms.author: jricketts
   ms.collection: na
   ms.date: 04/29/2022
   ms.service: active-directory
@@ -32,6 +32,8 @@ landingContent:
             url: configure-azure-active-directory-for-fedramp-high-impact.md
           - text: Configure Azure Active Directory for CMMC compliance
             url: configure-azure-active-directory-for-cmmc-compliance.md
+          - text: Configure Azure Active Directory for HIPAA compliance
+            url: hipaa-configure-azure-active-directory-for-compliance.md
 
   # Card 
   - title: Understand NIST AALs
@@ -99,3 +101,15 @@ landingContent:
           - text: Configure Azure Active Directory to meet CMMC Level 2
             url: configure-cmmc-level-2-additional-controls.md
 
+  # Card
+  - title: Achieve HIPAA compliance
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Configure access control safeguards
+            url: hipaa-access-controls.md
+          - text: Configure audit control safeguards
+            url: hipaa-audit-controls.md
+          - text: Configure other safeguards
+            url: hipaa-other-controls.md
+            

articles/load-balancer/skus.md

@@ -13,7 +13,7 @@ ms.author: mbender
 # Azure Load Balancer SKUs
 
 >[!Important]
->On September 30, 2025, Basic Load Balancer will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer/). If you are currently using Basic Load Balancer, make sure to upgrade to Standard Load Balancer prior to the retirement date. This article will help guide you through the upgrade process. 
+>On September 30, 2025, Basic Load Balancer will be retired. For more information, see the [official announcement](https://azure.microsoft.com/updates/azure-basic-load-balancer-will-be-retired-on-30-september-2025-upgrade-to-standard-load-balancer/). If you are currently using Basic Load Balancer, make sure to upgrade to Standard Load Balancer prior to the retirement date. For guidance on upgrading, visit [Upgrading from Basic Load Balancer - Guidance](load-balancer-basic-upgrade-guidance.md).
 
 Azure Load Balancer has three SKUs.
 

articles/machine-learning/azure-machine-learning-ci-image-release-notes.md

@@ -20,6 +20,22 @@ Azure Machine Learning checks and validates any machine learning packages that m
 
 Main updates provided with each image version are described in the below sections.
 
+## April 7, 2023
+Version: `23.04.07`
+
+Main changes:
+
+- `Azure Machine Learning SDK` to version `1.49.0`
+- `Certifi` updated to `2022.9.24`
+- `.Net` updated from `3.1` (EOL) to `6.0`
+- `Pyspark` update to `3.3.1` (mitigating log4j 1.2.17 and common-text-1.6 vulnerabilities)
+- Default `intellisense` to Python `3.10` on the CI
+- Bug fixes and stability improvements
+
+Main environment specific updates:
+
+- `Azureml_py38` environment is now the default.
+
 ## January 19, 2023
 Version: `23.01.19`
 

articles/machine-learning/how-to-create-manage-compute-instance.md

@@ -742,41 +742,44 @@ To create a compute instance, you'll need permissions for the following actions:
 * *Microsoft.MachineLearningServices/workspaces/computes/write*
 * *Microsoft.MachineLearningServices/workspaces/checkComputeNameAvailability/action*
 
-### Audit and observe compute instance version
+## Audit and observe compute instance version
 
 Once a compute instance is deployed, it does not get automatically updated. Microsoft [releases](azure-machine-learning-ci-image-release-notes.md) new VM images on a monthly basis. To understand options for keeping recent with the latest version, see [vulnerability management](concept-vulnerability-management.md#compute-instance). 
 
-To keep track of whether an instance's operating system version is current, you could query its version using the Studio UI. In your workspace in Azure Machine Learning studio, select Compute, then select compute instance on the top. Select a compute instance's compute name to see its properties including the current operating system. Enable 'audit and observe compute instance os version' under the previews management panel to see these preview properties.
+To keep track of whether an instance's operating system version is current, you could query its version using the CLI, SDK or Studio UI. 
 
-Administrators can use [Azure Policy](policy-reference.md) definitions to audit instances that are running on outdated operating system versions across workspaces and subscriptions. The following is a sample policy:
+# [Studio UI](#tab/azure-studio)
 
-```json
-{
-    "mode": "All",
-    "policyRule": {
-      "if": {
-        "allOf": [
-          {
-            "field": "type",
-            "equals": "Microsoft.MachineLearningServices/workspaces/computes"
-          },
-          {
-            "field": "Microsoft.MachineLearningServices/workspaces/computes/computeType",
-            "equals": "ComputeInstance"
-          },
-          {
-            "field": "Microsoft.MachineLearningServices/workspaces/computes/osImageMetadata.isLatestOsImageVersion",
-            "equals": "false"
-          }
-        ]
-      },
-      "then": {
-        "effect": "Audit"
-      }
-    }
-}    
+In your workspace in Azure Machine Learning studio, select Compute, then select compute instance on the top. Select a compute instance's compute name to see its properties including the current operating system.
+
+# [Python SDK](#tab/python)
+
+[!INCLUDE [sdk v2](../../includes/machine-learning-sdk-v2.md)]
+
+```python
+from azure.ai.ml.entities import ComputeInstance, AmlCompute
+
+# Display operating system version
+instance = ml_client.compute.get("myci")
+print instance.os_image_metadata
 ```
 
+For more information on the classes, methods, and parameters used in this example, see the following reference documents:
+
+* [`AmlCompute` class](/python/api/azure-ai-ml/azure.ai.ml.entities.amlcompute)
+* [`ComputeInstance` class](/python/api/azure-ai-ml/azure.ai.ml.entities.computeinstance)
+
+# [Azure CLI](#tab/azure-cli)
+
+[!INCLUDE [cli v2](../../includes/machine-learning-cli-v2.md)]
+
+```azurecli
+az ml compute show --name "myci"
+```
+---
+
+IT administrators can use [Azure Policy](./../governance/policy/overview.md) to monitor the inventory of instances across workspaces in Azure Policy compliance portal. Assign the built-in policy [Audit Azure Machine Learning Compute Instances with an outdated operating system](https://ms.portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff110a506-2dcb-422e-bcea-d533fc8c35e2) on an Azure subscription or Azure management group scope.
+
 ## Next steps
 
 * [Access the compute instance terminal](how-to-access-terminal.md)

articles/reliability/availability-zones-baseline.md

@@ -20,21 +20,24 @@ When creating reliable workloads, you can choose at least one of the following a
 
  - **Zone-redundant**.  A zone-redundant configuration provides resources that are replicated or distributed across zones automatically.
 
-In addition to the two availability zone options, zonal and zone-redundant, Azure offers **Global services**, meaning that they're available globally regardless of region. Because these services are always available across regions, they're resilient to both regional and zonal outages. You don't need to configure or enable these services.
+
+In addition to the two availability zone options, zonal and zone-redundant, Azure offers **Global services**, meaning that they're available globally regardless of region. Because these services are always available across regions, they're resilient to both regional and zonal outages.
 
 To see which Azure services support availability zones, see [Availability zone service and regional support](availability-zones-service-support.md).
 
 
 >[!NOTE] 
->When you don't select a zone configuration for your resource, whether zonal or zone-redundant, the resource and its sub-components won't be zone resilient and can go down during a zonal outage in that region.
+>When you don't select a zone configuration for your resource, either zonal or zone-redundant, the resource and its sub-components won't be zone resilient and can go down during a zonal outage in that region.
 
 ## Considerations for migrating to availability zone support
 
- There are many ways to create a reliable Azure application with availability zones that meet both SLAs and reliability targets.  Follow the steps in this section to choose the right approach for your needs based on technical and regulatory considerations, service capabilities, data residency, compliance requirements, and latency. 
+
+There are a number of possible ways to create a reliable Azure application with availability zones that meet both SLAs and reliability targets. Follow the steps below to choose the right approach for your needs based on technical and regulatory considerations, service capabilities, data residency, compliance requirements, and latency. 
 
 ### Step 1: Check if the Azure region supports availability zones
 
-In this first step, you need to [validate](availability-zones-service-support.md) that your selected Azure region support availability zones and the required Azure services for your application.
+In this first step, you'll need to [validate](availability-zones-service-support.md) that your selected Azure region support availability zones as well as the required Azure services for your application.
+
 
 If your region supports availability zones, we highly recommended that you configure your workload for availability zones.  If your region doesn't support availability zones, you'll need to use [Azure Resource Mover guidance](/azure/resource-mover/move-region-availability-zone) to migrate to a region that offers availability zone support.
 
@@ -50,16 +53,16 @@ To check for regional support of services, see [Products available by region](ht
 
 To list the available VM SKUs by Azure region and zone, see [Check VM SKU availability](/azure/virtual-machines/windows/create-powershell-availability-zone#check-vm-sku-availability). 
 
-If your region doesn't support the services and SKUs that your application requires, you'll need to go back to [Step 1: Check the product availability in the Azure region](#step-1-check-if-the-azure-region-supports-availability-zones) to find a new region.  
+If your region doesn't support the services and SKUs that your application requires, you'll need to go back to [Step 1: Check the product availability in the Azure region](#step-1-check-if-the-azure-region-supports-availability-zones) to find a new region that supports the services and SKUs that your application requires. We highly recommended that you configure your workload with zone-redundancy. 
 
- the services and SKUs that your application requires, we highly recommended that you configure your workload with zone-redundancy. For zonal high availability of Azure IaaS Virtual Machines, use [Virtual Machine Scale Sets Flex](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes) to spread VMs across multiple availability zones.
+For zonal high availability of Azure IaaS Virtual Machines, use [Virtual Machine Scale Sets (VMSS) Flex](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes) to spread VMs across multiple availability zones.
 
 
 ### Step 3: Consider your application requirements
 
 In this final step, you'll determine, based on application requirements, which kind of availability zone support is most suitable to your application.
 
-Below are three important questions that can help you choose the correct availability zone deployment:
+Below are three important questions that will help you choose the correct availability zone deployment:
 
 #### Does your application include latency sensitive components?
 
@@ -77,16 +80,22 @@ For a [distributed microservices model](/azure/architecture/guide/architecture-s
 With a zonal deployment, you must:
 
 1. Identify latency sensitive resources or services in your architecture.
+
 1. Confirm that the latency sensitive resources or services support zonal deployment.
+
 1. Co-locate the latency sensitive resources or services in same zone. Other services in your architecture may continue to remain zone redundant. 
-1. Replicate the latency sensitive zonal services across multiple availability zones to ensure you're zone resilient. 
+
+1. Replicate the latency sensitive zonal services across multiple availability zones to ensure zone resiliency. 
+
 1. Load balance between the multiple zonal deployments with a standard or global load balancers. 
 
 If the Azure service supports availability zones, we highly recommend that you use zone-redundancy by spreading nodes across the zones to get higher uptime SLA and protection against zonal outages.  
 
-For a 3-tier application, it's important to understand the state (stateful or stateless) of each tier (application, business, and data). State knowledge helps you to architect in alignment with the best practices and guidance according to the type of workload. 
 
-For specialized workload on Azure as below examples, refer to the respective landing zone architecture guidance and best practices. 
+For a 3-tier application it is important to understand the application, business, and data tiers; as well as their state (stateful or stateless) to architect in alignment with the best practices and guidance according to the type of workload. 
+
+For specialized workloads on Azure as below examples, please refer to the respective landing zone architecture guidance and best practices. 
+
 
 - SAP  
     - [SAP workload configurations with Azure Availability Zones](/azure/sap/workloads/high-availability-zones)
@@ -105,7 +114,7 @@ For specialized workload on Azure as below examples, refer to the respective lan
     - [Oracle on Azure architecture design](/azure/architecture/solution-ideas/articles/oracle-on-azure-start-here  )
 
 
-#### Do you want to achieve BCDR in the same Azure region due to compliance, data residency, or governance requirements? 
+#### Do you want to achieve Business Continuity and Disaster Recovery in the same Azure region due to compliance, data residency, or governance requirements? 
 
 To achieve business continuity and disaster recovery within the same region and when there **is no regional pair**, we highly recommend that you configure your workload with zone-redundancy. A single-region approach is also applicable to certain industries that have strict data residency and governance requirements within the same Azure region.  To learn how to replicate, failover, and failback Azure virtual machines from one availability zone to another within the same Azure region, see [Enable Azure VM disaster recovery between availability zones](/azure/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery).
 

articles/storage/.openpublishing.redirection.storage.json

@@ -90,6 +90,41 @@
             "redirect_url": "/azure/storage/blobs/data-lake-storage-best-practices",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-use-azcopy-troubleshoot.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/storage-use-azcopy-troubleshoot",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-explorer-troubleshooting.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/storage-explorer-troubleshooting",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/troubleshoot-storage-performance.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/troubleshoot-storage-performance",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/troubleshoot-storage-availability.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/troubleshoot-storage-availability",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/troubleshoot-storage-client-application-errors.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/troubleshoot-storage-client-application-errors",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-monitoring-diagnosing-troubleshooting.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/storage-monitoring-diagnosing-troubleshooting",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/troubleshoot-latency-storage-analytics-logs.md",
+            "redirect_url": "/troubleshoot/azure/azure-storage/troubleshoot-latency-storage-analytics-logs",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/storage/blobs/data-lake-storage-quickstart-create-account.md",
             "redirect_url": "/azure/storage/common/storage-account-create",