Skip to content

Commit 6e3762b

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 431a700 + ac49dc0 commit 6e3762b

File tree

116 files changed

+1205
-948
lines changed

Some content is hidden

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

116 files changed

+1205
-948
lines changed

articles/app-service/environment/ase-multi-tenant-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ App Service Environment v3 tends to be more expensive than the public multitenan
7474
|Pricing |[Pay per instance](overview.md#pricing)|[Pay per instance](../../app-service/overview-hosting-plans.md)|
7575
|Reserved instances|[Available](overview.md#pricing)|[Available](../../app-service/overview-hosting-plans.md)|
7676
|Savings plans|[Available](overview.md#pricing)|[Available](../../app-service/overview-hosting-plans.md)|
77-
|Availability zone pricing|[There's a minimum charge of 18 cores.](overview.md#pricing) There's no added charge for availability zone support if you have 18 or more cores across your App Service plan instances. If you have fewer than 18 cores across your App Service plans in the zone redundant App Service Environment, the difference between 18 cores and the sum of the cores from the running instance count is charged as Windows I1v2 instances.|[Three instance minimum enforced per App Service plan](../../reliability/reliability-app-service.md#pricing).|
77+
|Availability zone pricing|[There's a minimum charge of 18 cores.](overview.md#pricing) There's no added charge for availability zone support if you have 18 or more cores across your App Service plan instances. If you have fewer than 18 cores across your App Service plans in the zone redundant App Service Environment, the difference between 18 cores and the sum of the cores from the running instance count is charged as Windows I1v2 instances.|[Three instance minimum enforced per App Service plan](../../reliability/reliability-app-service.md#cost).|
7878

7979
### Frequently asked questions
8080

articles/app-service/network-secure-outbound-traffic-azure-firewall.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ Outbound traffic from your app is now routed through the integrated virtual netw
9999
1. Navigate to the firewall's overview page and select its firewall policy.
100100

101101
1. In the firewall policy page, from the left navigation, select **Application Rules** > **Add a rule collection**.
102-
1. In **Rules**, add a network rule with the App Service subnet as the source address, and specify an FQDN destination. In the screenshot below, the destination FQDN is set to `api.my-ip.io`.
102+
1. In **Rules**, add a network rule with the App Service subnet as the source address, and specify an FQDN destination. In the screenshot below, the destination FQDN is set to `contoso.com`.
103103

104104
:::image type="content" source="./media/network-secure-outbound-traffic-azure-firewall/config-azfw-policy-app-rule.png" alt-text="Screenshot of configure Azure Firewall policy rule.":::
105105

@@ -113,7 +113,7 @@ Outbound traffic from your app is now routed through the integrated virtual netw
113113
An easy way to verify your configuration is to use the `curl` command from your app's SCM debug console to verify the outbound connection.
114114

115115
1. In a browser, navigate to `https://<app-name>.scm.azurewebsites.net/DebugConsole`.
116-
1. In the console, run `curl -s <protocol>://<fqdn-address>` with a URL that matches the application rule you configured, To continue example in the previous screenshot, you can use **curl -s https://api.my-ip.io/ip**. The following screenshot shows a successful response from the API, showing the public IP address of your App Service app.
116+
1. In the console, run `curl -s <protocol>://<fqdn-address>` with a URL that matches an application rule you configured. The following screenshot is an example to a website that shows a successful response from a API, showing an IP address.
117117

118118
:::image type="content" source="./media/network-secure-outbound-traffic-azure-firewall/verify-outbound-traffic-fw-allow-rule.png" alt-text="Screenshot of verifying the success outbound traffic by using curl command in SCM debug console.":::
119119

articles/application-gateway/for-containers/how-to-backend-mtls-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ See the following figure:
3434
Apply the following deployment.yaml file on your cluster to create a sample web application and deploy sample secrets to demonstrate backend mutual authentication (mTLS).
3535

3636
```bash
37-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/https-scenario/end-to-end-ssl-with-backend-mtls/deployment.yaml
37+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/https-scenario/end-to-end-ssl-with-backend-mtls/deployment.yaml
3838
```
3939

4040
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-end-to-end-tls-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Application Gateway for Containers enables end-to-end TLS for improved privacy a
3030
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate TLS/SSL offloading.
3131

3232
```bash
33-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/https-scenario/end-to-end-tls/deployment.yaml
33+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/https-scenario/end-to-end-tls/deployment.yaml
3434
```
3535

3636
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-end-to-end-tls-ingress-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Application Gateway for Containers enables end-to-end TLS for improved privacy a
2727
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate TLS/SSL offloading.
2828

2929
```bash
30-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/https-scenario/end-to-end-tls/deployment.yaml
30+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/https-scenario/end-to-end-tls/deployment.yaml
3131
```
3232

3333
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-frontend-mtls-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The revoked client certificate flow shows a client presenting a revoked certific
3838
Apply the following deployment.yaml file on your cluster to create a sample web application and deploy sample secrets to demonstrate frontend mutual authentication (mTLS).
3939

4040
```bash
41-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/https-scenario/ssl-termination/deployment.yaml
41+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/https-scenario/ssl-termination/deployment.yaml
4242
```
4343

4444
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-header-rewrite-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following figure illustrates a request with a specific user agent being rewr
3333
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate the header rewrite.
3434

3535
```bash
36-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
36+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
3737
```
3838

3939
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-header-rewrite-ingress-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following figure illustrates an example of a request with a specific user ag
3333
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate the header rewrite.
3434

3535
```bash
36-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
36+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
3737
```
3838

3939
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-multiple-site-hosting-gateway-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Application Gateway for Containers enables multi-site hosting by allowing you to
3030
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate path, query, and header based routing.
3131

3232
```bash
33-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
33+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
3434
```
3535

3636
This command creates the following on your cluster:

articles/application-gateway/for-containers/how-to-multiple-site-hosting-ingress-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Application Gateway for Containers enables multi-site hosting by allowing you to
2929
Apply the following deployment.yaml file on your cluster to create a sample web application to demonstrate path, query, and header based routing.
3030

3131
```bash
32-
kubectl apply -f https://learn.microsoft.com/azure/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
32+
kubectl apply -f https://raw.githubusercontent.com/MicrosoftDocs/azure-docs/refs/heads/main/articles/application-gateway/for-containers/examples/traffic-split-scenario/deployment.yaml
3333
```
3434

3535
This command creates the following on your cluster:

0 commit comments

Comments
 (0)