Skip to content

Commit 852a86b

Browse files
learn-build-service-prod[bot]learn-build-service-prod[bot]
authored
Merge pull request #302512 from MicrosoftDocs/main
Auto Publish – main to live - 2025-07-10 05:00 UTC
2 parents 66eaca9 + 378808d commit 852a86b

File tree

9 files changed

+371
-45
lines changed

9 files changed

+371
-45
lines changed

‎articles/application-gateway/tutorial-url-redirect-powershell.md

Lines changed: 119 additions & 12 deletions
Large diffs are not rendered by default.

‎articles/private-link/network-security-perimeter-diagnostic-logs.md

Lines changed: 134 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,142 @@ Access logs categories for a network security perimeter are based on the results
3939
> [!NOTE]
4040
> The available access modes for a network security perimeter are **Transition** and **Enforced**. The **Transition** mode was previously named **Learning** mode. You may continue to see references to **Learning** mode in some instances.
4141
42+
## Access log schema
43+
44+
Every PaaS resource associated with the network security perimeter, generates access log(s) with unified log schema when enabled.
45+
> [!NOTE]
46+
> Network security perimeter access logs may have been aggregated. If the fields 'count' and 'timeGeneratedEndTime' are missing, consider the aggregation count as 1.
47+
48+
| **Value** | **Description** |
49+
| --- | --- |
50+
| **time** | The timestamp (UTC) of the first event in log aggregation window. |
51+
| **timeGeneratedEndTime** | The timestamp (UTC) of the last event in the log aggregation window. |
52+
| **count** | Number of logs aggregated. |
53+
| **resourceId** | The resource Id of the network security perimeter.|
54+
| **location** | The region of network security perimeter.|
55+
| **operationName** | The name of the PaaS resource operation represented by this event. |
56+
| **operationVersion** | The api-version associated with the operation. |
57+
| **category** | Log categories defined for Access logs. |
58+
| **properties** | Network security perimeter specific extended properties related to this category of events.|
59+
| **resultDescription** | The static text description of this operation on the PaaS resource, e.g. “Get storage file.” |
60+
61+
## Network security perimeter specific properties
62+
63+
This section describes the network security perimeter specific properties in the log schema.
64+
> [!NOTE]
65+
> Application of the properties is subjected to log category type. Do refer respective log category schemas for applicability.
66+
67+
| **Value** | **Description** |
68+
| --- | --- |
69+
| **serviceResourceId** | Resource ID of PaaS resource emitting network security perimeter access logs. |
70+
| **serviceFqdn** | Fully Qualified Domain Name of PaaS resource emitting network security perimeter access logs. |
71+
| **profile** | Name of the network security perimeter profile associated to the resource. |
72+
| **parameters** | List of optional PaaS resource properties in JSON string format. E.g., { {Param1}: {value1}, {Param2}: {value2}, ...}. |
73+
| **appId** | Unique GUID representing the app ID of resource in the Azure Active Directory. |
74+
| **matchedRule** | JSON property bag containing matched accessRule name, {"accessRule" : "{ruleName}"}. It can be either network security perimeter access rule Name or resource rule name (not the ArmId). |
75+
| **source** | JSON property bag describing source of the inbound connection. |
76+
| **destination** | JSON property bag describing destination of the outbound connection. |
77+
| **accessRulesVersion** | JSON property bag containing access rule version of the resource. |
78+
79+
## Source properties
80+
81+
Properties describing source of inbound connection.
82+
83+
| **Value** | **Description** |
84+
| --- | --- |
85+
| **resourceId** | Resource ID of source PaaS resource for an inbound connection. Will exist if applicable. |
86+
| **ipAddress** | IP address of source making inbound connection. Will exist if applicable. |
87+
| **port** | Port number of inbound connection. May not exist for all resource types. |
88+
| **protocol** | Application & transport layer protocols for inbound connection in format {AppProtocol}:{TptProtocol}. E.g., HTTPS:TCP. May not exist for all resource types. |
89+
| **perimeterGuids** | List of perimeter GUIDs of source resource. It should be specified only if allowed based on perimeter GUID. |
90+
| **appId** | Unique GUID representing the app ID of source in the Azure Active Directory. |
91+
| **parameters** | List of optional source properties in JSON string format. E.g., { {Param1}: {value1}, {Param2}: {value2}, ...}. |
92+
93+
## Destination properties
94+
Properties describing destination of outbound connection.
95+
96+
| **Value** | **Description** |
97+
| --- | --- |
98+
| **resourceId** | Resource ID of destination PaaS resource for an outbound connection. Will exist if applicable. |
99+
| **fullyQualifiedDomainName** | Fully Qualified Domain (FQDN) name of the destination. |
100+
| **parameters** | List of optional destination properties in JSON string format. E.g., { {Param1}: {value1}, {Param2}: {value2}, ...}. |
101+
| **port** | Port number of outbound connection. May not exist for all resource types. |
102+
| **protocol** | Application & transport layer protocols for outbound connection in the format {AppProtocol}:{TptProtocol}. E.g., HTTPS:TCP. May not exist for all resource types. |
103+
104+
## Sample log entry For inbound categories
105+
106+
``` json
107+
{
108+
"time" : "{timestamp}",
109+
"timeGeneratedEndTime" : "{timestamp}",
110+
"count" : "{countOfAggregatedLogs}",
111+
"resourceId" : "/SUBSCRIPTIONS/{subsId}/RESOURCEGROUPS/{resourceGroupName}/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYPERIMETERS/{perimeterName}",
112+
"operationName" : "{PaaSOperationName}" ,
113+
"operationVersion" : "{api-version}",
114+
"category" : "{inboundCategory}",
115+
"location" : "{networksecurityperimeterRegion}",
116+
"properties" : {
117+
"serviceResourceId" : "/subscriptions/{paasSubsId}/resourceGroups/{paasResourceGroupName}/providers/{provider}/{resourceType}/{resourceName}",
118+
"serviceFqdn": "{PaaSResourceFQDN}",
119+
"accessRulesVersion" : "{accessRulesVersion}",
120+
"profile" : "{networksecurityperimeterProfileName}",
121+
"appId" : "{resourceAppId}",
122+
"parameters" : "{ {ParameterType1}: {value1}, {ParameterType2}: {value2}, ...}", // Parsable JSON
123+
"matchedRule" : {
124+
"accessRule" : "{matchedRuleName}",
125+
},
126+
"source" : {
127+
"resourceId" : "/subscriptions/{sourceSubscriptionId}/resourceGroups/{sourceResourceGroupName}/providers/{sourceProvider}/{sourceResourceType}/{sourceResourceName}",
128+
"ipAddress": "{sourceIPAddress}",
129+
"perimeterGuids" : ["{sourcePerimeterGuid}"], // Only included if request comes from perimeter
130+
"appId" : "{sourceAppId}",
131+
"port" : "{Port}",
132+
"protocol" : "{Protocol}",
133+
"parameters" : "{ {ParameterType1}: {value1}, {ParameterType2}: {value2}, ...}", // Parsable JSON
134+
},
135+
},
136+
"resultDescription" : "The static text description of this operation on the PaaS resource. For example, \"Get storage file.\""
137+
}
138+
```
139+
140+
## Sample log entry for outbound categories
141+
142+
``` json
143+
{
144+
"time" : "{timestamp}",
145+
"timeGeneratedEndTime" : "{timestamp}",
146+
"count" : "{countOfAggregatedLogs}",
147+
"resourceId" : "/SUBSCRIPTIONS/{subsId}/RESOURCEGROUPS/{resourceGroupName}/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYPERIMETERS/{perimeterName}",
148+
"operationName" : "{PaaSOperationName}" ,
149+
"operationVersion" : "{api-version}",
150+
"category" : "{outboundCategory}",
151+
"location" : "{networksecurityperimeterRegion}",
152+
"properties" : {
153+
"serviceResourceId" : "/subscriptions/{paasSubsId}/resourceGroups/{paasResourceGroupName}/providers/{provider}/{resourceType}/{resourceName}",
154+
"serviceFqdn": "{PaaSResourceFQDN}",
155+
"accessRulesVersion" : "{accessRulesVersion}",
156+
"profile" : "{networksecurityperimeterProfileName}",
157+
"appId" : "{resourceAppId}",
158+
"parameters" : "{{ParameterType1}: {value1}, {ParameterType2}: {value2}, ...}", // Parsable JSON
159+
"matchedRule" : {
160+
"accessRule" : "{matchedRuleName}",
161+
},
162+
"destination" : {
163+
"resourceId" : "/subscriptions/{destSubsId}/resourceGroups/{destResourceGroupName}/providers/{destProvider}/{destResourceType}/{destResourceName}",
164+
"fullyQualifiedDomainName" : "{destFQDN}",
165+
"appId" : "{destAppId}",
166+
"port" : "{Port}",
167+
"protocol" : "{Protocol}",
168+
"parameters" : "{ {ParameterType1}: {value1}, {ParameterType2}: {value2}, ...}", // Parsable JSON
169+
},
170+
},
171+
"resultDescription" : "The static text description of this operation on the PaaS resource. For example, \"Get storage file.\""
172+
}
173+
```
174+
42175
## Logging destination options for access logs
43176

