Skip to content

Commit fecd639

Browse files
author
Pat Altimore
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-gateway-diagram
2 parents 00a1bca + f2ebbeb commit fecd639

17 files changed

+445
-115
lines changed

articles/application-gateway/configure-web-app.md

Lines changed: 53 additions & 52 deletions
Large diffs are not rendered by default.

articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: mbender-ms
77
ms.service: azure-appgw-for-containers
88
ms.custom: devx-track-azurecli
99
ms.topic: quickstart
10-
ms.date: 5/2/2025
10+
ms.date: 7/9/2025
1111
ms.author: mbender
1212
# Customer intent: As a Kubernetes administrator, I want to install the Application Gateway for Containers ALB Controller on my AKS cluster, so that I can efficiently manage load balancing rules and enhance application traffic handling.
1313
---
@@ -181,7 +181,6 @@ You need to complete the following tasks before deploying Application Gateway fo
181181
182182
| NAME | READY | STATUS | RESTARTS | AGE |
183183
| ---------------------------------------- | ----- | ------- | -------- | ---- |
184-
| alb-controller-bootstrap-6648c5d5c-hrmpc | 1/1 | Running | 0 | 4d6h |
185184
| alb-controller-6648c5d5c-sdd9t | 1/1 | Running | 0 | 4d6h |
186185
| alb-controller-6648c5d5c-au234 | 1/1 | Running | 0 | 4d6h |
187186

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

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

articles/backup/azure-file-share-support-matrix.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Support Matrix for Azure files backup by using Azure Backup
33
description: Provides a summary of support settings and limitations when backing up Azure files.
44
ms.topic: reference
5-
ms.date: 07/03/2025
5+
ms.date: 07/10/2025
66
ms.custom: references_regions, engagement-fy24
77
ms.service: azure-backup
88
author: jyothisuri
@@ -33,7 +33,7 @@ Vaulted backup for Azure Files is available in the following regions: UK South,
3333

3434
Cross Region Restore is supported in all preceding regions, except Italy North.
3535

36-
Migration of File Shares protected with snapshot backup to vaulted backup is supported in the following regions: UK South, UK West, Southeast Asia, East Asia, West Central US, and India Central.
36+
Migration of File Shares protected with snapshot backup to vaulted backup is supported in the following regions: UK South, UK West, Southeast Asia, East Asia, West Central US, India Central, Spain Central, Jio India West, Israel Central, Australia Central 2 and Germany North.
3737

3838
>[!Note]
3939
>Cross Subscription Backup and Restore are supported for vaulted backup.

articles/oracle/oracle-db/oracle-database-regions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
5757
| West US | US West (San Jose) |||| | Preview available | Single |
5858
| Central US | US Midwest (Chicago) |||| | | Dual |
5959
| East US 2 | US East (Ashburn) || | | | | Dual |
60-
| South Central US || | | | | | Dual |
60+
| South Central US |Dallas|| | | | | Dual |
6161

6262
> [!NOTE]
6363
> To provision Oracle Database@Azure resources in a supported region, your tenancy must be subscribed to the target region. Learn how to [manage regions](https://docs.oracle.com/iaas/Content/Identity/regions/managingregions.htm#Managing_Regions) and [subscribe to an infrastructure region](https://docs.oracle.com/iaas/Content/Identity/regions/To_subscribe_to_an_infrastructure_region.htm#subscribe).

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

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/storage/files/encryption-in-transit-for-nfs-shares.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ EiT is now Generally Available (GA) in all regions that support Azure Premium Fi
4747

4848
### Register for preview (not needed for GA regions)
4949

50-
To enable encryption in transit for your storage accounts and NFS shares in the preview regions (China North3, New Zealand North, West Europe, US East2, US Central, US South, and Korea Central), you must register for the preview. **No registration is needed in the GA regions.**
50+
To enable encryption in transit for your storage accounts and NFS shares in the preview regions (China North3, New Zealand North, West Europe, US Central, US South, and Korea Central), you must register for the preview. **No registration is needed in the GA regions.**
5151

5252
### [Portal](#tab/azure-portal)
5353

0 commit comments

Comments
 (0)