Skip to content

Commit 98fb810

Browse files
authored
Merge pull request #296796 from MicrosoftDocs/main
3/21/2025 PM Publish
2 parents f418541 + 3c0fb4f commit 98fb810

File tree

123 files changed

+1025
-277
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

123 files changed

+1025
-277
lines changed

articles/api-management/inject-vnet-v2.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dlepow
55
ms.author: danlep
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 11/18/2024
8+
ms.date: 03/20/2025
99
---
1010

1111
# Inject an Azure API Management instance in a private virtual network - Premium v2 tier
@@ -14,6 +14,9 @@ ms.date: 11/18/2024
1414

1515
This article guides you through the requirements to inject your Azure API Management Premium v2 (preview) instance in a virtual network.
1616

17+
> [!NOTE]
18+
> The Premium v2 tier is currently in limited preview. To sign up, fill [this form](https://aka.ms/premiumv2).
19+
1720
> [!NOTE]
1821
> To inject a classic Developer or Premium tier instance in a virtual network, the requirements and configuration are different. [Learn more](virtual-network-injection-resources.md).
1922
@@ -54,7 +57,7 @@ If you want to enable *public* inbound access to an API Management instance in t
5457

5558
### Network security group
5659

57-
A network security group must be associated with the subnet.
60+
A network security group must be associated with the subnet. No specific rules are required. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
5861

5962
### Subnet delegation
6063

articles/api-management/integrate-vnet-outbound.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dlepow
55
ms.author: danlep
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 11/18/2024
8+
ms.date: 03/20/2025
99
---
1010

1111
# Integrate an Azure API Management instance with a private virtual network for outbound connections
@@ -48,7 +48,7 @@ If you want to inject a Premium v2 API Management instance into a virtual networ
4848

4949
### Network security group
5050

51-
A network security group must be associated with the subnet.
51+
A network security group must be associated with the subnet. No specific rules are required. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
5252

5353
### Subnet delegation
5454

articles/app-service/configure-language-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: astay
77
ms.author: msangapu
88
author: msangapu-msft
99
ms.devlang: python
10-
ms.custom: mvc, devx-track-python, devx-track-azurecli, mode-other, py-fresh-zinc, linux-related-content
10+
ms.custom: mvc, devx-track-python, devx-track-azurecli, mode-other, py-fresh-zinc, linux-related-content, innovation-engine
1111
adobe-target: true
1212
---
1313

68.1 KB
Loading
77 KB
Loading

articles/app-service/routine-maintenance.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Like personal computers, mobile phones, and other devices, machines in the cloud
2424

2525
Because a typical cloud solution consists of multiple applications, databases, storage accounts, functions, and other resources, parts of your solutions can undergo maintenance at different times. Some of this coordination is related to geography, region, datacenters, and availability zones. It can also be due to the cloud, where not everything is touched simultaneously. For more information, see [Safe deployment practices](/devops/operate/safe-deployment-practices).
2626

27-
The following screenshot shows an example of a maintenance event.
27+
The following screenshot shows an example of a maintenance event:
2828

2929
:::image type="content" source="./media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure portal.":::
3030

@@ -34,6 +34,23 @@ In order from top to bottom, the example shows:
3434
- Affected regions and subscriptions.
3535
- The expected maintenance window.
3636

37+
The following screenshots show additional information available through the Impacted Resources dropdown:
38+
39+
:::image type="content" source="./media/routine-maintenance/routine-maintenance-first-page.png" alt-text="Screenshot of the Impacted Resources blade in the Azure portal.":::
40+
41+
In order from left to right, the example shows:
42+
43+
- Selecting the "Impacted Resources" dropdown.
44+
- The "More info" option.
45+
46+
:::image type="content" source="./media/routine-maintenance/routine-maintenance-more.png" alt-text="Screenshot of more info for a maintenance event in the Azure portal.":::
47+
48+
This example shows:
49+
50+
- The state of the maintenance, which can be pending, started, or completed.
51+
- Once maintenance starts, timestamps can be viewed under "More info."
52+
53+
3754
## Frequently asked questions
3855

3956
### Why is the maintenance taking so long?

articles/application-gateway/for-containers/how-to-cert-manager-lets-encrypt-gateway-api.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: azure-appgw-for-containers
77
ms.topic: how-to
8-
ms.date: 3/7/2025
8+
ms.date: 3/31/2025
99
ms.author: greglin
1010
---
1111

@@ -15,7 +15,7 @@ This guide demonstrates how to use cert-manager to automatically issue and renew
1515

1616
For the purposes of this example, we have cert-manager configure certificates issued from Let's Encrypt to demonstrate an end-to-end deployment, where Application Gateway for Containers is providing TLS offloading.
1717

18-
![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg)
18+
[ ![A figure showing cert-manager retrieving a certificate from Let's Encrypt and storing it into Kubernetes' secret store for TLS with Application Gateway for Containers.](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg) ](./media/how-to-cert-manager-lets-encrypt-gateway-api/how-to-cert-manager-lets-encrypt-gateway-api.svg#lightbox)
1919

2020
For certificates to be issued by Let's Encrypt, a challenge is required by the authority to validate domain ownership. This validation happens by allowing cert-manager to create a pod and HTTPRoute resource that exposes an endpoint during certificate issuance, proving your ownership of the domain name.
2121

@@ -437,7 +437,7 @@ Now we're ready to send some traffic to our sample application, via the hostname
437437
curl https://contoso.com/ -v 2>&1 | grep issuer
438438
```
439439

440-
Upon result, you should see
440+
You should see the following output:
441441

442442
`* issuer: C=US; O=Let's Encrypt; CN=R10`
443443

articles/application-gateway/how-to-tcp-tls-proxy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: application-gateway
66
author: greg-lindsay
77
ms.service: azure-application-gateway
88
ms.topic: how-to
9-
ms.date: 02/26/2024
9+
ms.date: 03/21/2025
1010
ms.author: greglin
1111
---
1212

@@ -177,7 +177,7 @@ First, create a SQL Server virtual machine (VM) using the Azure portal.
177177
- Configured the SQL server to accept SQL authentication
178178
- Created an admin account on the SQL server
179179

180-
2. On a client device with [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) installed, connect to the public IP address of the Azure virtual machine.
180+
2. On a client device with [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) installed, connect to the public IP address of the Azure Application Gateway frontend.
181181

182182
<br><img src="./media/how-to-tcp-tls-proxy/sql-connect.png" alt="Screenshot displaying the connection to a SQL server." width="60%">
183183

articles/azure-functions/TOC.yml

Lines changed: 30 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -585,21 +585,6 @@
585585
href: ../operational-excellence/relocation-functions.md?toc=/azure/azure-functions/toc.json
586586
- name: Work with legacy Functions Proxies
587587
href: legacy-proxies.md
588-
- name: Migrate
589-
items:
590-
- name: Migrate .NET apps to the isolated model
591-
href: migrate-dotnet-to-isolated-model.md
592-
- name: Migrate v3.x to v4.x
593-
href: migrate-version-3-version-4.md
594-
- name: Migrate v1.x to v4.x
595-
href: migrate-version-1-version-4.md
596-
- name: Node.js
597-
items:
598-
- name: Migrate to model v4.x
599-
href: functions-node-upgrade-v4.md
600-
- name: Update language versions
601-
href: update-language-versions.md
602-
displayName: upgrade, migrate, language stack
603588
- name: Monitor
604589
items:
605590
- name: Monitor Azure Functions
@@ -747,6 +732,36 @@
747732
href: python-scale-performance-reference.md
748733
- name: Memory profiling
749734
href: python-memory-profiler-reference.md
735+
- name: Migration guides
736+
items:
737+
- name: Migrate from AWS Lambda
738+
items:
739+
- name: Overview
740+
href: migration/lambda-functions-migration-overview.md
741+
displayName: AWS Lambda, migration
742+
- name: Discover
743+
href: migration/lambda-functions-migration-discover.md
744+
displayName: AWS Lambda, migration
745+
- name: Assess
746+
href: migration/lambda-functions-migration-assess.md
747+
displayName: AWS Lambda, migration
748+
- name: Migrate
749+
href: migration/lambda-functions-migration-migrate.md
750+
displayName: AWS Lambda, migration
751+
- name: Upgrade runtime versions
752+
items:
753+
- name: Migrate v3.x to v4.x
754+
href: migrate-version-3-version-4.md
755+
- name: Migrate v1.x to v4.x
756+
href: migrate-version-1-version-4.md
757+
- name: Language version updates
758+
items:
759+
- name: Update language versions
760+
href: update-language-versions.md
761+
displayName: upgrade, migrate, language stack
762+
- name: Migrate Node.js to model v4.x
763+
href: functions-node-upgrade-v4.md
764+
750765
- name: Reference
751766
items:
752767
- name: API references

0 commit comments

Comments
 (0)