Skip to content

Commit f27fed9

Browse files
authored
Merge pull request #303541 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents dccf45e + c6fe6bf commit f27fed9

File tree

3 files changed

+6
-2
lines changed

3 files changed

+6
-2
lines changed

articles/app-service/tutorial-ai-openai-chatbot-python.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection: ce-skilling-ai-copilot
1515

1616
# Tutorial: Build a chatbot with Azure App Service and Azure OpenAI (Flask)
1717

18-
In this tutorial, you'll build an intelligent AI application by integrating Azure OpenAI with a Python web application and deploying it to Azure App Service. You'll create a Flask app that sends chat completion requests to a model in Azure OpneAI.
18+
In this tutorial, you'll build an intelligent AI application by integrating Azure OpenAI with a Python web application and deploying it to Azure App Service. You'll create a Flask app that sends chat completion requests to a model in Azure OpenAI.
1919

2020
:::image type="content" source="media/tutorial-ai-openai-chatbot-python/chat-in-browser.png" alt-text="Screenshot showing chatbot running in Azure App Service.":::
2121

articles/application-gateway/application-gateway-private-deployment.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -187,6 +187,10 @@ The resource tag is cosmetic, and serves to confirm that the gateway has been pr
187187

188188
Application Gateway Subnet is the subnet within the Virtual Network where the Application Gateway Resources will be deployed. In the Frontend Private Ip configuration, is important that this subnet can reach privately the resources that want to connect to your exposed app or site.
189189

190+
> [!NOTE]
191+
> As of May 5, 2025, new and existing deployments of Private Application Gateway require Subnet Delegation to `Microsoft.Network/applicationGateways`.
192+
> Please follow [these steps](/azure/virtual-network/manage-subnet-delegation?tabs=manage-subnet-delegation-portal) for configuring Subnet Delegation.
193+
190194
## Outbound Internet connectivity
191195

192196
Application Gateway deployments that contain only a private frontend IP configuration (do not have a public IP frontend configuration associated to a request routing rule) aren't able to egress traffic destined to the Internet. This configuration affects communication to backend targets that are publicly accessible via the Internet.

articles/virtual-network/ip-services/public-ip-address-prefix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ You can associate the following resources to a static public IP address from a p
4949

5050
|Resource|Scenario|Steps|
5151
|---|---|---|
52-
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/).
52+
|Virtual machines| Associating public IPs from a prefix to your virtual machines in Azure reduces management overhead when adding IP addresses to an allowlist in the firewall. You can add an entire prefix with a single firewall rule. As you scale with virtual machines in Azure, you can associate IPs from the same prefix saving cost, time, and management overhead.| To associate IPs from a prefix to your virtual machine:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. [Associate the IP to your virtual machine's network interface.](./virtual-network-network-interface-addresses.md#add-ip-addresses)</br> You can also [associate the IPs to a Virtual Machine Scale Set](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/). In the event you'll need the public IP address to be available to route internally, the [Public IP Prefix can be added to the VNET](../how-to-multiple-prefixes-subnet.md), and then assigned to the Virtual Machine as an IP address from a subnet that the VM participates in.
5353
| Standard load balancers | Associating public IPs from a prefix to your frontend IP configuration or outbound rule of a load balancer ensures simplification of your Azure public IP address space. Simplify your scenario by grooming outbound connections from a range of contiguous IP addresses. | To associate IPs from a prefix to your load balancer:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. When creating the load balancer, select or update the IP created in step 2 above as the frontend IP of your load balancer. |
5454
| Azure Firewall | You can use a public IP from a prefix for outbound SNAT. All outbound virtual network traffic is translated to the [Azure Firewall](../../firewall/overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) public IP. | To associate an IP from a prefix to your firewall:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. When you [deploy the Azure firewall](../../firewall/tutorial-firewall-deploy-portal.md?toc=%2fazure%2fvirtual-network%2ftoc.json#create-a-virtual-network), be sure to select the IP you previously gave from the prefix.|
5555
| VPN Gateway (AZ SKU), Application Gateway v2, NAT Gateway | You can use a public IP from a prefix for your gateway | To associate an IP from a prefix to your gateway:</br> 1. [Create a prefix.](manage-public-ip-address-prefix.md)</br> 2. [Create an IP from the prefix.](manage-public-ip-address-prefix.md)</br> 3. When you deploy the [VPN Gateway](../../vpn-gateway/tutorial-create-gateway-portal.md), [Application Gateway](../../application-gateway/quick-create-portal.md#create-an-application-gateway), or [NAT Gateway](../nat-gateway/quickstart-create-nat-gateway-portal.md), be sure to select the IP you previously gave from the prefix.|

0 commit comments

Comments
 (0)