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

duongau · duongau · commit 3bfe11620edd · 2024-02-29T12:21:40.000-08:00
diff --git a/articles/azure-netapp-files/backup-introduction.md b/articles/azure-netapp-files/backup-introduction.md
@@ -48,6 +48,7 @@ Azure NetApp Files backup is supported for the following regions:
 * Japan East
 * Japan West
 * Korea Central
+* Korea South
 * North Central US
 * North Europe
 * Norway East
@@ -63,6 +64,7 @@ Azure NetApp Files backup is supported for the following regions:
 * UAE Central
 * UAE North
 * UK South
+* UK West
 * West Europe
 * West US
 * West US 2
diff --git a/articles/chaos-studio/TOC.yml b/articles/chaos-studio/TOC.yml
@@ -4,9 +4,17 @@
   items:
   - name: What is Azure Chaos Studio?
     href: chaos-studio-overview.md
+  - name: Chaos experiments
+    href: chaos-studio-chaos-experiments.md
+  - name: Faults and actions
+    href: chaos-studio-faults-actions.md
+  - name: Targets and capabilities
+    href: chaos-studio-targets-capabilities.md
+  - name: Target selection
+    href: chaos-studio-target-selection.md
 - name: Quickstart
   items:
-  - name: Create and run a chaos experiment using Azure Chaos Studio 
+  - name: Create and run a chaos experiment 
     href: chaos-studio-quickstart-azure-portal.md
 - name: Tutorials
   items:
@@ -28,68 +36,60 @@
     href: chaos-studio-bicep.md
   - name: Azure policy definitions
     href: sample-policy-targets.md
-- name: Concepts
+- name: Security and Reliability
   items:
-  - name: Chaos experiments
-    href: chaos-studio-chaos-experiments.md
-  - name: Faults and actions
-    href: chaos-studio-faults-actions.md
-  - name: Targets and capabilities
-    href: chaos-studio-targets-capabilities.md
-  - name: Target selection
-    href: chaos-studio-target-selection.md
   - name: Permissions and security
     href: chaos-studio-permissions-security.md
   - name: Private networking
     href: chaos-studio-private-networking.md
-  - name: Regional availability
-    href: chaos-studio-region-availability.md
   - name: Reliability 
     href: ../reliability/reliability-chaos-studio.md?toc=/azure/chaos-studio/toc.json&bc=/azure/chaos-studio/breadcrumb/toc.json
-- name: How-to guides
+- name: Create and run experiments
   items:
-  - name: Create and run experiment - Service-direct faults
+  - name: Service-direct faults
     items:
     - name: Portal
       href: chaos-studio-tutorial-service-direct-portal.md
     - name: CLI
       href: chaos-studio-tutorial-service-direct-cli.md
-  - name: Create and run experiment - Agent-based faults
+  - name: Agent-based faults
     items:
     - name: Portal
       href: chaos-studio-tutorial-agent-based-portal.md
     - name: CLI
       href: chaos-studio-tutorial-agent-based-cli.md
-  - name: Create and run experiment - Chaos Mesh faults on AKS
+  - name: Chaos Mesh faults on AKS
     items:
     - name: Portal
       href: chaos-studio-tutorial-aks-portal.md
     - name: CLI
       href: chaos-studio-tutorial-aks-cli.md
-  - name: Create and run experiment - Dynamic targeting
+  - name: Dynamic targeting
     items:
     - name: Portal
       href: chaos-studio-tutorial-dynamic-target-portal.md
     - name: CLI 
       href: chaos-studio-tutorial-dynamic-target-cli.md
