You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/api-mgmt/availability/request-throttling-http-403.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,4 +65,4 @@ Apart from the above, we are also encountering **HTTP 429 - Too many requests**
65
65
66
66
Read more about [ip-filter](/azure/api-management/api-management-access-restriction-policies#RestrictCallerIPs) and [rate-limit-by-key](/azure/api-management/api-management-access-restriction-policies#LimitCallRateByKey) policies in APIM.
67
67
68
-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/api-mgmt/availability/soap-based-api-return-404-http-code.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,4 +170,4 @@ You need to understand who is throwing these HTTP 404 and 500 responses, APIM, o
170
170
171
171
:::image type="content" source="media/soap-based-api-return-404-500-http-code/intb-value.png" alt-text="Screenshot of the intB value that is set to zero.":::
172
172
173
-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/api-mgmt/availability/unauthorized-errors-invoke-apis.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,4 +64,4 @@ The expected HTTP response code for all the operations is 200, however the respo
64
64
65
65
Developers must first subscribe to a product to get access to the API. When they subscribe, they get a subscription key that is good for any API in that product. If you created the APIM instance, you are an administrator already, so you are subscribed to every product by default.
66
66
67
-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/app-service/backing-up-restoring-and-cloning-microsoft-azure-app-services.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,4 +18,4 @@ In this video, you will learn about different kinds of backup and restore proced
18
18
19
19
For more troubleshooting tips, see [My backups are failing - Azure App Service](https://azure.github.io/AppService/2018/01/02/My-Backups-are-failing%2c-Let%27s-open-a-support-ticket.html)
20
20
21
-
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-custom-domain-issues-azure-app-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -335,6 +335,6 @@ domain might be intended for internal use only.
335
335
336
336
**Solution**: Verify the IP where your custom domain is resolving. If it's a private address, then external users can't reach it by design. In such cases, either expose the site by using a public IP or proxy, or make sure that clients are within the network (for example, by using a VPN). If this situation isn't intentional, you might have configured a private endpoint. Consider removing the private endpoint for a purely public web app. If you expected internal-only access, and you see external exposure, make sure that you didn't use a public DNS for an internal app. Internal apps should use DNS entries that resolve internally only (for example, by using Azure Private DNS). Make sure that you match your DNS configuration to your network setup.
Copy file name to clipboardExpand all lines: support/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-domain-and-tls-ssl-certificates.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -385,4 +385,4 @@ Also, if your CA gives you multiple certificates in the certificate chain, you h
385
385
For an App Service certificate, you purchase through the Azure portal or by using a Powershell/CLI command. A certificate-signing request isn't needed. However, Azure Key Vault supports storing digital certificates issued by any CA. It supports creating a certificate-signing request with a private/public key pair. The certificate-signing request can be signed by any CA (an internal enterprise CA or an external public CA). For more information, see [Create a certificate-signing request](/azure/key-vault/certificates/create-certificate-signing-request).
386
386
387
387
388
-
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments