Merge pull request #186733 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)

Author: huypub

articles/active-directory/develop/scenario-daemon-overview.md

@@ -34,6 +34,14 @@ Here are some examples of use cases for daemon apps:
 
 There's another common case where non-daemon applications use client credentials: even when they act on behalf of users, they need to access a web API or a resource under their own identity for technical reasons. An example is access to secrets in Azure Key Vault or Azure SQL Database for a cache.
 
+> [!NOTE]
+> You can't deploy a daemon application to a regular user's device, and a regular user can't access a daemon application. Only a limited set of IT administrators can access devices that have daemon applications running, so a bad actor can't access a client secret or token from device traffic and act on behalf of the daemon application. The daemon application scenario doesn't replace device authentication.
+>
+> Examples of non-daemon applications:
+> - A mobile application that accesses a web service on behalf of an application, but not on behalf of a user.
+> - An IoT device that accesses a web service on behalf of a device, but not on behalf of a user.
+>
+
 Applications that acquire a token for their own identities:
 
 - Are confidential client applications. These apps, given that they access resources independently of users, need to prove their identity. They're also rather sensitive apps. They need to be approved by the Azure Active Directory (Azure AD) tenant admins.

articles/azure-arc/data/privacy-data-collection-and-reporting.md

@@ -69,7 +69,7 @@ Operational data is collected for all database instances and for the Azure Arc-e
 
 The operational data stored locally requires built in administrative privileges to view it in Grafana/Kibana. 
 
-The operational data does not leave yous environment unless you chooses to export/upload (indirect connected mode) or automatically send (directly connected mode) the data to Azure Monitor/Log Analytics. The data goes into a Log Analytics workspace, which you control. 
+The operational data does not leave your environment unless you chooses to export/upload (indirect connected mode) or automatically send (directly connected mode) the data to Azure Monitor/Log Analytics. The data goes into a Log Analytics workspace, which you control. 
 
 If the data is sent to Azure Monitor or Log Analytics, you can choose which Azure region or datacenter the Log Analytics workspace resides in. After that, access to view or copy it from other locations can be controlled by you. 
 

articles/azure-resource-manager/templates/copy-resources.md

@@ -56,7 +56,7 @@ The following example creates the number of storage accounts specified in the `s
   "parameters": {
     "storageCount": {
       "type": "int",
-      "defaultValue": 2
+      "defaultValue": 3
     }
   },
   "resources": [

articles/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm.md

@@ -111,7 +111,7 @@ Provide the SQL Server license type as either pay-as-you-go (`PAYG`) to pay per
 Register a SQL Server VM in full mode with the Azure CLI:
 
 ```azurecli-interactive
-# Register Enterprise or Standard self-installed VM in Lightweight mode
+# Register Enterprise or Standard self-installed VM in full mode
 az sql vm create --name <vm_name> --resource-group <resource_group_name> --location <vm_location> --license-type <license_type> --sql-mgmt-type Full
 ```
 

articles/container-apps/compare-options.md

@@ -1,6 +1,6 @@
 ---
 title: 'Comparing Container Apps with other Azure container options'
-description: Understand when to use Azure Container Apps and how it compares to d container options including Azure Container Instances, Azure App Service, Azure Functions, and Azure Kubernetes Service.
+description: Understand when to use Azure Container Apps and how it compares to other container options including Azure Container Instances, Azure App Service, Azure Functions, and Azure Kubernetes Service.
 services: container-apps
 author: jeffhollan
 ms.service: container-apps

articles/data-factory/connector-http.md

@@ -139,7 +139,11 @@ If you use **certThumbprint** for authentication and the certificate is installe
 1. Open the Microsoft Management Console (MMC). Add the **Certificates** snap-in that targets **Local Computer**.
 2. Expand **Certificates** > **Personal**, and then select **Certificates**.
 3. Right-click the certificate from the personal store, and then select **All Tasks** > **Manage Private Keys**.
-3. On the **Security** tab, add the user account under which the Integration Runtime Host Service (DIAHostService) is running, with read access to the certificate.
+4. On the **Security** tab, add the user account under which the Integration Runtime Host Service (DIAHostService) is running, with read access to the certificate.
+5. The HTTP connector loads only trusted certificates. If you're using a self-signed or nonintegrated CA-issued certificate, to enable trust, the certificate must also be installed in one of the following stores:
+   - Trusted People
+   - Third-Party Root Certification Authorities
+   - Trusted Root Certification Authorities
 
 **Example 1: Using certThumbprint**
 

articles/marketplace/dynamics-365-business-central-supplemental-content.md

@@ -17,6 +17,9 @@ This page lets you provide additional information to help us validate your offer
 
 Indicate which release of Microsoft Dynamics 365 Business Central your solution targets: **Current**, **Next Major**, or **Next Minor**. This information lets us test your solution appropriately.
 
+> [!NOTE]
+> The target release isn't used anymore during the validation of Business Central solutions and this field is being removed from Partner Center soon. For more information about the release computation during the validation, see [Technical Validation Checklist](/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission).
+
 ## Supported editions
 
 If your offer requires the Premium edition of Microsoft Dynamics 365 Business Central, select **Premium** only. Otherwise, select both **Essentials** and **Premium**.
@@ -25,6 +28,9 @@ If your offer requires the Premium edition of Microsoft Dynamics 365 Business Ce
 
 Upload a PDF file that lists your offer's key usage scenarios. All scenarios listed here may be verified by our validation team before we approve your offer for the marketplace.
 
+> [!NOTE]
+> The key usage scenario PDF isn't used anymore during the validation of Business Central solutions and we are working on removing this field from Partner Center. For more information, see [Technical Validation FAQ](/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission-faq).
+
 ## Test accounts
 
 If a test account is needed in order for our certification team to properly review your offer, upload a .pdf, .doc, or .docx file with your **Test accounts** information.
@@ -35,6 +41,9 @@ If your offer is an Add-on app, you must upload an **App tests automation** file
 
 Select **Save draft**, then continue with review and publish in **Next steps** below.
 
+> [!NOTE]
+> The test app isn't used anymore during the validation of Business Central solutions and we are currently working on removing this field from Partner Center. For more information, see [Technical Validation FAQ](/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission-faq).
+
 ## Next steps
 
 - [Review and publish](dynamics-365-review-publish.md)

articles/virtual-machines/boot-diagnostics.md

@@ -34,7 +34,7 @@ Located in the virtual machine blade, the boot diagnostics option is under the *
 :::image type="content" source="./media/boot-diagnostics/boot-diagnostics-windows.png" alt-text="Screenshot of Windows boot diagnostics":::
 
 ## Enable managed boot diagnostics 
-Managed boot diagnostics can be enabled through the Azure portal, CLI and ARM Templates. Enabling through PowerShell is not yet supported. 
+Managed boot diagnostics can be enabled through the Azure portal, CLI and ARM Templates.
 
 ### Enable managed boot diagnostics using the Azure portal
 When creating a VM in the Azure portal, the default setting is to have boot diagnostics enabled using a managed storage account. To view this, navigate to the *Management* tab during the VM creation.