Skip to content

Commit 019f981

Browse files
Merge pull request #303486 from MicrosoftDocs/main
Auto Publish – main to live - 2025-07-29 05:00 UTC
2 parents d7056ef + f8c8967 commit 019f981

File tree

10 files changed

+58
-175
lines changed

10 files changed

+58
-175
lines changed

articles/azure-functions/functions-bindings-mcp-trigger.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -421,6 +421,8 @@ In both cases, you must include a call to `builder.EnableMcpToolMetadata()` in y
421421
```csharp
422422
var builder = FunctionsApplication.CreateBuilder(args);
423423

424+
builder.ConfigureFunctionsWebApplication();
425+
424426
builder.EnableMcpToolMetadata();
425427

426428
// other configuration
@@ -449,6 +451,8 @@ You can define one or more tool properties in your entry point (`Program.cs`) fi
449451
```csharp
450452
var builder = FunctionsApplication.CreateBuilder(args);
451453

454+
builder.ConfigureFunctionsWebApplication();
455+
452456
builder.EnableMcpToolMetadata();
453457

454458
builder

articles/azure-functions/functions-bindings-mcp.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,9 @@ To use this preview bundle in your app, replace the existing `extensionBundle` o
6464

6565
[!INCLUDE [functions-host-json-section-intro](../../includes/functions-host-json-section-intro.md)]
6666

67+
> [!NOTE]
68+
> Until the extension is no longer in preview, the JSON schema for `host.json` isn't updated, and specific properties and behaviors might change. During the preview period, you might see warnings in your editor that say the `mcp` section isn't recognized. You can safely ignore these warnings.
69+
6770
You can use `host.json` to define MCP server information.
6871

6972
```json

articles/backup/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -744,7 +744,7 @@
744744
items:
745745
- name: Back up Hyper-V virtual machines
746746
href: back-up-hyper-v-virtual-machines-mabs.md
747-
- name: Back up Azure Stack HCI virtual machines
747+
- name: Back up Azure Local virtual machines
748748
href: back-up-azure-stack-hyperconverged-infrastructure-virtual-machines.md
749749
- name: VMware server
750750
href: backup-azure-backup-server-vmware.md

articles/communication-services/concepts/analytics/logs/voice-and-video-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Azure Communication Services calling generates **eight distinct log types**, eac
3939

4040
### **Call summary updates logs**:
4141
Fast-arriving logs with basic call metadata (IDs, timestamps, endpoints, SDK info). These log data arrive in Azure Monitor faster than the call summary logs. This log contains basic information about the call, including all the relevant IDs, time stamps, endpoints, and SDK information.
42-
- Data available within 60 minutes of the call ending.
42+
- Data generally available within 60 minutes after the call ending.
4343
- May contain multiple rows per call participant.
4444
- Contains the most recent updates for each participant.
4545
- Useful for near-real-time monitoring and analysis of call activities.
@@ -48,7 +48,7 @@ To learn more, see: [Call summary updates log schema](call-summary-updates-log-s
4848

4949
### **Call summary logs**:
5050
This log is a subset of the Call summary updates log schema. It contains basic information about the call, including all the relevant IDs, time stamps, endpoints, and SDK information. For faster log latency, use the call summary updates logs instead.
51-
- Data available within 3-5 hours of the call ending.
51+
- Data generally available within 3 to 5 hours after the call ending.
5252
- Contains a single row per call participant.
5353
- Represents a snapshot of the call state at the time of finalization.
5454
- Useful for post-call analysis and reporting.

articles/governance/service-groups/overview.md

Lines changed: 10 additions & 120 deletions
Original file line numberDiff line numberDiff line change
@@ -89,126 +89,16 @@ Access to the root has to be given from a user with "microsoft.authorization/rol
8989
There are three built-in roles definitions to support Service Groups in the preview.
9090

9191
> [!NOTE]
92-
> Custom Role Based Access Controls aren't supported within the Preview.
93-
94-
#### Service Group Administrator
95-
This role manages all aspects of Service Groups and Relationships and is the default role given to users when they create a Service Group. The role restricts the role assignment capabilities to "Service Group Administrator', "Service Group Contributor", and "Service Group Reader" to other users.
96-
97-
**ID**: '/providers/Microsoft.Authorization/roleDefinitions/4e50c84c-c78e-4e37-b47e-e60ffea0a775"
98-
99-
```json
100-
{
101-
"assignableScopes": [
102-
"/providers/Microsoft.Management/serviceGroups"
103-
],
104-
"createdBy": null,
105-
"createdOn": "2024-10-15T18:15:20.488676+00:00",
106-
"description": "Role Definition for administrator of a Service Group",
107-
"id": "/providers/Microsoft.Authorization/roleDefinitions/4e50c84c-c78e-4e37-b47e-e60ffea0a775",
108-
"name": "4e50c84c-c78e-4e37-b47e-e60ffea0a775",
109-
"permissions": [
110-
{
111-
"actions": [
112-
"*"
113-
],
114-
"condition": null,
115-
"conditionVersion": null,
116-
"dataActions": [],
117-
"notActions": [
118-
"Microsoft.Authorization/roleAssignments/write",
119-
"Microsoft.Authorization/roleAssignments/delete"
120-
],
121-
"notDataActions": []
122-
},
123-
{
124-
"actions": [
125-
"Microsoft.Authorization/roleAssignments/write",
126-
"Microsoft.Authorization/roleAssignments/delete"
127-
],
128-
"condition": "((!(ActionMatches{'Microsoft.Authorization/roleAssignments/write'})) OR (@Request[Microsoft.Authorization/roleAssignments:RoleDefinitionId] ForAnyOfAnyValues:GuidEquals{4e50c84cc78e4e37b47ee60ffea0a775,32e6a4ec60954e37b54b12aa350ba81f,de754d53652d4c75a67f1e48d8b49c97})) AND ((!(ActionMatches{'Microsoft.Authorization/roleAssignments/delete'})) OR (@Resource[Microsoft.Authorization/roleAssignments:RoleDefinitionId] ForAnyOfAnyValues:GuidEquals{4e50c84cc78e4e37b47ee60ffea0a775,32e6a4ec60954e37b54b12aa350ba81f,de754d53652d4c75a67f1e48d8b49c97}))",
129-
"conditionVersion": "2.0",
130-
"dataActions": [],
131-
"notActions": [],
132-
"notDataActions": []
133-
}
134-
],
135-
"roleName": "Service Group Administrator",
136-
"roleType": "BuiltInRole",
137-
"type": "Microsoft.Authorization/roleDefinitions",
138-
"updatedBy": null,
139-
"updatedOn": "2025-03-25T18:40:31.229386+00:00"
140-
}
141-
```
142-
#### Service Group Contributor
143-
The Service Group Contributor role given to users when they need to create or manage the lifecycle of a Service Group. This role allows for all actions except for Role Assignment capabilities.
144-
```json
145-
{
146-
"assignableScopes": [
147-
"/providers/Microsoft.Management/serviceGroups"
148-
],
149-
"createdBy": null,
150-
"createdOn": "2024-10-15T18:15:20.488676+00:00",
151-
"description": "Role Definition for contributor of a Service Group",
152-
"id": "/providers/Microsoft.Authorization/roleDefinitions/32e6a4ec-6095-4e37-b54b-12aa350ba81f",
153-
"name": "32e6a4ec-6095-4e37-b54b-12aa350ba81f",
154-
"permissions": [
155-
{
156-
"actions": [
157-
"*"
158-
],
159-
"condition": null,
160-
"conditionVersion": null,
161-
"dataActions": [],
162-
"notActions": [
163-
"Microsoft.Authorization/roleAssignments/write",
164-
"Microsoft.Authorization/roleAssignments/delete"
165-
],
166-
"notDataActions": []
167-
}
168-
],
169-
"roleName": "Service Group Contributor",
170-
"roleType": "BuiltInRole",
171-
"type": "Microsoft.Authorization/roleDefinitions",
172-
"updatedBy": null,
173-
"updatedOn": "2024-10-15T18:15:20.488676+00:00"
174-
}
175-
```
176-
177-
178-
#### Service Group Reader
179-
This built-in role is to be used to read service groups and can also be assigned to other resources to view the connected relationships.
180-
181-
```json
182-
{
183-
"assignableScopes": [
184-
"/"
185-
],
186-
"createdBy": null,
187-
"createdOn": "2024-10-15T18:15:20.487675+00:00",
188-
"description": "Role Definition for reader of a Service Group",
189-
"id": "/providers/Microsoft.Authorization/roleDefinitions/de754d53-652d-4c75-a67f-1e48d8b49c97",
190-
"name": "de754d53-652d-4c75-a67f-1e48d8b49c97",
191-
"permissions": [
192-
{
193-
"actions": [
194-
"Microsoft.Management/serviceGroups/read",
195-
"Microsoft.Authorization/*/read"
196-
],
197-
"condition": null,
198-
"conditionVersion": null,
199-
"dataActions": [],
200-
"notActions": [],
201-
"notDataActions": []
202-
}
203-
],
204-
"roleName": "Service Group Reader",
205-
"roleType": "BuiltInRole",
206-
"type": "Microsoft.Authorization/roleDefinitions",
207-
"updatedBy": null,
208-
"updatedOn": "2024-10-15T18:15:20.487675+00:00"
209-
}
210-
```
211-
92+
> Custom Role Based Access Controls aren't supported during the Preview.
93+
94+
- [Service Group Administrator](../../role-based-access-control/built-in-roles/management-and-governance.md#service-group-administrator): This built-in role manages all aspects of Service Groups and Relationships and is the *default role* given to users when they create a Service Group.
95+
96+
97+
- [Service Group Contributor](../../role-based-access-control/built-in-roles/management-and-governance.md#service-group-contributor): This built-in role should be given to users when they need to create or manage the lifecycle of a Service Group. This role allows for all actions except for Role Assignment capabilities.
98+
99+
100+
- [Service Group Reader](../../role-based-access-control/built-in-roles/management-and-governance.md#service-group-reader): This built-in role provides read-only access to service group information and can be assigned to other resources in order to view the connected relationships.
101+
212102

213103

214104
## Related content

articles/lab-services/connect-virtual-machine-mac-remote-desktop.md

Lines changed: 10 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: azure-lab-services
77
author: RoseHJM
88
ms.author: rosemalcolm
99
ms.topic: how-to
10-
ms.date: 03/04/2024
10+
ms.date: 07/08/2025
1111
#customer intent: As a student or trainee, I want to connect to an Azure Lab Services VM from my Mac over RDP in order to use the lab resources.
1212
---
1313

@@ -17,17 +17,15 @@ ms.date: 03/04/2024
1717

1818
In this article, you learn how to connect to a lab virtual machine (VM) in Azure Lab Services from a Mac by using Remote Desktop Protocol (RDP).
1919

20-
## Install Microsoft Remote Desktop on a Mac
20+
## Install Windows App on a Mac
2121

22-
To connect to the lab VM by using RDP, use the Microsoft Remote Desktop app.
22+
To connect to the lab VM by using RDP, use the Windows App app.
2323

24-
To install the Microsoft Remote Desktop app:
24+
To install the Windows App app:
2525

26-
1. Open the App Store on your Mac, and search for **Microsoft Remote Desktop**.
26+
1. Open the App Store on your Mac, and search for **Windows App**.
2727

28-
:::image type="content" source="./media/connect-virtual-machine-mac-remote-desktop\install-remote-desktop.png" alt-text="Screenshot of Microsoft Remote Desktop app in the App Store." lightbox="./media/connect-virtual-machine-mac-remote-desktop\install-remote-desktop.png" :::
29-
30-
1. Select **Install** to install the latest version of Microsoft Remote Desktop.
28+
1. Select **Install** to install the latest version of Windows App.
3129

3230
## Access the VM from your Mac using RDP
3331

@@ -43,18 +41,14 @@ Connect to the lab VM by using the remote desktop application. You can retrieve
4341

4442
:::image type="content" source="./media/connect-virtual-machine-mac-remote-desktop/student-vm-connect-options.png" alt-text="Screenshot that shows VM tile for student with the RDP and SSH connection options highlighted." lightbox="./media/connect-virtual-machine-mac-remote-desktop/student-vm-connect-options.png":::
4543

46-
1. Open the *RDP* file on your computer with **Microsoft Remote Desktop** installed. Your computer should start to connect to the VM.
47-
48-
:::image type="content" source="./media/how-to-use-classroom-lab/connect-linux-vm.png" alt-text="Screenshot of Microsoft Remote Desktop app connecting to a remote VM." lightbox="./media/how-to-use-classroom-lab/connect-linux-vm.png":::
49-
50-
1. When prompted, enter your user name and password.
44+
1. Open the *RDP* file on your computer with **Windows App** installed. Your computer should start to connect to the VM.
5145

52-
1. If you receive a certificate warning, you can select **Continue**.
53-
54-
:::image type="content" source="./media/how-to-use-classroom-lab/certificate-error.png" alt-text="Screenshot of certificate error for Microsoft Remote Desktop app." lightbox="./media/how-to-use-classroom-lab/certificate-error.png":::
46+
1. When prompted, log in.
5547

5648
1. After the connection is established, you see the desktop of your lab VM.
5749

50+
For more information about using Windows App, see [Get started with Windows App to connect to devices and apps](/windows-app/get-started-connect-devices-desktops-apps?tabs=macos-avd%2Cwindows-w365%2Cwindows-devbox%2Cmacos-rds%2Cmacos-pc&pivots=azure-virtual-desktop).
51+
5852
## Related content
5953

6054
- As a student, learn to [connect to a VM using X2Go](connect-virtual-machine-linux-x2go.md).

articles/sentinel/roles.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Alternatively, you might want to assign the ability to read tables from within a
100100

101101
|Tasks |Permissions |
102102
|---------|---------|
103-
|**Read permissions on the default workspace** | Use a [custom Microsoft Defender XDR unified RBAC role with *data (read)*](/defender-xdr/custom-permissions-details) permissions over the Microsoft Sentinel data collection. |
103+
|**Read permissions on the default workspace** | Use a [custom Microsoft Defender XDR unified RBAC role with ](/defender-xdr/custom-permissions-details)*[data (read)](/defender-xdr/custom-permissions-details)* permissions over the Microsoft Sentinel data collection. |
104104
|**Read permissions on any other workspace enabled for Microsoft Sentinel in the data lake** | Use one of the following built-in roles in Azure RBAC for permissions on that workspace: <br>- [Log Analytics Reader](/azure/role-based-access-control/built-in-roles/monitor#log-analytics-reader) <br>- [Log Analytics Contributor](/azure/role-based-access-control/built-in-roles/monitor#log-analytics-contributor) <br>- [Microsoft Sentinel Contributor](/azure/role-based-access-control/built-in-roles/security#microsoft-sentinel-contributor) <br>- [Microsoft Sentinel Reader](/azure/role-based-access-control/built-in-roles/security#microsoft-sentinel-reader) <br>- [Reader](/azure/role-based-access-control/built-in-roles/general#reader)<br>- [Contributor](/azure/role-based-access-control/built-in-roles/privileged#contributor)<br>- [Owner](/azure/role-based-access-control/built-in-roles/privileged#owner)|
105105

106106

@@ -113,7 +113,7 @@ Microsoft Entra ID roles provides broad access across all workspaces in the data
113113
|**Write to tables in the analytics tier using KQL jobs or notebooks** | Use one of the following Microsoft Entra ID roles: <br><br> - [Security operator](/entra/identity/role-based-access-control/permissions-reference#security-operator)<br>- [Security administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator) <br>- [Global administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) |
114114
|**Write to tables in the Microsoft Sentinel data lake** | Use one of the following Microsoft Entra ID roles: <br>- [Security operator](/entra/identity/role-based-access-control/permissions-reference#security-operator) <br>- [Security administrator](/entra/identity/role-based-access-control/permissions-reference#security-administrator) <br>- [Global administrator](/entra/identity/role-based-access-control/permissions-reference#global-administrator) |
115115

116-
Alternatively, you might want to assign the ability to write output to a specific workspace, including creating, updating, and deleted tables in that workspace. In such cases, use one of the following:
116+
Alternatively, you might want to assign the ability to write output to a specific workspace. This can include the ability to configure connectors to that workspace, modifying retention settings for tables in the workspace, or creating, updating, and deleting custom tables in that workspace. In such cases, use one of the following:
117117

118118
|Tasks |Permissions |
119119
|---------|---------|

0 commit comments

Comments
 (0)