Merge pull request #289639 from MicrosoftDocs/main

11/1 11:00 AM IST Publish

Author: Saisang

articles/bastion/bastion-faq.md

@@ -171,9 +171,9 @@ Yes. See [About VM connections and features](vm-about.md#audio).
 
 Azure Bastion offers support for file transfer between your target VM and local computer using Bastion and a native RDP or SSH client. At this time, you can’t upload or download files using PowerShell or via the Azure portal. For more information, see [Upload and download files using the native client](vm-upload-download-native.md).
 
-### <a name="aadj"></a>Does Bastion hardening work with AADJ VM extension-joined VMs?
+### <a name="aadj"></a>Does Bastion work with Entra ID extension-joined VMs?
 
-This feature doesn't work with AADJ VM extension-joined machines using Microsoft Entra users. For more information, see [Sign in to a Windows virtual machine in Azure by using Microsoft Entra ID](../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#requirements).
+Bastion does work with Entra ID extension-joined VMs for Microsoft Entra users with RDP and SSH on the native client, and SSH only on the portal. Entra ID for RDP on the portal is not yet supported. For more information, see [Sign in to a Windows virtual machine in Azure by using Microsoft Entra ID](../active-directory/devices/howto-vm-sign-in-azure-ad-windows.md#requirements).
 
 ### <a name="rdscal-compatibility"></a>Is Bastion compatible with VMs set up as RDS session hosts?
 

articles/container-apps/log-streaming.md

@@ -62,14 +62,14 @@ You can stream the system or console logs for your container app. To stream the
 
 #### View container app system log stream
 
-This example uses the `--tail` argument to display the last 50 system log messages from the container app. Replace the \<placeholders\> with your container app's values.
+This example uses the `--tail` argument to display the last 50 system log messages from the container app. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp logs show \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
   --type system \
   --tail 50
 ```
@@ -78,22 +78,22 @@ az containerapp logs show \
 
 ```azurecli
 az containerapp logs show `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
   --type system `
   --tail 50
 ```
 
 ---
 
-This example displays a continuous live stream of system log messages from the container app using the `--follow` argument. Replace the \<placeholders\> with your container app's values.
+This example displays a continuous live stream of system log messages from the container app using the `--follow` argument. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp logs show \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
   --type system \
   --follow
 ```
@@ -102,8 +102,8 @@ az containerapp logs show \
 
 ```azurecli
 az containerapp logs show `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
   --type system `
   --follow
 ```
@@ -122,63 +122,63 @@ To connect to a container's console log stream in a container app with multiple
 | `--replica` | The replica name in the revision. |
 | `--container` | The container name to connect to. |
 
-You can get the revision names with the `az containerapp revision list` command. Replace the \<placeholders\> with your container app's values.
+You can get the revision names with the `az containerapp revision list` command. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp revision list \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
   --query "[].name"
 ```
 
 # [PowerShell](#tab/powershell)
 
 ```azurecli
 az containerapp revision list `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
   --query "[].name"
 ```
 
 ---
 
-Use the `az containerapp replica list` command to get the replica and container names. Replace the \<placeholders\> with your container app's values.
+Use the `az containerapp replica list` command to get the replica and container names. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp replica list \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
-  --revision <RevisionName> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
+  --revision <REVISION_NAME> \
   --query "[].{Containers:properties.containers[].name, Name:name}"
 ```
 
 # [PowerShell](#tab/powershell)
 
 ```azurecli
 az containerapp replica list `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
-  --revision <RevisionName> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
+  --revision <REVISION_NAME> `
   --query "[].{Containers:properties.containers[].name, Name:name}"
 ```
 
 ---
 
-Live stream the container console using the `az container app show` command with the `--follow` argument. Replace the \<placeholders\> with your container app's values.
+Live stream the container console using the `az container app show` command with the `--follow` argument. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp logs show \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
-  --revision <RevisionName> \
-  --replica <ReplicaName> \
-  --container <ContainerName> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
+  --revision <REVISION_NAME> \
+  --replica <REPLICA_NAME> \
+  --container <CONTAINER_NAME> \
   --type console \
   --follow
 ```
@@ -187,11 +187,11 @@ az containerapp logs show \
 
 ```azurecli
 az containerapp logs show  `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
-  --revision <RevisionName> `
-  --replica <ReplicaName> `
-  --container <ContainerName> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
+  --revision <REVISION_NAME> `
+  --replica <REPLICA_NAME> `
+  --container <CONTAINER_NAME> `
   --type console `
   --follow
 ```
@@ -200,17 +200,17 @@ az containerapp logs show  `
 
 Use `Ctrl-C` or `Cmd-C` to stop the live stream.
 
-View the last 50 console log messages using the `az containerapp logs show` command with the `--tail` argument. Replace the \<placeholders\> with your container app's values.
+View the last 50 console log messages using the `az containerapp logs show` command with the `--tail` argument. Replace the `<PLACEHOLDERS>` with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp logs show \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
-  --revision <RevisionName> \
-  --replica <ReplicaName> \
-  --container <ContainerName> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
+  --revision <REVISION_NAME> \
+  --replica <REPLICA_NAME> \
+  --container <CONTAINER_NAME> \
   --type console \
   --tail 50
 ```
@@ -219,11 +219,11 @@ az containerapp logs show \
 
 ```azurecli
 az containerapp logs show  `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
-  --revision <RevisionName> `
-  --replica <ReplicaName> `
-  --container <ContainerName> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
+  --revision <REVISION_NAME> `
+  --replica <REPLICA_NAME> `
+  --container <CONTAINER_NAME> `
   --type console `
   --tail 50
 ```
@@ -232,47 +232,47 @@ az containerapp logs show  `
 
 ### View environment system log stream
 
-Use the following command with the `--follow` argument to view the live system log stream from the Container Apps environment. Replace the \<placeholders\> with your environment values.
+Use the following command with the `--follow` argument to view the live system log stream from the Container Apps environment. Replace the `<PLACEHOLDERS>` with your environment values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp env logs show \
-  --name <ContainerAppEnvironmentName> \
-  --resource-group <ResourceGroup> \
+  --name <ENVIRONMENT_NAME> \
+  --resource-group <RESOURCE_GROUP> \
   --follow
 ```
 
 # [PowerShell](#tab/powershell)
 
 ```azurecli
 az containerapp env logs show  `
-  --name <ContainerAppEnvironmentName> `
-  --resource-group <ResourceGroup> `
+  --name <ENVIRONMENT_NAME> `
+  --resource-group <RESOURCE_GROUP> `
   --follow
 ```
 
 ---
 
 Use `Ctrl-C` or `Cmd-C` to stop the live stream.
 
-This example uses the `--tail` argument to display the last 50 environment system log messages. Replace the \<placeholders\> with your environment values.
+This example uses the `--tail` argument to display the last 50 environment system log messages. Replace the `<PLACEHOLDERS>` with your environment values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp env logs show \
-  --name <ContainerAppName> \
-  --resource-group <ResourceGroup> \
+  --name <CONTAINER_APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
   --tail 50
 ```
 
 # [PowerShell](#tab/powershell)
 
 ```azurecli
 az containerapp env logs show `
-  --name <ContainerAppName> `
-  --resource-group <ResourceGroup> `
+  --name <CONTAINER_APP_NAME> `
+  --resource-group <RESOURCE_GROUP> `
   --tail 50
 ```
 

articles/data-factory/tutorial-managed-virtual-network-on-premise-sql-server.md

@@ -258,6 +258,9 @@ data factory from the resources list.
    > [!NOTE]
    > When deploying your SQL Server on a virtual machine within a virtual network, it is essential to enhance your FQDN by appending **privatelink**. Otherwise, it will be conflicted with other records in the DNS setting. For example, you can simply modify the SQL Server's FQDN from **sqlserver.westus.cloudapp.azure.net** to **sqlserver.privatelink.westus.cloudapp.azure.net**.
 
+   > [!NOTE]
+   > Currently ApplicationIntent and MultiSubnetFailover are not supported in SQL connection properties.
+
 8. Create private endpoint.
 
 ## Create a linked service and test the connection

articles/healthcare-apis/known-issues.md

@@ -20,6 +20,7 @@ Refer to the table for details about resolution dates or possible workarounds.
 
 |Issue | Date discovered | Workaround | Date resolved |
 | :------------------------------------- | :------------ | :------------- | :------------- |
+|Customers can't access FHIR, DICOM, or Medtech through the portal. | October 31, 2024 1:00 pm PST | ARM calls are still operational, and there's no disruption to existing services. | -- |
 |For FHIR instances created after August 19,2024, diagnostic logs aren't available in log analytics workspace. |September 19,2024 9:00 am PST| -- | October 17,2024 9:00 am PST |
 |For FHIR instances created after August 19,2024, in metrics blade - Total requests, Total latency, and Total errors metrics are not being populated. |September 19,2024 9:00 am PST| -- | October 28,2024 9:00 am PST |
 |For FHIR instances created after August 19,2024, changes in private link configuration at the workspace level causes FHIR service to be stuck in 'Updating' state. |September 24,2024 9:00 am PST| Accounts deployed prior to September 27,2024 and facing this issue can follow the steps: <br> 1. Remove private endpoint from the Azure Health Data Services workspace having this issue. On Azure blade, go to Workspace and then click on Networking blade. In networking blade, select existing private link connection and click on 'Remove' <br> 2. Create new private connection to link to the workspace.| September 27,2024 9:00 am PST |

articles/iot-operations/troubleshoot/iot-operations-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: patricka
   ms.topic: faq
   ms.custom: references_regions
-  ms.date: 09/10/2024
+  ms.date: 10/30/2024
 
 title: Azure IoT Operations frequently asked questions
 summary: |
@@ -27,6 +27,9 @@ sections:
     - question: |
          Does Azure IoT Operations offer high availability across multi-node setups?
       answer: Yes, Azure IoT Operations workloads on K3s and HCI/AKS-Arc multi-node clusters support distribution of Azure IoT Operations workloads across multi-nodes setups in the preview version.
+    - question: |
+         Does Azure Device Registry Preview offer high availability across availability zones and regions?
+      answer: For information on high availability across availability zones and regions for ADR, see [Reliability in Azure Device Registry](../../reliability/reliability-device-registry.md).
     - question: |
          Can I migrate my IoT Edge workloads to Azure IoT Operations?
       answer: Currently, there's no documented migration path from IoT Edge to Azure IoT Operations. If you have any feature asks for Azure IoT Operations as part of your migration plans, share your requests on the [Azure IoT Operations public feedback forum](https://feedback.azure.com/d365community/forum/20152d6e-6a76-ee11-8179-000d3a1abe9e).

articles/operator-nexus/.openpublishing.redirection.operator-nexus.json

@@ -48,13 +48,23 @@
         {
             "source_path": "troubleshoot-enable-node-down-cleaner.md",
             "redirect_url": "concepts-storage",
-
             "redirect_document_id": false
         },
         {
             "source_path": "troubleshoot-bmm-node-reboot.md",
             "redirect_url": "troubleshoot-vm-error-after-reboot",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "reference-operator-nexus-fabric-skus.md",
+            "redirect_url": "reference-operator-nexus-skus",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "reference-operator-nexus-network-cloud-skus-us.md",
+            "redirect_url": "reference-operator-nexus-skus",
+            "redirect_document_id": false
         }
+
     ]
 }

articles/operator-nexus/TOC.yml

@@ -367,10 +367,8 @@
           href: reference-acl-configuration.md
         - name: Access Control List configuration examples
           href: reference-acl-examples.md
-    - name: Operator Nexus Network Fabric SKUs
-      href: reference-operator-nexus-fabric-skus.md
-    - name: Operator Nexus Network Cloud SKUs      
-      href: reference-operator-nexus-network-cloud-skus-us.md
+    - name: Operator Nexus SKUs
+      href: reference-operator-nexus-skus.md
 - name: Release Notes
   items:
     - name: 2024

articles/operator-nexus/concepts-compute.md

@@ -116,4 +116,4 @@ Azure Operator Nexus offers a group of on-premises cloud solutions that cater to
 
 ### Operator Nexus Network Cloud SKUs
 
-For Stock Keeping Unit (SKU) information please see [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-network-cloud-skus-us.md).
+For Stock Keeping Unit (SKU) information please see [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-skus.md).

articles/operator-nexus/howto-configure-cluster.md

@@ -74,7 +74,7 @@ az networkcloud cluster create --name "$CLUSTER_NAME" --location "$LOCATION" \
 | LAW_ID                    | Log Analytics Workspace ID for the Cluster                                                                            |
 | CLUSTER_LOCATION          | The local name of the Cluster                                                                                         |
 | AGGR_RACK_RESOURCE_ID     | RackID for Aggregator Rack                                                                                            |
-| AGGR_RACK_SKU             | Rack SKU for Aggregator Rack  *See [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-network-cloud-skus-us.md)                                                                                        |
+| AGGR_RACK_SKU             | Rack SKU for Aggregator Rack  *See [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-skus.md)                                                                                        |
 | AGGR_RACK_SN              | Rack Serial Number for Aggregator Rack                                                                                |
 | AGGR_RACK_LOCATION        | Rack physical location for Aggregator Rack                                                                            |
 | AGGR_RACK_BMM             | Used for single rack deployment only, empty for multi-rack                                                            |
@@ -83,7 +83,7 @@ az networkcloud cluster create --name "$CLUSTER_NAME" --location "$LOCATION" \
 | SA_USER                   | Storage Appliance admin user                                                                                          |
 | SA_SN                     | Storage Appliance Serial Number                                                                                       |
 | COMPX_RACK_RESOURCE_ID    | RackID for CompX Rack; repeat for each rack in compute-rack-definitions                                               |
-| COMPX_RACK_SKU            | Rack SKU for CompX Rack; repeat for each rack in compute-rack-definitions *See [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-network-cloud-skus-us.md)                                             |
+| COMPX_RACK_SKU            | Rack SKU for CompX Rack; repeat for each rack in compute-rack-definitions *See [Operator Nexus Network Cloud SKUs](./reference-operator-nexus-skus.md)                                             |
 | COMPX_RACK_SN             | Rack Serial Number for CompX Rack; repeat for each rack in compute-rack-definitions                                   |
 | COMPX_RACK_LOCATION       | Rack physical location for CompX Rack; repeat for each rack in compute-rack-definitions                               |
 | COMPX_SVRY_BMC_PASS       | CompX Rack ServerY Baseboard Management Controller (BMC) password; repeat for each rack in compute-rack-definitions and for each server in rack         |