Skip to content

Commit 180fdfb

Browse files
authored
Merge pull request #300356 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 5/26
2 parents 164df1e + f417560 commit 180fdfb

18 files changed

+94
-314
lines changed

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

Lines changed: 44 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,16 @@ To interact with the Radiology Insights model, you can provide several model con
2828
},
2929
"findingOptions": {
3030
"provideFocusedSentenceEvidence": false
31+
},
32+
"GuidanceOptions": {
33+
"showGuidanceInHistory": true
34+
},
35+
"QualityMeasureOptions": {
36+
"measureTypes": [
37+
"mips364",
38+
"mips360",
39+
"mips436"
40+
]
3141
}
3242
},
3343
"locale": "en-US",
@@ -52,6 +62,8 @@ false | No Evidence is returned
5262
- type: boolean
5363
- Provide a single focused sentence as evidence for the finding, default is true.
5464

65+
See [finding inference](finding-inference.md)
66+
5567
**FollowupRecommendationOptions**
5668
- includeRecommendationsWithNoSpecifiedModality
5769
- type: boolean
@@ -66,6 +78,22 @@ false | No Evidence is returned
6678
- type: boolean
6779
- description: Provide a single focused sentence as evidence for the recommendation, default is true.
6880

81+
See [recommendation inference](recommendation-inference.md)
82+
83+
**GuidanceOptions**
84+
- showGuidanceInHistory:
85+
- type: boolean
86+
- 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.
87+
88+
See [guidance inference](guidance-inference.md)
89+
90+
**QualityMeasureOptions**
91+
- measureTypes:
92+
- type: array of strings
93+
- description: the quality measure kinds that a result will be made for.
94+
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".)
95+
96+
See [quality measure inference](quality-measure-inference.md)
6997

7098
IncludeEvidence
7199

@@ -78,56 +106,57 @@ IncludeEvidence
78106
## Examples
79107

80108

81-
**Example 1**
109+
**Example 1 (with recommendation inferences)**
82110

83111
followupRecommendationOptions:
84112
- includeRecommendationsWithNoSpecifiedModality is true
85-
- includeRecommendationsInReferences are false
113+
- includeRecommendationsInReferences is false
86114
- provideFocusedSentenceEvidence for recommendations is false
87115

116+
The options for quality measures and guidance aren't set, because findings and quality measures aren't in the inference types for this document.
117+
88118

89119

90120
As a result:
91121

92122
The model checks for follow-up recommendations with a specified modality (such as DIAGNOSTIC ULTRASONOGRAPHY)
93123
and for recommendations with no specific radiologic modality (such as RADIOGRAPHIC IMAGING PROCEDURE).
94-
The model does not check for a recommendation in a guideline.
95-
The model does not provide a single focused sentence as evidence for the recommendation.
124+
The model doesn't check for a recommendation in a guideline.
125+
The model doesn't provide a single focused sentence as evidence for the recommendations.
96126

97127

98128
- includeEvidence is true. (The model includes evidence for all inferences.)
99129

100130

101131
Examples request/response json:
102132

103-
[!INCLUDE [Example input json](../includes/example-2-inference-follow-up-recommendation-json-request.md)]
133+
[!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
104134

105-
[!INCLUDE [Example output json](../includes/example-2-inference-follow-up-recommendation-json-response.md)]
135+
[!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
106136

107137

108138

109139

110-
**Example 2**
140+
**Example 2 (with recommendation inferences)**
111141

112142
followupRecommendationOptions:
113143
- includeRecommendationsWithNoSpecifiedModality is false
114-
- includeRecommendationsInReferences are true
115-
- provideFocusedSentenceEvidence for findings is true
116-
- includeEvidence is true
144+
- includeRecommendationsInReferences is true
145+
- provideFocusedSentenceEvidence for recommendations is true
146+
147+
The options for quality measures and guidance aren't set, because findings and quality measures aren't in the inference types for this document.
117148

118149
As a result:
119-
The model checks for follow-up recommendations with a specified modality, not for and for recommendations with a nonspecific radiologic modality.
150+
The model checks for follow-up recommendations with a specified modality, not for recommendations with a nonspecific radiologic modality.
120151
The model checks for a recommendation in a guideline.
121152
The model provides a single focused sentence as evidence for the recommendation.
122153

123154

124155
Examples request/response json:
125156

126-
[!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
127-
128-
[!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
129-
157+
[!INCLUDE [Example input json](../includes/example-2-inference-follow-up-recommendation-json-request.md)]
130158

159+
[!INCLUDE [Example output json](../includes/example-2-inference-follow-up-recommendation-json-response.md)]
131160

132161

133162
## Next steps

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.date: 04/04/2025
99
ms.author: janschietse
1010
---
1111

12-
# Transparency Note for Radiology Insights (Preview)
12+
# Transparency Note for Radiology Insights
1313

1414
## What is a Transparency Note?
1515

articles/backup/backup-rbac-rs-vault.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Manage Backups with Azure role-based access control
33
description: Use Azure role-based access control to manage access to backup management operations in Recovery Services vault.
4-
ms.reviewer: utraghuv
4+
ms.reviewer: dapatil
55
ms.topic: how-to
6-
ms.date: 05/08/2025
6+
ms.date: 05/26/2025
77
ms.service: azure-backup
88
author: jyothisuri
99
ms.author: jsuri
@@ -124,16 +124,19 @@ The following table captures the Backup management actions and corresponding Azu
124124

125125
| Management Operation | Minimum Azure role required | Scope Required | Alternative |
126126
| --- | --- | --- | --- |
127-
| Validate before configuring backup | Backup Operator | Backup vault | |
127+
| Validate before configuring backup | Backup Operator | Backup vault <br><br> - Resources/deployments/validate/action <br> - Resources/deployments/write <br> - Resources/subscriptions/resourceGroups/read | |
128128
| | Storage account backup contributor | Storage account containing the blob | |
129-
| Enable backup from backup vault | Backup Operator | Backup vault | |
129+
| Enable backup from backup vault | Backup Operator | Backup vault <br><br> - Resources/deployments/validate/action <br> - Resources/deployments/write <br> - Resources/subscriptions/resourceGroups/read | |
130130
| | Storage account backup contributor | Storage account containing the blob | In addition, the backup vault MSI should be given [these permissions](./blob-backup-configure-manage.md#grant-permissions-to-the-backup-vault-on-storage-accounts) |
131-
| On demand backup of blob | Backup Operator | Backup vault | |
132-
| Validate before restoring a blob | Backup Operator | Backup vault | |
131+
| On demand backup of blob | Backup Operator | Backup vault <br><br> - Resources/deployments/validate/action <br> - Resources/deployments/write <br> - Resources/subscriptions/resourceGroups/read | |
132+
| Validate before restoring a blob | Backup Operator | Backup vault <br><br> - Resources/deployments/validate/action <br> - Resources/deployments/write <br> - Resources/subscriptions/resourceGroups/read | |
133133
| | Storage account backup contributor | Storage account containing the blob | |
134134
| Restoring a blob | Backup Operator | Backup vault | |
135135
| | Storage account backup contributor | Storage account containing the blob | In addition, the backup vault MSI should be given [these permissions](./blob-backup-configure-manage.md#grant-permissions-to-the-backup-vault-on-storage-accounts) |
136136

137+
>[!Note]
138+
>For Storage account validation operation, the Backup vault Managed ID must have the **Owner** privileges.
139+
137140
### Minimum role requirements for Azure database for PostgreSQL server backup
138141

139142
| Management Operation | Minimum Azure role required | Scope Required | Alternative |

articles/sap/workloads/integration-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -222,7 +222,7 @@ Use [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-
222222

223223
Complimenting that, use the [SAP certified](https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/solutions?id=s:33db1376-91ae-4f36-a435-aafa892a88d8) solution [Microsoft Sentinel for SAP](../../sentinel/sap/sap-solution-security-content.md) to protect your SAP system and [SAP Business Technology Platform (BTP)](../../sentinel/sap/sap-btp-solution-overview.md) instance from within using signals from the SAP Audit Log among others.
224224

225-
Unify all your security solutions for Microsoft 365, cloud-infrastructure, and SAP in a unified portal experience with [Microsoft Unified Security Operations Platform](/unified-secops-platform/overview-unified-security). Profit from the correlation of signals across the Microsoft ecosystem and connected third parties to detect and respond to threats in real-time.
225+
Unify all your security solutions for Microsoft 365, cloud-infrastructure, and SAP in a [single experience](/unified-secops-platform/overview-unified-security) in the Defender portal. Profit from the correlation of signals across the Microsoft ecosystem and connected third parties to detect and respond to threats in real-time.
226226

227227
Learn more about identity focused integration capabilities that power the analysis on Defender and Microsoft Sentinel via the [Microsoft Entra ID section](#microsoft-entra-id-formerly-azure-ad).
228228

@@ -234,7 +234,7 @@ Discover partner offerings for SAP security on the [Azure Marketplace](https://a
234234

235235
#### Microsoft Sentinel for SAP
236236

237-
Microsoft Sentinel integrates natively with Microsoft Unified Security Operations Platform. See the integration in action with [Automatic attack disruption for SAP](../../sentinel/sap/deployment-attack-disrupt.md).
237+
Microsoft Sentinel integrates natively with Microsoft Defender XDR in the Defender portal. See the integration in action with [Automatic attack disruption for SAP](../../sentinel/sap/deployment-attack-disrupt.md).
238238

239239
For more information about [SAP certified](https://www.sap.com/dmc/exp/2013_09_adpd/enEN/#/solutions?id=s:33db1376-91ae-4f36-a435-aafa892a88d8) threat monitoring with Microsoft Sentinel for SAP, see the following Microsoft resources:
240240

articles/sentinel/connect-microsoft-365-defender.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to ingest incidents, alerts, and raw event data from Micr
44
author: yelevin
55
ms.author: yelevin
66
ms.topic: how-to
7-
ms.date: 11/26/2024
7+
ms.date: 05/22/2025
88
appliesto:
99
- Microsoft Sentinel with Defender XDR in the Microsoft Defender portal
1010
- Microsoft Sentinel in the Azure portal
@@ -19,7 +19,7 @@ ms.collection: usx-security
1919

2020
The Microsoft Defender XDR connector for Microsoft Sentinel allows you to stream all Microsoft Defender XDR incidents, alerts, and advanced hunting events into Microsoft Sentinel. This connector keeps the incidents synchronized between both portals. Microsoft Defender XDR incidents include alerts, entities, and other relevant information from all the Microsoft Defender products and services. For more information, see [Microsoft Defender XDR integration with Microsoft Sentinel](microsoft-365-defender-sentinel-integration.md).
2121

22-
The Defender XDR connector, especially its incident integration feature, is the foundation of Microsoft's unified security operations platform.
22+
The Defender XDR connector, especially its incident integration feature, is the foundation of unified security operations in the Microsoft Defender portal. The Defender XDR data connector is automatically connected when you onboard Microsoft Sentinel to the Defender portal.
2323

2424
[!INCLUDE [unified-soc-preview](includes/unified-soc-preview.md)]
2525

@@ -198,4 +198,4 @@ See more information on the following items used in the preceding examples, in t
198198

199199
In this document, you learned how to integrate Microsoft Defender XDR incidents, alerts, and advanced hunting event data from Microsoft Defender services, into Microsoft Sentinel, by using the Microsoft Defender XDR connector.
200200

201-
To use Microsoft Sentinel integrated with Defender XDR in Microsoft's unified security operations platform, see [Connect Microsoft Sentinel to the Microsoft Defender portal](/defender-xdr/microsoft-sentinel-onboard).
201+
To use Microsoft Sentinel together with Defender XDR in the Defender portal, see [Connect Microsoft Sentinel to the Microsoft Defender portal](/unified-secops-platform/microsoft-sentinel-onboard?toc=%2Fazure%2Fsentinel%2FTOC.json&bc=%2Fazure%2Fsentinel%2Fbreadcrumb%2Ftoc.json)

articles/sentinel/data-type-cloud-support.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,4 +56,4 @@ In this article, you learned about the types of clouds that affect the supported
5656

5757
- To get started with Microsoft Sentinel, you need a subscription to Microsoft Azure. If you don't have a subscription, you can sign up for a [free trial](https://azure.microsoft.com/free/).
5858
- Learn how to [onboard your data to Microsoft Sentinel](quickstart-onboard.md) and [get visibility into your data and potential threats](get-visibility.md).
59-
- Microsoft Sentinel is available as part of the unified security operations platform in the Microsoft Defender portal. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](microsoft-sentinel-defender-portal.md) and [Connect Microsoft Sentinel to Microsoft Defender XDR](/microsoft-365/security/defender/microsoft-sentinel-onboard).
59+
- Microsoft Sentinel is also available for unified security operations in the Microsoft Defender portal. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](microsoft-sentinel-defender-portal.md) and [Connect Microsoft Sentinel to Microsoft Defender XDR](/microsoft-365/security/defender/microsoft-sentinel-onboard).

articles/sentinel/includes/unified-soc-preview-without-alert.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ ms.author: bagol
99
ms.custom: "include file"
1010
---
1111

12-
Microsoft Sentinel is generally available within Microsoft's unified security operations platform in the Microsoft Defender portal, including for customers without Microsoft Defender XDR or an E5 license. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](../microsoft-sentinel-defender-portal.md).
12+
Microsoft Sentinel is generally available in the Microsoft Defender portal, including for customers without Microsoft Defender XDR or an E5 license. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](../microsoft-sentinel-defender-portal.md).

articles/sentinel/includes/unified-soc-preview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ ms.custom: "include file"
1010
---
1111

1212
> [!IMPORTANT]
13-
> Microsoft Sentinel is generally available within Microsoft's unified security operations platform in the Microsoft Defender portal, including for customers without Microsoft Defender XDR or an E5 license. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](../microsoft-sentinel-defender-portal.md).
13+
> Microsoft Sentinel is generally available in the Microsoft Defender portal, including for customers without Microsoft Defender XDR or an E5 license. For more information, see [Microsoft Sentinel in the Microsoft Defender portal](../microsoft-sentinel-defender-portal.md).

articles/sentinel/index.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,21 +54,21 @@ landingContent:
5454
url: sentinel-solutions-deploy.md
5555

5656
# Card
57-
- title: Microsoft's unified security operations platform
57+
- title: Unified security operations
5858
linkLists:
5959
- linkListType: overview
6060
links:
61-
- text: "What is Microsoft's unified SecOps platform?"
61+
- text: "What are unified security operations?"
6262
url: /unified-secops-platform/overview-unified-security
6363
- text: "Microsoft Defender portal overview"
6464
url: /unified-secops-platform/overview-defender-portal
6565
- text: "Microsoft Sentinel in the Microsoft Defender portal"
6666
url: microsoft-sentinel-defender-portal.md
6767
- linkListType: deploy
6868
links:
69-
- text: "Plan your unified SecOps deployment"
69+
- text: "Plan for unified security operations"
7070
url: /unified-secops-platform/overview-plan
71-
- text: "Deploy Microsoft's unified SecOps platform"
71+
- text: "Deploy unified security operations"
7272
url: /unified-secops-platform/overview-deploy
7373
- linkListType: how-to-guide
7474
links:

articles/sentinel/microsoft-365-defender-sentinel-integration.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ ms.collection: usx-security
1919

2020
Integrate Microsoft Defender XDR with Microsoft Sentinel to stream all Defender XDR incidents and advanced hunting events into Microsoft Sentinel and keep the incidents and events synchronized between the Azure and Microsoft Defender portals. Incidents from Defender XDR include all associated alerts, entities, and relevant information, providing you with enough context to perform triage and preliminary investigation in Microsoft Sentinel. Once in Microsoft Sentinel, incidents remain bi-directionally synced with Defender XDR, allowing you to take advantage of the benefits of both portals in your incident investigation.
2121

22-
Alternatively, onboard Microsoft Sentinel with Defender XDR to Microsoft's unified security operations (SecOps) platform in the Defender portal. Microsoft's unified SecOps platform brings together the full capabilities of Microsoft Sentinel, Defender XDR, and generative AI built specifically for cybersecurity. For more information, see the following resources:
22+
Alternatively, onboard Microsoft Sentinel to the Defender portal to use it together with Defender XDR for unified security operations. For more information, see the following resources:
2323

24-
- [What is Microsoft's unified security operations platform?](/unified-secops-platform/overview-unified-security)
24+
- [What are unified security operations?](/unified-secops-platform/overview-unified-security)
2525
- [Microsoft Sentinel in the Microsoft Defender portal](microsoft-sentinel-defender-portal.md)
2626

2727
## Microsoft Sentinel and Defender XDR
@@ -30,7 +30,7 @@ Use one of the following methods to integrate Microsoft Sentinel with Microsoft
3030

3131
- Ingest Microsoft Defender XDR service data into Microsoft Sentinel and view Microsoft Sentinel data in the Azure portal. Enable the Defender XDR connector in Microsoft Sentinel.
3232

33-
- Integrate Microsoft Sentinel and Defender XDR into a single, unified security operations platform in the Microsoft Defender portal. In this case, view Microsoft Sentinel data directly in the Microsoft Defender portal with the rest of your Defender incidents, alerts, vulnerabilities, and other security data. Enable the Defender XDR connector in Microsoft Sentinel and onboard Microsoft Sentinel to the Defender portal.
33+
- Integrate Microsoft Sentinel and Defender XDR directly in the Microsoft Defender portal. In this case, view Microsoft Sentinel data directly with the rest of your Defender incidents, alerts, vulnerabilities, and other security data. To do this, you must onboard Microsoft Sentinel to the Defender portal.
3434

3535
Select the appropriate tab to see what the Microsoft Sentinel integration with Defender XDR looks like depending on which integration method you use.
3636

@@ -88,7 +88,7 @@ In addition to collecting alerts from these components and other services, Defen
8888

8989
Consider integrating Defender XDR with Microsoft Sentinel for the following use cases and scenarios:
9090

91-
- Onboard Microsoft Sentinel to Microsoft's unified SecOps platform in the Microsoft Defender portal. Enabling the Defender XDR connector is a prerequisite.
91+
- Onboard Microsoft Sentinel to the Microsoft Defender portal.
9292

9393
- Enable one-click connect of Defender XDR incidents, including all alerts and entities from Defender XDR components, into Microsoft Sentinel.
9494

@@ -98,7 +98,7 @@ Consider integrating Defender XDR with Microsoft Sentinel for the following use
9898

9999
- Facilitate investigations across both portals with in-context deep links between a Microsoft Sentinel incident and its parallel Defender XDR incident.
100100

101-
For more information about the capabilities of the Microsoft Sentinel integration with Defender XDR in Microsoft's unified SecOps platform, see [Microsoft Sentinel in the Microsoft Defender portal](microsoft-sentinel-defender-portal.md).
101+
For more information, see [Microsoft Sentinel in the Microsoft Defender portal](microsoft-sentinel-defender-portal.md).
102102

103103
## Connecting to Microsoft Defender XDR <a name="microsoft-defender-xdr-incidents-and-microsoft-incident-creation-rules"></a>
104104

0 commit comments

Comments
 (0)