Skip to content

Commit 0395fcf

Browse files
authored
Merge pull request #291720 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 79e0688 + 9be5908 commit 0395fcf

File tree

3 files changed

+5
-3
lines changed

3 files changed

+5
-3
lines changed

articles/container-apps/how-to-use-private-endpoint.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ In this article, you learn how to use a private endpoint to securely access your
1717

1818
A private endpoint uses a private IP address from your virtual network (VNet). This endpoint connects you privately and securely to a service powered by [Azure Private Link](/azure/private-link/private-link-overview).
1919

20+
Private endpoints on Azure Container Apps only support inbound HTTP traffic. TCP traffic is not supported.
21+
2022
::: zone pivot="azure-portal"
2123

2224
## Prerequisites

articles/migrate/migrate-services-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Azure Migrate provides a simplified migration, modernization, and optimization s
2222

2323
- **Decide**: The first step in a migration journey is to identify your workloads. This process of identification is known as discovery. To discover your workloads, you can deploy a light-weight [Azure Migrate appliance](migrate-appliance.md) (recommended approach) or quickly import the inventory data for your workloads. The Azure Migrate appliance is a virtual appliance that can be deployed on a server on your datacenter. The appliance collects the configuration and performance data for your servers and continually sends it over to Azure Migrate Service. Once the inventory of workloads is identified, you can create a business case to make your decision to migrate to Azure.
2424

25-
- **Business case** helps you decide if you should migrate your on-premises workloads to Azure, by estimating the costs and savings of moving to Azure. The business case helps you identify-
25+
- **Business case** helps you decide if you should migrate your on-premises workloads to Azure, by estimating the costs and savings of moving to Azure. The business case helps you identify-
2626
- On-premises vs Azure total cost of ownership
2727
- YoY comparison of cash flows
2828
- Resource utilization-based insights on Azure targets.
@@ -92,7 +92,7 @@ Azure Migrate has a suite of the following tools integrated within the product:
9292
[Lakeside](https://go.microsoft.com/fwlink/?linkid=2104908) | Assess VDI.
9393
[RackWare](https://go.microsoft.com/fwlink/?linkid=2102735) | Migrate servers.
9494
[Turbonomic](https://go.microsoft.com/fwlink/?linkid=2094295) | Assess servers.
95-
[UnifyCloud](https://www.cloudatlasinc.com/cloudrecon/) | Assess servers and databases.
95+
[UnifyCloud: CloudRecon](https://www.cloudatlasinc.com/cloudrecon/) | Assess servers and databases.
9696
[Zerto](https://go.microsoft.com/fwlink/?linkid=2152102) | Migrate servers.
9797

9898
## Next steps

articles/service-connector/includes/code-postgres-me-id.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -364,4 +364,4 @@ For other languages, use the connection properties that Service Connector sets t
364364

365365
---
366366

367-
[!INCLUDE [Postgresql grant permission](./postgres-grant-permission.md)]
367+
[!INCLUDE [PostgreSQL grant permission](./postgres-grant-permission.md)]

0 commit comments

Comments
 (0)