-  - name: Experiment templates
-    items: 
-    - name: Use a chaos experiment template to induce an outage on an Azure Active Directory instance
-      href: chaos-studio-tutorial-aad-outage-portal.md
-    - name: Use a chaos experiment template to take down Virtual Machine Scale Set availability zones with autoscale disabled
-      href: chaos-studio-tutorial-availability-zone-down-portal.md
-  - name: Telemetry
-    items:
-    - name: Set up your Chaos Experiment to emit telemetry to Azure Monitor
-      href: chaos-studio-set-up-azure-monitor.md
-    - name: Set up your Agent-Based Chaos Experiment to emit telemetry to App Insights
-      href: chaos-studio-set-up-app-insights.md
-  - name: Configure an experiment using customer-managed keys (CMK)
-    href: chaos-studio-configure-customer-managed-keys.md
-  - name: Set up an agent-based chaos experiment using private link
-    href: chaos-studio-private-link-agent-service.md
-  - name: Troubleshoot common issues
-    href: troubleshooting.md
+- name: Use Chaos experiment templates
+  items: 
+  - name: Use a chaos experiment template to induce an outage on an Azure Active Directory instance
+    href: chaos-studio-tutorial-aad-outage-portal.md
+  - name: Use a chaos experiment template to take down Virtual Machine Scale Set availability zones with autoscale disabled
+    href: chaos-studio-tutorial-availability-zone-down-portal.md
+- name: Manage and Monitor experiments
+  items:
+    - name: Emit Chaos experiment telemetry
+      items:
+      - name: Set up your Chaos Experiment to emit telemetry to Azure Monitor
+        href: chaos-studio-set-up-azure-monitor.md
+      - name: Set up your Agent-Based Chaos Experiment to emit telemetry to App Insights
+        href: chaos-studio-set-up-app-insights.md
+    - name: Configure an experiment using customer-managed keys (CMK)
+      href: chaos-studio-configure-customer-managed-keys.md
+    - name: Set up an agent-based chaos experiment using private link
+      href: chaos-studio-private-link-agent-service.md
+    - name: Troubleshoot common issues
+      href: troubleshooting.md
 - name: Reference
   items:
   - name: Fault library
@@ -98,18 +98,22 @@
     href: chaos-studio-fault-providers.md
   - name: Version compatibility
     href: chaos-studio-versions.md
+  - name: Regional availability
+    href: chaos-studio-region-availability.md
   - name: Limitations and known issues
     href: chaos-studio-limitations.md
   - name: Service limits
     href: chaos-studio-service-limits.md
   - name: REST API documentation
     href: /rest/api/chaosstudio/
-  - name: Python SDK
-    href: /python/api/azure-mgmt-chaos/
-  - name: .NET SDK
-    href: /dotnet/api/overview/azure/resourcemanager.chaos-readme?view=azure-dotnet-preview&preserve-view=true
-  - name: JavaScript SDK
-    href: https://www.npmjs.com/package/@azure/arm-chaos/
+  - name: SDKs
+    items:
+    - name: Python SDK
+      href: /python/api/azure-mgmt-chaos/
+    - name: .NET SDK
+      href: /dotnet/api/overview/azure/resourcemanager.chaos-readme?view=azure-dotnet-preview&preserve-view=true
+    - name: JavaScript SDK
+      href: https://www.npmjs.com/package/@azure/arm-chaos/
 - name: Resources
   items:
   - name: Service updates
diff --git a/articles/chaos-studio/chaos-studio-quickstart-dns-outage.md b/articles/chaos-studio/chaos-studio-quickstart-dns-outage.md
@@ -10,11 +10,11 @@ ms.reviewer: prashabora
 ms.service: chaos-studio
 ---
 
-# Quickstart: Replicate a DNS outage by using the NSG fault
+# Replicate a DNS outage by using the NSG fault
 
 The network security group (NSG) fault enables you to modify your existing NSG rules as part of a chaos experiment in Azure Chaos Studio. By using this fault, you can block network traffic to your Azure resources and simulate a loss of connectivity or outages of dependent resources.
 
