Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-remove-last-owner-role-assignment

Author: rolyon

articles/application-gateway/http-response-codes.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: troubleshooting
-ms.date: 03/28/2025
+ms.date: 05/26/2025
 ms.author: mbender
 ---
 
@@ -97,10 +97,7 @@ Other reasons for clients receiving 403 responses include:
 
 #### 404 – Page not found
 
-An HTTP 404 response can be returned if a request is sent to an application gateway that is:
-- Using a [v2 sku](overview-v2.md).
-- Without a hostname match defined in any [multi-site listeners](multiple-site-overview.md).
-- Not configured with a [basic listener](application-gateway-components.md#types-of-listeners).
+An HTTP 404 response is generated when a request is made to Application Gateway (V2 SKUs) with a hostname that doesn’t corresponds to any of the configured Multi-site listeners, and there is no Basic listener present. Learn more about [types of listeners](application-gateway-components.md#types-of-listeners.
 
 #### 408 – Request Time-out
 

articles/automation/shared-resources/modules.md

@@ -3,7 +3,7 @@ title: Manage modules in Azure Automation
 description: This article tells how to use PowerShell modules to enable cmdlets in runbooks and DSC resources in DSC configurations.
 services: automation
 ms.subservice: shared-capabilities
-ms.date: 10/01/2024
+ms.date: 05/27/2025
 ms.topic: how-to 
 ms.custom: devx-track-azurepowershell, devx-track-python
 ms.service: azure-automation

articles/azure-health-insights/radiology-insights/model-configuration.md

@@ -28,6 +28,16 @@ To interact with the Radiology Insights model, you can provide several model con
       },
       "findingOptions": {
         "provideFocusedSentenceEvidence": false
+      },
+      "GuidanceOptions": {
+        "showGuidanceInHistory": true      
+      },
+      "QualityMeasureOptions": {
+        "measureTypes": [
+          "mips364",
+          "mips360",
+          "mips436"
+        ]
       }
     },
     "locale": "en-US",
@@ -52,6 +62,8 @@ false  | No Evidence is returned
 - type: boolean
 - Provide a single focused sentence as evidence for the finding, default is true.
 
+See [finding inference](finding-inference.md) 
+
 **FollowupRecommendationOptions**
 - includeRecommendationsWithNoSpecifiedModality
     - type: boolean
@@ -66,6 +78,22 @@ false  | No Evidence is returned
     - type: boolean
     - description: Provide a single focused sentence as evidence for the recommendation, default is true.
 
+See [recommendation inference](recommendation-inference.md)
+
+**GuidanceOptions**
+- showGuidanceInHistory:
+    - type: boolean
+    - description: If this is true, also show guidance from a clinical history section, i.e. if the first token of the associated finding's clinical indicator is in this section. Default is false.
+
+See [guidance inference](guidance-inference.md)
+
+**QualityMeasureOptions**
+- measureTypes:
+  - type: array of strings
+  - description: the quality measure kinds that a result will be made for.
+The possible values of this array are:  "mips76", "mips147", "mips195", "mips360", "mips364", "mips405", "mips406", "mips436", "mips145", "acrad36", "acrad37", "acrad38", "acrad39", "acrad40", "acrad41", "acrad42", "mednax55", "msn13", "msn15", "qmm26", "qmm17", "qmm18", "qmm19". (These values can also be found in the open api specification under "QualityMeasureType".)
+
+See [quality measure inference](quality-measure-inference.md)
 
 IncludeEvidence
 
@@ -78,56 +106,57 @@ IncludeEvidence
 ## Examples 
 
 
-**Example 1** 
+**Example 1 (with recommendation inferences)** 
 
 followupRecommendationOptions:
 - includeRecommendationsWithNoSpecifiedModality is true
-- includeRecommendationsInReferences are false
+- includeRecommendationsInReferences is false
 - provideFocusedSentenceEvidence for recommendations is false
 
+The options for quality measures and guidance aren't set, because findings and quality measures aren't in the inference types for this document.
+
 
 
 As a result:
 
 The model checks for follow-up recommendations with a specified modality (such as DIAGNOSTIC ULTRASONOGRAPHY)
 and for recommendations with no specific radiologic modality (such as RADIOGRAPHIC IMAGING PROCEDURE).
-The model does not check for a recommendation in a guideline.
-The model does not provide a single focused sentence as evidence for the recommendation.
+The model doesn't check for a recommendation in a guideline.
+The model doesn't provide a single focused sentence as evidence for the recommendations.
 
 
 - includeEvidence is true. (The model includes evidence for all inferences.)
 
 
 Examples request/response json:
 
-[!INCLUDE [Example input json](../includes/example-2-inference-follow-up-recommendation-json-request.md)]
+[!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
 
-[!INCLUDE [Example output json](../includes/example-2-inference-follow-up-recommendation-json-response.md)]
+[!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
 
 
 
 
-**Example 2**
+**Example 2 (with recommendation inferences)**
 
 followupRecommendationOptions:
 - includeRecommendationsWithNoSpecifiedModality is false
-- includeRecommendationsInReferences are true
-- provideFocusedSentenceEvidence for findings is true
-- includeEvidence is true 
+- includeRecommendationsInReferences is true
+- provideFocusedSentenceEvidence for recommendations is true
+
+The options for quality measures and guidance aren't set, because findings and quality measures aren't in the inference types for this document.
 
 As a result:
-The model checks for follow-up recommendations with a specified modality, not for and for recommendations with a nonspecific radiologic modality.
+The model checks for follow-up recommendations with a specified modality, not for recommendations with a nonspecific radiologic modality.
 The model checks for a recommendation in a guideline.
 The model provides a single focused sentence as evidence for the recommendation. 
 
 
 Examples request/response json:
 
-[!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
-
-[!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
-
+[!INCLUDE [Example input json](../includes/example-2-inference-follow-up-recommendation-json-request.md)]
 
+[!INCLUDE [Example output json](../includes/example-2-inference-follow-up-recommendation-json-response.md)]
 
 
 ## Next steps

articles/azure-health-insights/radiology-insights/transparency-note.md

@@ -9,7 +9,7 @@ ms.date: 04/04/2025
 ms.author: janschietse
 ---
 
-# Transparency Note for Radiology Insights (Preview)
+# Transparency Note for Radiology Insights
 
 ## What is a Transparency Note?
 

articles/azure-signalr/signalr-howto-work-with-azure-front-door.md

@@ -93,7 +93,7 @@ Paste in the content to the `afd-demo.csproj` file. This project uses only the "
 ```
 
 #### Configure app settings
-Create an `appsettings.json` file and paste in the content. The values will be referenced in the `Program.cs` file, which we create in the next step.
+Create an `appsettings.json` file and paste in the content. The values will be referenced in the `Program.cs` file, which we create in the next step. Add a `ClientEndpoint` section in the ConnectionString.
 ```bash
 touch appsettings.json
 ```
@@ -104,10 +104,7 @@ touch appsettings.json
 {
   "Azure": {
     "SignalR": {
-      "ConnectionString": "<the-connection-string-of-your-Azure-SignalR-resource>"
-    },
-    "AFD": {
-      "Endpoint": "<the-endpoint-of-your-Azure-Front-Door-resource>"
+      "ConnectionString": "<the-connection-string-of-your-Azure-SignalR-resource>;ClientEndpoint=<the-endpoint-of-your-Azure-Front-Door-resource>"
     }
   }
 }
@@ -123,21 +120,8 @@ Paste in the code to the `Program.cs` file. The web app defines a SignalR hub an
 using Microsoft.Azure.SignalR;
 var builder = WebApplication.CreateBuilder(args);
 
-// Reads in the configuration from `appsettings.json`
-var azureSignalRConnectionString = builder.Configuration["Azure:SignalR:ConnectionString"];
-var afdEndpoint = builder.Configuration["Azure:AFD:Endpoint"];
-
-builder.Services.AddSignalR().AddAzureSignalR(o =>
-{
-    o.Endpoints = new Microsoft.Azure.SignalR.ServiceEndpoint[1]
-    {
-        new Microsoft.Azure.SignalR.ServiceEndpoint(azureSignalRConnectionString)
-        {   
-            // Instructs SignalR server to return a `ClientEndpoint` to SignalR clients, with which they establish a connection. In our case, it's the endpoint of the Azure Front Door resource you just created.
-            ClientEndpoint = new Uri(afdEndpoint),
-        }
-    };
-});
+// Automatically read in the configuration from `appsettings.json`
+builder.Services.AddSignalR().AddAzureSignalR();
 
 var app = builder.Build();
 app.UseStaticFiles();

articles/backup/azure-data-lake-storage-backup-troubleshoot.md

@@ -0,0 +1,72 @@
+---
+title: Troubleshooting Azure Data Lake Storage backup using Azure Backup (preview)
+description: Learn to troubleshoot Azure Data Lake Storage backup using Azure Backup.
+ms.topic: troubleshooting
+ms.date: 05/27/2025
+ms.service: azure-backup
+author: jyothisuri
+ms.author: jsuri
+---
+
+# Troubleshoot Azure Data Lake Storage backup (preview)
+
+This article provides troubleshooting details for error codes that appear when configuring backup and restoring for Azure Data Lake Storage data using Azure Backup (preview).
+
+## Common backup errors
+
+### UserErrorMissingRequiredPermissions
+
+**Error code**: `UserErrorMissingRequiredPermissions`
+
+**Error message**: Appropriate permissions to perform the operation are missing.
+
+**Recommended action**: Ensure that you [granted appropriate permissions](azure-data-lake-storage-configure-backup.md#grant-permissions-to-the-backup-vault-on-storage-accounts).
+
+### UserErrorBackupRequestThrottled
+
+**Error code**: `UserErrorBackupRequestThrottled`
+
+**Error message**: The backup request is throttled as the number of backups on a given backup instance in a day reached the maximum limit.
+
+**Recommended action**: Wait for a day before triggering a new backup operation.
+
+### UserErrorIncorrectContainersSelectedForOperation
+
+**Error code**: `UserErrorIncorrectContainersSelectedForOperation`
+
+**Error message**: Incorrect containers are selected for the backup operation.
+
+**Cause**: One or more containers included in the scope of protection no longer exist in the protected storage account.
+
+**Recommended action**: Retrigger the operation after modifying the protected container list using the **edit backup instance** option.
+
+### UserErrorUnsupportedStorageAccountType
+
+**Error code**: `UserErrorUnsupportedStorageAccountType`
+
+**Error message**: The storage account type isn't supported for Backup.
+
+**Recommended action**: Ensure that you select only the hierarchical namespace (HNS) enabled storage accounts for backup. Network File System (NFS) or Secure File Transfer Protocol (SFTP) enabled storage accounts aren't supported for Azure Data Lake Storage.  
+
+## Common restore errors
+
+### UserErrorTargetContainersExistOnAccount
+
+**Error code**: `UserErrorTargetContainersExistOnAccount`
+	
+**Error message**: The containers that are part of restore request shouldn't exist on target storage account.
+
+**Recommended action**: Ensure that the target storage account doesn't have containers with the same name you're trying to restore. Choose another storage target or retry the restore operation after removing containers with the same name.
+
+### UserErrorOriginalLocationRestoreNotSupported
+
+**Error code**: `UserErrorOriginalLocationRestoreNotSupported`
+
+**Error message**: Original location restores aren't supported for vaulted blob backup.
+
+**Recommended action**: Choose an alternate target storage account and trigger the restore operation.
+
+## Related content
+
+- [Configure vaulted backup for Azure Data Lake Storage using Azure portal (preview)](azure-data-lake-storage-configure-backup.md).
+- [Restore Azure Data Lake Storage using Azure portal (preview)](azure-data-lake-storage-restore.md).