44-
The destinations for storing diagnostic logs for a network security perimeter include services like Log Analytic workspace, Azure Storage account, and Azure Event Hubs. For the full list and details of supported destinations, see [Supported destinations for diagnostic logs](/azure/azure-monitor/essentials/diagnostic-settings).
177+
The destinations for storing diagnostic logs for a network security perimeter include services like Log Analytic workspace (**Table name: NSPAccessLogs**), Azure Storage account, and Azure Event Hubs. For the full list and details of supported destinations, see [Supported destinations for diagnostic logs](/azure/azure-monitor/essentials/diagnostic-settings).
45178

46179
## Enable logging through the Azure portal
47180

‎articles/sre-agent/media/blue-check.png

745 Bytes
Loading

‎articles/sre-agent/overview.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,32 @@ Further, here are some prompts you can use to help you interact with your agent:
103103
- List [Container Apps/Web Apps/etc.] that you’re managing across all subscriptions.
104104
- Visualize split of Container Apps vs Web Apps vs AKS clusters managed across all subscriptions as a pie chart.
105105

106+
## Supported services
107+
108+
While Azure SRE Agent can help you manage and report on all Azure services, the agent features specialized tools for managing the following services:
109+
110+
- Azure API Management
111+
- Azure App Service
112+
- Azure Cache for Redis
113+
- Azure Container Apps
114+
- Azure Cosmos DB
115+
- Azure Database for PostgreSQL
116+
- Azure Functions
117+
- Azure Kubernetes Service
118+
- Azure SQL
119+
- Azure Storage
120+
- Azure Virtual Machines
121+
122+
To get the latest list of services with custom agent tooling, you can submit the following prompt to the agent:
123+
124+
```text
125+
Which Azure services do you have specialized tooling available for?
126+
```
127+
128+
### Identifying resource groups
129+
130+
As you create an agent, the resource group picker indicates groups that have instances of services with specialized tooling. From the resource group picker you'll see a checkmark (:::image type="icon" source="media/blue-check.png" border="false":::) next to the group name indicating the group includes services with specialized support.
131+
106132
## Preview access
107133