-In this quickstart, you create a chaos experiment that blocks all traffic to external (internet) DNS servers for 15 minutes. With this experiment, you can validate that resources connected to the Azure virtual network associated with the target NSG don't have a dependency on external DNS servers. In this way, you can validate one of the risk-threat model requirements.
+This article walks you through creating a chaos experiment that blocks all traffic to external (internet) DNS servers for 15 minutes. You can validate that resources connected to the Azure virtual network associated with the target NSG don't have a dependency on external DNS servers. In this way, you can validate one of the risk-threat model requirements.
 
 ## Prerequisites
 
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md
@@ -67,7 +67,72 @@ For example: `https://myworkspace-myfhirserver.fhir.azurehealthcareapis.com/Pati
 After you've found the record you want to restore, use the `PUT` operation to recreate the resource with the same ID, or use the `POST` operation to make a new resource with the same information.
  
 > [!NOTE]
-> There is no time-based expiration for history/soft delete data. The only way to remove history/soft deleted data is with a hard delete or the purge history operation.
+> There is no time-based expiration for history/soft delete data. The only way to remove history/soft deleted data is with a hard delete or the purge history operation.\
+
+## Batch Bundles 
+In FHIR, bundles can be considered as a container that holds multiple resources. Batch bundles enable users to submit a set of actions to be performed on a server in single HTTP request/response.
+
+A batch bundle interaction with FHIR service is performed with HTTP POST command at base URL.  
+```rest
+POST {{fhir_url}} 
+{ 
+  "resourceType": "Bundle", 
+  "type": "batch", 
+  "entry": [ 
+    { 
+      "resource": { 
+        "resourceType": "Patient", 
+        "id": "patient-1", 
+        "name": [ 
+          { 
+            "given": ["Alice"], 
+            "family": "Smith" 
+          } 
+        ], 
+        "gender": "female", 
+        "birthDate": "1990-05-15" 
+      }, 
+      "request": { 
+        "method": "POST", 
+        "url": "Patient" 
+      } 
+    }, 
+    { 
+      "resource": { 
+        "resourceType": "Patient", 
+        "id": "patient-2", 
+        "name": [ 
+          { 
+            "given": ["Bob"], 
+            "family": "Johnson" 
+          } 
+        ], 
+        "gender": "male", 
+        "birthDate": "1985-08-23" 
+      }, 
+      "request": { 
+        "method": "POST", 
+        "url": "Patient" 
+      } 
+    } 
+   } 
+  ] 
+} 
+```
+
+In the case of a batch, each entry is treated as an individual interaction or operation. 
+> [!NOTE]
+> For batch bundles there should be no interdependencies between different entries in FHIR bundle. The success or failure of one entry should not impact the success or failure of another entry.
+
+### Batch bundle parallel processing in public preview 
+
+Currently batch bundles are executed serially in FHIR service. To improve performance and throughput, we're enabling parallel processing of batch bundles in public preview.  
+To use the capability of parallel batch bundle processing-
+* Set header “x-bundle-processing-logic” value to “parallel”. 
+* Ensure there's no overlapping resource ID that is executing on DELETE, POST, PUT or PATCH operations in the same bundle.
+
+> [!IMPORTANT]
+> Bundle parallel processing is currently in public preview. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review Supplemental Terms of Use for Microsoft Azure Previews 
 
 ## Patch and Conditional Patch
 
@@ -162,7 +227,8 @@ Content-Type: `application/json`
 ```
 
 ## Performance consideration with Conditional operations
-Conditional interactions can be complex and performance-intensive. To enhance the latency of queries involving conditional interactions, you have the option to utilize the request header **x-conditionalquery-processing-logic** . Setting this header to **parallel** allows concurrent execution of queries with conditional interactions.
+1. Conditional interactions can be complex and performance-intensive. To enhance the latency of queries involving conditional interactions, you have the option to utilize the request header **x-conditionalquery-processing-logic** . Setting this header to **parallel** allows concurrent execution of queries with conditional interactions.
+2. **x-ms-query-latency-over-efficiency** header value when set to "true", all queries are executed using maximum supported parallelism, which forces the scan of physical partitions to be executed concurrently. This feature was designed for accounts with a high number of physical partitions which queries can take longer due to the number of physical segments that need to be scanned. 
 
 ## Next steps
 
diff --git a/articles/machine-learning/how-to-create-workspace-template.md b/articles/machine-learning/how-to-create-workspace-template.md
@@ -7,10 +7,10 @@ ms.service: machine-learning
 ms.subservice: enterprise-readiness
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell, devx-track-arm-template, devx-track-azurecli
-ms.author: deeikele
-author: deeikele
-ms.reviewer: larryfr
-ms.date: 11/09/2022
+ms.author: larryfr
+author: Blackmist
+ms.reviewer: deeikele
+ms.date: 02/29/2024
 #Customer intent: As a DevOps person, I need to automate or customize the creation of Azure Machine Learning by using templates.
 ---
 
