Skip to content

Commit 442d0fa

Browse files
authored
Merge pull request #99070 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
2 parents 2909908 + 05f5c9e commit 442d0fa

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

articles/api-management/api-management-howto-mutual-certificates.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,14 +28,14 @@ For information about managing certificates using the API Management REST API, s
2828

2929
This guide shows you how to configure your API Management service instance to use client certificate authentication to access the back-end service for an API. Before following the steps in this article, you should have your back-end service configured for client certificate authentication ([to configure certificate authentication in Azure WebSites refer to this article][to configure certificate authentication in Azure WebSites refer to this article]). You need access to the certificate and the password for uploading it to the API Management service.
3030

31-
## <a name="step1"> </a>Upload a client certificate
31+
## <a name="step1"> </a>Upload a Certificate
3232

33-
![Add client certificates](media/api-management-howto-mutual-certificates/apim-client-cert.png)
33+
![Add client certificates](media/api-management-howto-mutual-certificates/apim-client-cert-new.png)
3434

3535
Follow the steps below to upload a new client certificate. If you have not created an API Management service instance yet, see the tutorial [Create an API Management service instance][Create an API Management service instance].
3636

3737
1. Navigate to your Azure API Management service instance in the Azure portal.
38-
2. Select **Client certificates** from the menu.
38+
2. Select **Certificates** from the menu.
3939
3. Click the **+ Add** button.
4040
![Add client certificates](media/api-management-howto-mutual-certificates/apim-client-cert-add.png)
4141
4. Browse for the certificate, provide its ID and password.
@@ -44,7 +44,7 @@ Follow the steps below to upload a new client certificate. If you have not creat
4444
> [!NOTE]
4545
> The certificate must be in **.pfx** format. Self-signed certificates are allowed.
4646
47-
Once the certificate is uploaded, it shows in the **Client certificates**. If you have many certificates, make a note of the thumbprint of the desired certificate in order to [Configure an API to use a client certificate for gateway authentication][Configure an API to use a client certificate for gateway authentication].
47+
Once the certificate is uploaded, it shows in the **Certificates**. If you have many certificates, make a note of the thumbprint of the desired certificate in order to [Configure an API to use a client certificate for gateway authentication][Configure an API to use a client certificate for gateway authentication].
4848

4949
> [!NOTE]
5050
> To turn off certificate chain validation when using, for example, a self-signed certificate, follow the steps described in this FAQ [item](api-management-faq.md#can-i-use-a-self-signed-ssl-certificate-for-a-back-end).
@@ -53,7 +53,7 @@ Once the certificate is uploaded, it shows in the **Client certificates**. If y
5353

5454
To delete a certificate, click context menu **...** and select **Delete** beside the certificate.
5555

56-
![Delete client certificates](media/api-management-howto-mutual-certificates/apim-client-cert-delete.png)
56+
![Delete client certificates](media/api-management-howto-mutual-certificates/apim-client-cert-delete-new.png)
5757

5858
If the certificate is in use by an API, then a warning screen is displayed. To delete the certificate, you must first remove the certificate from any APIs that are configured to use it.
5959

8.33 KB
Loading
21.9 KB
Loading

articles/azure-resource-manager/move-limitations/app-service-move-limitations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ When moving a Web App across subscriptions, the following guidance applies:
1818
- App Service plans
1919
- Uploaded or imported SSL certificates
2020
- App Service Environments
21-
- All App Service resources in the resource group must be moved together.
21+
- All App Service resources in the resource group must be moved together. Note that App Service Environments cannot be moved to a new Resource Group nor to a new Subscription.
2222
- You can move a certificate bound to a web without deleting the SSL bindings, as long as the certificate is moved with all other resources in the resource group.
2323
- App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions.
2424

0 commit comments

Comments
 (0)