108134
Access to an SRE Agent is only available as in preview. To sign up for access, fill out the [SRE Agent application](https://go.microsoft.com/fwlink/?linkid=2319540).

‎articles/storage/file-sync/file-sync-planning.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,9 +82,7 @@ Azure File Sync is supported with the following versions of Windows Server:
8282
| Windows Server 2022 | Azure, Datacenter, Essentials, Standard, and IoT | Full and Core |
8383
| Windows Server 2019 | Datacenter, Essentials, Standard, and IoT | Full and Core |
8484
| Windows Server 2016 | Datacenter, Essentials, Standard, and Storage Server | Full and Core |
85-
| Windows Server 2012 R2* | Datacenter, Essentials, Standard, and Storage Server | Full and Core |
8685

87-
*Requires downloading and installing [Windows Management Framework (WMF) 5.1](https://www.microsoft.com/download/details.aspx?id=54616). The appropriate package to download and install for Windows Server 2012 R2 is **Win8.1AndW2K12R2-KB\*\*\*\*\*\*\*-x64.msu**.
8886

8987
> [!IMPORTANT]
9088
> We recommend keeping all servers that you use with Azure File Sync up to date with the latest updates from Windows Update.

‎articles/update-manager/arc-enabled-vm-extensions.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
title: Release notes for Arc-enabled VM extensions July 2025
3+
description: Learn about Azure Arc-enabled VM extensions, including their latest releases, known issues, and bug fixes, in the month of July to help you manage updates effectively.
4+
ms.service: azure-update-manager
5+
ms.date: 07/09/2025
6+
ms.topic: overview
7+
author: habibaum
8+
ms.author: v-uhabiba
9+
---
10+
11+
# Release notes for Azure Arc-enabled VM extensions - July 25
12+
13+
For Azure Arc-enabled machines, two extensions are installed. For more information, see [How Update Manager works](workflow-update-manager.md)
14+
15+
16+
The Azure Arc-enabled VM extensions receive improvements on an ongoing basis. This article provides you with the following information to help you stay up to date with the latest developments:
17+
18+
- The latest releases
19+
- Known issues
20+
- Bug fixes
21+
22+
## Windows extension
23+
24+
Update this when future versions are released.
25+
26+
## Linux extensions
27+
28+
### July 2025
29+
30+
#### Extension name: Microsoft.SoftwareUpdateManagement.LinuxOsUpdateExtension
31+
#### Extension Version: 1.0.55.0
32+
33+
Added support for management of following distributions:
34+
35+
- Ubuntu 24
36+
- Debian 12
37+
38+
In previous releases, patching an Ubuntu 24.04 server failed with the error: **E: the list of sources couldn't be read**.
39+
40+
41+
## Next steps
42+
43+
- [How Update Manager works](workflow-update-manager.md)
44+
- [Prerequisites of Update Manager](prerequisites.md)
45+
- [View updates for a single machine](view-updates.md).
46+
- [Deploy updates now (on-demand) for a single machine](deploy-updates.md).
47+
- [Enable periodic assessment at scale using policy](https://aka.ms/aum-policy-support).
48+
- [Schedule recurring updates](scheduled-patching.md)
49+
- [Manage update settings via the portal](manage-update-settings.md).
50+
- [Manage multiple machines by using Update Manager](manage-multiple-machines.md).
51+

‎articles/update-manager/overview-arc-enabled-vm-extensions.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Release notes of Arc-enabled VM extensions
2+
title: Release notes of Arc-enabled VM extensions May 2025
33
description: Learn about Azure Arc-enabled VM extensions, including their latest releases, known issues, and bug fixes, to help you manage updates effectively.
44
ms.service: azure-update-manager
55
ms.date: 03/28/2025
@@ -9,12 +9,12 @@ ms.author: v-uhabiba
99
# Customer intent: "As a cloud administrator, I want to stay updated on the latest improvements and bug fixes for Azure Arc-enabled VM extensions, so that I can effectively manage updates and troubleshoot any issues that arise."
1010
---
1111

12-
# Release notes for Azure Arc-enabled VM extensions
12+
# Release notes for Azure Arc-enabled VM extensions - March 25
1313

1414
For Azure Arc-enabled machines, two extensions are installed. For more information, see [How Update Manager works](workflow-update-manager.md)
1515

1616

17-
The Azure Arc-enabled VM extensions receive improvements on an ongoing basis. To stay up to date with the most recent developments, this article provides you with the information about:
17+
The Azure Arc-enabled VM extensions receive improvements on an ongoing basis. This article provides you with the following information to help you stay up to date with the latest developments:
1818

1919
- The latest releases
2020
- Known issues
@@ -33,7 +33,7 @@ The Azure Arc-enabled VM extensions receive improvements on an ongoing basis. To
3333
- Current error message: *An internal error occurred while processing the operation.*
3434
- New error message: *Windows update API threw an exception while assessing the machine for available updates. HResult: 0x80004005*
3535
> [!NOTE]
36-
> The HResult could be different, based on the issue.
36+
> The HResult changes based on the issue.
3737
3838
- Fixed an issue where at times the extension status is stuck in **Creating state**. Then the assessment or install updates job fails with the following error: *Extension failed during enable. Extension Enable command timed out.*
3939

@@ -43,7 +43,6 @@ The Azure Arc-enabled VM extensions receive improvements on an ongoing basis. To
4343

4444
To be updated as and when future versions are released.
4545

46-
4746
## Next steps
4847

4948
- [How Update Manager works](workflow-update-manager.md)

‎articles/update-manager/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ items:
1717
items:
1818
- name: March 2025
1919
href: overview-arc-enabled-vm-extensions.md
20+
- name: July 2025
21+
href: arc-enabled-vm-extensions.md
2022
- name: Getting started
2123
items:
2224
- name: Prerequisites

0 commit comments

Comments
 (0)