@@ -39,7 +39,7 @@ For more information, see [Deploy an application with Azure Resource Manager tem
 
     ```json
     "type": "Microsoft.MachineLearningServices/workspaces",
-    "apiVersion": "2020-03-01",
+    "apiVersion": "2023-10-01",
     ```
 
 ### Multiple workspaces in the same VNet
@@ -188,43 +188,43 @@ For more information, see [Customer-managed keys](concept-customer-managed-keys.
 > 
 > For steps on creating the vault and key, see [Configure customer-managed keys](how-to-setup-customer-managed-keys.md).
 
-__To get the values__ for the `cmk_keyvault` (ID of the Key Vault) and the `resource_cmk_uri` (key URI) parameters needed by this template, use the following steps:	
+__To get the values__ for the `cmk_keyvault` (ID of the Key Vault) and the `resource_cmk_uri` (key URI) parameters needed by this template, use the following steps:    
 
-1. To get the Key Vault ID, use the following command:	
+1. To get the Key Vault ID, use the following command:    
 
-    # [Azure CLI](#tab/azcli)	
+    # [Azure CLI](#tab/azcli)    
     
-    ```azurecli	
-    az keyvault show --name <keyvault-name> --query 'id' --output tsv	
-    ```	
+    ```azurecli    
+    az keyvault show --name <keyvault-name> --query 'id' --output tsv    
+    ```    
     
-    # [Azure PowerShell](#tab/azpowershell)	
+    # [Azure PowerShell](#tab/azpowershell)    
     
-    ```azurepowershell	
-    Get-AzureRMKeyVault -VaultName '<keyvault-name>'	
-    ```	
-    ---	
+    ```azurepowershell    
+    Get-AzureRMKeyVault -VaultName '<keyvault-name>'    
+    ```    
+    ---    
 
-    This command returns a value similar to `/subscriptions/{subscription-guid}/resourceGroups/<resource-group-name>/providers/Microsoft.KeyVault/vaults/<keyvault-name>`.	
+    This command returns a value similar to `/subscriptions/{subscription-guid}/resourceGroups/<resource-group-name>/providers/Microsoft.KeyVault/vaults/<keyvault-name>`.    
 
-1. To get the value for the URI for the customer managed key, use the following command:	
+1. To get the value for the URI for the customer managed key, use the following command:    
 
-    # [Azure CLI](#tab/azcli)	
+    # [Azure CLI](#tab/azcli)    
     
-    ```azurecli	
-    az keyvault key show --vault-name <keyvault-name> --name <key-name> --query 'key.kid' --output tsv	
-    ```	
+    ```azurecli    
+    az keyvault key show --vault-name <keyvault-name> --name <key-name> --query 'key.kid' --output tsv    
+    ```    
     
-    # [Azure PowerShell](#tab/azpowershell)	
+    # [Azure PowerShell](#tab/azpowershell)    
     
-    ```azurepowershell	
-    Get-AzureKeyVaultKey -VaultName '<keyvault-name>' -KeyName '<key-name>'	
-    ```	
-    ---	
+    ```azurepowershell    
+    Get-AzureKeyVaultKey -VaultName '<keyvault-name>' -KeyName '<key-name>'    
+    ```    
+    ---    
 
-  This command returns a value similar to `https://mykeyvault.vault.azure.net/keys/mykey/{guid}`.	
+  This command returns a value similar to `https://mykeyvault.vault.azure.net/keys/mykey/{guid}`.    
 
-> [!IMPORTANT]	
+> [!IMPORTANT]    
 > Once a workspace has been created, you cannot change the settings for confidential data, encryption, key vault ID, or key identifiers. To change these values, you must create a new workspace using the new values.
 
 To enable use of Customer Managed Keys, set the following parameters when deploying the template:
