Merge pull request #287900 from MicrosoftDocs/main

Taojunshen · web-flow · commit 435fcc05bcd7 · 2024-10-05T00:59:26.000+08:00
10/4/2024 AM Publish
diff --git a/articles/container-apps/dapr-overview.md b/articles/container-apps/dapr-overview.md
@@ -6,7 +6,7 @@ author: hhunter-ms
 ms.service: azure-container-apps
 ms.custom: build-2023
 ms.topic: conceptual
-ms.date: 08/05/2024
+ms.date: 10/04/2024
 ---
 
 # Microservice APIs powered by Dapr
@@ -46,6 +46,22 @@ To learn more about using _alpha_ Dapr APIs and features, [see the Dapr FAQ][dap
 | [**Secrets**][dapr-secrets]                           | GA | Access secrets from your application code or reference secure values in your Dapr components.                                                                   |
 | [**Configuration**][dapr-config]                           | GA | Retrieve and subscribe to application configuration items for supported configuration stores.                                                                   |
 
+### Compatible SDKs
+
+Dapr's latest client SDK packages are compatible with Azure Container Apps. You can use any of the [supported, GA Dapr APIs](#managed-apis) with the following Dapr client SDK versions:
+
+| Language | SDK version |
+| -------- | ------- |
+| Java | 1.12.0 | 
+| Go | 1.11.0 | 
+| Python | 1.14.0 |
+| .NET | 1.14.0 | 
+| JavaScript | 3.3.1 | 
+| Rust | 0.15.1 | 
+
+> [!NOTE] 
+> Currently, the Dapr server extensions, actor, and workflow SDK packages are not compatible with Azure Container Apps. [Learn more about all of the Dapr SDK packages.](https://docs.dapr.io/developing-applications/sdks/)
+
 [!INCLUDE [component-support](~/reusable-content/ce-skilling/azure/includes/dapr-in-azure/dapr-support-policy.md)]
 
 ### Tooling
diff --git a/articles/container-apps/media/workload-profiles/azure-container-apps-workload-profiles-environment-v2.png b/articles/container-apps/media/workload-profiles/azure-container-apps-workload-profiles-environment-v2.png
diff --git a/articles/container-apps/media/workload-profiles/azure-container-apps-workload-profiles-environment.png b/articles/container-apps/media/workload-profiles/azure-container-apps-workload-profiles-environment.png
diff --git a/articles/container-apps/workload-profiles-manage-portal.md b/articles/container-apps/workload-profiles-manage-portal.md
@@ -38,14 +38,13 @@ Learn to manage a [workload profiles](./workload-profiles-overview.md) environme
 
 1. Configure the new environment.
 
-    :::image type="content" source="media/workload-profiles/azure-container-apps-workload-profiles-environment.png" alt-text="Screenshot of create an Azure Container Apps workload profiles environment window.":::
+    :::image type="content" source="media/workload-profiles/azure-container-apps-workload-profiles-environment-v2.png" alt-text="Screenshot of create an Azure Container Apps workload profiles environment window.":::
 
     Enter the following values to create your environment.
 
     | Property | Value |
     | --- | --- |
     | Environment name | Enter an environment name. |
-    | Environment type| Select **Workload profiles** |
   
     Select the new **Workload profiles** tab at the top of this section.
 
diff --git a/articles/firewall-manager/dns-settings.md b/articles/firewall-manager/dns-settings.md
@@ -112,8 +112,6 @@ To configure DNS proxy, you must configure your virtual network DNS servers sett
 4. Review the **DNS servers** configuration to make sure that the settings are appropriate for your environment.
 5. Select **Save**.
 
-:::image type="content" source="../firewall/media/dns-settings/dns-proxy.png" alt-text="Screenshot showing settings for the DNS proxy.":::
-
 #### [CLI](#tab/azure-devops-cli)
 
 You can use the Azure CLI to configure DNS proxy settings in Azure Firewall. You can also use it to update virtual networks to use Azure Firewall as the DNS server.
diff --git a/articles/firewall/dns-settings.md b/articles/firewall/dns-settings.md
@@ -115,8 +115,6 @@ To configure DNS proxy, you must configure your virtual network DNS servers sett
 4. Review the **DNS servers** configuration to make sure that the settings are appropriate for your environment.
 5. Select **Save**.
 
-:::image type="content" source="../firewall/media/dns-settings/dns-proxy.png" alt-text="Screenshot showing settings for the DNS proxy.":::
-
 #### [CLI](#tab/azure-devops-cli)
 
 You can use the Azure CLI to configure DNS proxy settings in Azure Firewall. You can also use it to update virtual networks to use Azure Firewall as the DNS server.
diff --git a/articles/firewall/media/dns-settings/dns-proxy.png b/articles/firewall/media/dns-settings/dns-proxy.png
diff --git a/articles/hdinsight/hdinsight-component-versioning.md b/articles/hdinsight/hdinsight-component-versioning.md
@@ -3,7 +3,7 @@ title: Open-source components and versions - Azure HDInsight
 description: Learn about the open-source components and versions in Azure HDInsight.
 ms.service: azure-hdinsight
 ms.topic: conceptual
-ms.date: 09/10/2024
+ms.date: 10/04/2024
 ---
 
 # Azure HDInsight versions
@@ -18,7 +18,6 @@ This table lists the versions of HDInsight that are available in the Azure porta
 | --- | --- | --- | --- | --- | --- | ---|
 | [HDInsight 5.1](./hdinsight-5x-component-versioning.md) |Ubuntu 18.0.4 LTS |November 1, 2023 | [Standard](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) | Not announced |Not announced| Yes |
 | [HDInsight 5.0](./hdinsight-5x-component-versioning.md) |Ubuntu 18.0.4 LTS |March 11, 2022 | [Basic](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) | March 31, 2025 | March 31, 2025| Yes |
-| HDInsight 4.0 |Ubuntu 18.0.4 LTS |September 24, 2018 | [Basic](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) | March 31, 2025 | March 31, 2025 |Yes |
 | [HDInsight 4.0](hdinsight-40-component-versioning.md) |Ubuntu 18.0.4 LTS |September 24, 2018 | [Basic](hdinsight-component-versioning.md#support-options-for-hdinsight-versions) | March 31, 2025 | March 31, 2025 |Yes |
 
 **Support expiration** means that Microsoft no longer provides support for the specific HDInsight version. You might not be able to create clusters from the Azure portal.
diff --git a/articles/healthcare-apis/fhir/fhir-best-practices.md b/articles/healthcare-apis/fhir/fhir-best-practices.md
@@ -23,10 +23,10 @@ This document provides guidance on best practices with the Azure Health Data Ser
 
 Azure FHIR service supports data ingestion through the import operation, which offers two modes: initial mode, and incremental mode. For detailed guidance, refer to the [Importing data into the FHIR service](import-data.md) documentation.
 
-* **Consider** using the import operation over HTTP API requests to ingest the data into FHIR service. The import operation provides a high throughput and is a scalable method for loading data.
 To achieve optimal performance with the import operation, consider the following best practices.
 
 * **Do** use large files while ingesting data. The optimal DNJSON file size for import is 50 MB or larger (or 20,000 resources or more, with no upper limit). Combining smaller files into larger ones can enhance performance.
+* **Consider** using the import operation over HTTP API requests to ingest the data into FHIR service. The import operation provides a high throughput and is a scalable method for loading data.
 * **Consider** importing all FHIR resource files in a single import operation for optimal performance. Aim for a total file size of 100 GB or more (or 100 million resources, no upper limit) in one operation. Maximizing an import in this way helps reduce the overhead associated with managing multiple import jobs.
 * **Consider** running multiple concurrent imports only if necessary, but limit parallel import jobs. A single large import is designed to consume all available system resources, and processing throughput doesn't increase with concurrent import jobs.
 
@@ -73,4 +73,4 @@ For more information on export operations, see [Export your FHIR data](export-da
 
 By applying these best practices you can enhance the performance and efficiency of data ingestion, bundle processing, query execution, and data extraction in Azure FHIR service.
 
-[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
diff --git a/articles/healthcare-apis/fhir/toc.yml b/articles/healthcare-apis/fhir/toc.yml
@@ -16,7 +16,7 @@ items:
       href: migration-strategies.md
     - name: SMART on FHIR
       href: smart-on-fhir.md
-    - name: FHIR best practices
+    - name: Best practices
       href: fhir-best-practices.md
 - name: Quickstarts
   expanded: true
diff --git a/articles/iot-operations/get-started-end-to-end-sample/quickstart-upload-telemetry-to-cloud.md b/articles/iot-operations/get-started-end-to-end-sample/quickstart-upload-telemetry-to-cloud.md
@@ -135,7 +135,7 @@ kubectl apply -f dataflow.yaml
 
 ## Verify data is flowing
 
-To verify that data is flowing to the cloud, you can view your Event Hubs instance in the Azure portal.
+To verify that data is flowing to the cloud, you can view your Event Hubs instance in the Azure portal. You may need to wait for several minutes for the dataflow to start and for messages to flow to the event hub.
 
 If messages are flowing to the instance, you can see the count on incoming messages on the instance **Overview** page:
 
diff --git a/articles/load-testing/resource-supported-azure-resource-types.md b/articles/load-testing/resource-supported-azure-resource-types.md
@@ -23,6 +23,7 @@ This section lists the Azure resource types that Azure Load Testing supports for
 * Azure API Management
 * Azure App Service
 * Azure App Service plan
+* Azure Application Gateway
 * Azure Application Insights
 * Azure Application Gateway
 * Azure Batch Service
diff --git a/articles/oracle/oracle-db/provision-manage-oracle-resources.md b/articles/oracle/oracle-db/provision-manage-oracle-resources.md
@@ -37,28 +37,6 @@ The following management functions are available for all resources from the Micr
    1. Follow the steps to access the resource blade.
    1. You can remove a single or multiple resources from the blade by selecting the checkbox on the left side of the table. Once you have selected the resource(s) to remove, you can then select the **Delete** icon at the top of the blade.
    1. You can also remove a single resource by selecting the link to the resource from the **Name** field in the table. From the resource's detail page, select the **Delete** icon at the top of the blade.
-* **Move the resource to a new resource group.**
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the **Name** field in the table.
-   1. From the resource's overview page, select the **Move** link on the Resource group field.
-   1. From the **Move resources** page, use the drop-down field for **Resource group** to select an existing resource group.
-   1. To create and use a new resource group, select the **Create new** link below the Resource group field. Enter a new resource group name in the **Name** field. Select the **OK** button to save your new resource group and use it. Select the **Cancel** button to return without creating a new resource group.
-* **Move the resource to a new subscription.**
-
-   > [!NOTE]
-   > You must have access to another Microsoft Azure subscription, and that subscription must have been setup for access to OracleDB@Azure. If both of these conditions are not met, you will not be able to successfully move the resource to another subscription.
-
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the Name field in the table.
-   1. From the resource's overview page, select the **Move** link on the Subscription field.
-   1. From the **Move resources** page, use the drop-down field for **Subscription** to select an existing subscription.
-   1. You can also simultaneously move the resource group for the resource. To do this, note the steps in the **Move the resource to a new resource group** tasks. **Add, manage, or delete tags for the resource.**
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the Name field in the table.
-   1. From the resource's overview page, select the **Edit** link on the **Tags** field.
-   1. To create a new tag, enter values in the **Name** and **Value** fields.
-   1. To edit an existing tag, change the value in the existing tag's **Value** field.
-   1. To delete an existing tag, select the **Trashcan** icon at the right-side of the tag.
 
 ## Manage resource allocation for Oracle Autonomous Database Serverless instances
 
@@ -81,4 +59,4 @@ Follow the following steps to access the Oracle Autonomous Database@Azure blade.
    1. Select the link to the resource from the **Name** field in the table.
    1. From the resource's detail page, select the **Go to OCI** link on the **OCI Database URL** field.
    1. Log in to OCI.
-   1. Manage the resource from within the OCI console.
+   1. Manage the resource from within the OCI console.
diff --git a/articles/reliability/migrate-cache-redis.md b/articles/reliability/migrate-cache-redis.md
@@ -18,6 +18,9 @@ Azure Cache for Redis supports zone redundancy in its Premium, Enterprise, and E
 
 Currently, the only way to convert a resource from non-availability zone support to availability zone support is to redeploy your current cache.
 
+ > [!NOTE]
+   > Zone redundancy isn't supported with geo-replication.
+
 ## Prerequisites
 
 To migrate to availability zone support, you must have an Azure Cache for Redis resource in either the Premium, Enterprise, or Enterprise Flash tiers.
@@ -54,4 +57,4 @@ Running multiple caches simultaneously as you convert your data to the new cache
 Learn more about:
 
 > [!div class="nextstepaction"]
-> [Azure services and regions that support availability zones](availability-zones-service-support.md)
+> [Azure services and regions that support availability zones](availability-zones-service-support.md)
diff --git a/articles/route-server/troubleshoot-route-server.md b/articles/route-server/troubleshoot-route-server.md
@@ -47,6 +47,10 @@ If you advertise a route from your NVA to Route Server that is an exact prefix m
  
 If you associate a service endpoint policy to the RouteServerSubnet or GatewaySubnet, then communication may break between Azure's underlying management platform and these respective Azure services (Route Server and VPN/ExpressRoute gateway). This can cause these Azure resources to enter an unhealthy state, resulting in connectivity loss between your on-premises and Azure workloads.
 
+### Why do I lose connectivity after using custom DNS instead of the default (Azure-provided DNS) for Route Server's virtual network?
+
+For the virtual network that Route Server is deployed in, if you are not using default (Azure-provided) DNS, then make sure your custom DNS configuration is able to resolve public domain names. This ensures that Azure services (Route Server and VPN/ExpressRoute gateway) are able to communicate with Azure's underlying management plane. Please see the note about wildcard rules in the [Azure DNS Private Resolver documentation](../dns/private-resolver-endpoints-rulesets.md#rules).
+
 ### Why can't I TCP ping from my NVA to the BGP peer IP of the Route Server after I set up the BGP peering between them?
 
 In some NVAs, you need to add a static route to the Route Server subnet to be able to TCP ping the Route Server from the NVA and to avoid BGP peering flapping. For example, if the Route Server is in 10.0.255.0/27 and your NVA is in 10.0.1.0/24, you need to add the following route to the routing table in the NVA:
diff --git a/articles/sap/automation/plan-deployment.md b/articles/sap/automation/plan-deployment.md
@@ -57,7 +57,7 @@ The control plane provides the following services:
 
 The control plane is defined by using two configuration files, one for the deployer and one for the SAP Library.
 
-The deployment configuration file defines the region, environment name, and virtual network information. For example:
+The deployer configuration file defines the region, environment name, and virtual network information. For example:
 
 ```tfvars
 # Deployer Configuration File
diff --git a/articles/security/fundamentals/steps-secure-identity.md b/articles/security/fundamentals/steps-secure-identity.md
@@ -37,7 +37,7 @@ The recommendations in this document are aligned with the [Identity Secure Score
 
 ## Before you begin: Protect privileged accounts with MFA
 
-Before you begin this checklist, make sure you don't get compromised while you're reading this checklist. In Microsoft Entra we observe 50 million password attacks daily, yet only 20% of users and 30% of global admins are using strong authentications such as multifactor authentication (MFA). These statistics are based on data as of August 2021. In Microsoft Entra ID, users who have privileged roles, such as administrators, are the root of trust to build and manage the rest of the environment. Implement the following practices to minimize the effects of a compromise. 
+Before you begin this checklist, make sure you don't get compromised while you're reading this checklist. In Microsoft Entra we observe 50 million password attacks daily, yet only a fraction of users and administrators are using strong authentications such as multifactor authentication (MFA). These statistics are based on data as of August 2021. In Microsoft Entra ID, users who have privileged roles, such as administrators, are the root of trust to build and manage the rest of the environment. Implement the following practices to minimize the effects of a compromise. 
 
 Attackers who get control of privileged accounts can do tremendous damage, so it's critical to [protect these accounts before proceeding](../../active-directory/authentication/how-to-authentication-find-coverage-gaps.md). Enable and require [Microsoft Entra multifactor authentication (MFA)](../../active-directory/authentication/concept-mfa-howitworks.md) for all administrators in your organization using [Microsoft Entra Security Defaults](../../active-directory/fundamentals/concept-fundamentals-security-defaults.md) or [Conditional Access](../../active-directory/conditional-access/howto-conditional-access-policy-admin-mfa.md). It's critical.
 
diff --git a/articles/sentinel/data-transformation.md b/articles/sentinel/data-transformation.md
@@ -101,7 +101,7 @@ Only the following tables are currently supported for custom log ingestion:
 - [**CommonSecurityLog**](/azure/azure-monitor/reference/tables/commonsecuritylog)
 - [**Syslog**](/azure/azure-monitor/reference/tables/syslog)
 - [**ASimAuditEventLogs**](/azure/azure-monitor/reference/tables/asimauditeventlogs)
-- **ASimAuthenticationEventLogs**
+- [**ASimAuthenticationEventLogs**](/azure/azure-monitor/reference/tables/asimauthenticationeventlogs)
 - [**ASimDnsActivityLogs**](/azure/azure-monitor/reference/tables/asimdnsactivitylogs)
 - [**ASimFileEventLogs**](/azure/azure-monitor/reference/tables/asimfileeventlogs)
 - [**ASimNetworkSessionLogs**](/azure/azure-monitor/reference/tables/asimnetworksessionlogs)
diff --git a/articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md b/articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md
@@ -210,7 +210,7 @@ For example, if the workload characteristics of a disk put it in the P20 or P30
 
 **Boot Type**: Boot type of the virtual machine. It can be either BIOS or EFI.  Currently Azure Site Recovery supports Windows Server EFI virtual machines (Windows Server 2012, 2012 R2 and 2016) provided the number of partitions in the boot disk is less than 4 and boot sector size is 512 bytes. To protect EFI virtual machines, Azure Site Recovery mobility service version must be 9.13 or later. Only failover is supported for EFI virtual machines. Failback isn't supported.  
 
-**OS Type**: It's OS type of the virtual machine. It can be either Windows or Linux or other based on the chosen template from virtual machineware vSphere while creating the virtual machine.  
+**OS Type**: It's OS type of the virtual machine. It can be either Windows or Linux or other based on the chosen template from VMware vSphere while creating the virtual machine.  
 
 ## Incompatible virtual machines
 
@@ -282,4 +282,4 @@ Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-
 
 
 ## Next steps
-Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-estimation.md).
+Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-estimation.md).
diff --git a/articles/virtual-network-manager/concept-ip-address-management.md b/articles/virtual-network-manager/concept-ip-address-management.md
@@ -77,6 +77,7 @@ Learn more about [Azure role-based access control (Azure RBAC)](../role-based-ac
 - When virtual networks are associated with an IPAM pool, peering sync may show as out of sync, even though peering is functioning correctly.
 - When a VNet is moved to a different subscription, the references in IPAM are not updated, leading to inconsistent management status.
 - When multiple requests for the same VNet are made, it can result in duplicate allocations entries.
+- When entering an IP address space, the address space entered must be a valid address range (valid starting address and valid size), else a failure will be encountered when sending a request. Currently, the portal does not validate CIDR input prior to sending requests.
 
 ## Next steps
 
diff --git a/articles/virtual-wan/about-virtual-hub-routing-preference.md b/articles/virtual-wan/about-virtual-hub-routing-preference.md
diff --git a/includes/route-server-limits.md b/includes/route-server-limits.md
