Merge pull request #279498 from greg-lindsay/appgw-gh-issues

Appgw gh issues

Author: prmerger-automator[bot]

articles/application-gateway/certificates-for-backend-authentication.md

@@ -6,7 +6,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 06/27/2024
 ms.author: greglin
 ---
 
@@ -32,40 +32,40 @@ From your TLS/SSL certificate, export the public key .cer file (not the private
 
 1. To obtain a .cer file from the certificate, open **Manage user certificates**. Locate the certificate, typically in 'Certificates - Current User\Personal\Certificates', and right-click. Click **All Tasks**, and then click **Export**. This opens the **Certificate Export Wizard**. If you want to open Certificate Manager in current user scope using PowerShell, you type *certmgr* in the console window.
 
-> [!NOTE]
-> If you can't find the certificate under Current User\Personal\Certificates, you may have accidentally opened "Certificates - Local Computer", rather than "Certificates - Current User"). 
+   > [!NOTE]
+   > If you can't find the certificate under Current User\Personal\Certificates, you may have accidentally opened "Certificates - Local Computer", rather than "Certificates - Current User"). 
 
    ![Screenshot shows the Certificate Manager with Certificates selected and a contextual menu with All tasks, then Export selected.](./media/certificates-for-backend-authentication/export.png)
 
-1. In the Wizard, click **Next**.
+2. In the Wizard, click **Next**.
 
    ![Export certificate](./media/certificates-for-backend-authentication/exportwizard.png)
 
-1. Select **No, do not export the private key**, and then click **Next**.
+3. Select **No, do not export the private key**, and then click **Next**.
 
    ![Do not export the private key](./media/certificates-for-backend-authentication/notprivatekey.png)
 
-1. On the **Export File Format** page, select **Base-64 encoded X.509 (.CER).**, and then click **Next**.
+4. On the **Export File Format** page, select **Base-64 encoded X.509 (.CER).**, and then click **Next**.
 
    ![Base-64 encoded](./media/certificates-for-backend-authentication/base64.png)
 
-1. For **File to Export**, **Browse** to the location to which you want to export the certificate. For **File name**, name the certificate file. Then, click **Next**.
+5. For **File to Export**, **Browse** to the location to which you want to export the certificate. For **File name**, name the certificate file. Then, click **Next**.
 
    ![Screenshot shows the Certificate Export Wizard where you specify a file to export.](./media/certificates-for-backend-authentication/browse.png)
 
-1. Click **Finish** to export the certificate.
+6. Click **Finish** to export the certificate.
 
    ![Screenshot shows the Certificate Export Wizard after you complete the file export.](./media/certificates-for-backend-authentication/finish-screen.png)
 
-1. Your certificate is successfully exported.
+7. Your certificate is successfully exported.
 
    ![Screenshot shows the Certificate Export Wizard with a success message.](./media/certificates-for-backend-authentication/success.png)
 
    The exported certificate looks similar to this:
 
    ![Screenshot shows a certificate symbol.](./media/certificates-for-backend-authentication/exported.png)
 
-1. If you open the exported certificate using Notepad, you see something similar to this example. The section in blue contains the information that is uploaded to application gateway. If you open your certificate with Notepad and it doesn't look similar to this, typically this means you didn't export it using the Base-64 encoded X.509(.CER) format. Additionally, if you want to use a different text editor, understand that some editors can introduce unintended formatting in the background. This can create problems when uploaded the text from this certificate to Azure.
+8. If you open the exported certificate using Notepad, you see something similar to this example. The section in blue contains the information that is uploaded to application gateway. If you open your certificate with Notepad and it doesn't look similar to this, typically this means you didn't export it using the Base-64 encoded X.509(.CER) format. Additionally, if you want to use a different text editor, understand that some editors can introduce unintended formatting in the background. This can create problems when uploaded the text from this certificate to Azure.
 
    ![Open with Notepad](./media/certificates-for-backend-authentication/format.png)
 

articles/application-gateway/classic-to-resource-manager.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: how-to
-ms.date: 02/10/2022
+ms.date: 06/27/2024
 ms.author: greglin
 ---
 
@@ -34,6 +34,9 @@ For more information on how to set up an Application Gateway resource after VNet
 
 The word "classic" in classic networking service refers to networking resources managed by Azure Service Manager (ASM). Azure Service Manager (ASM) is the old control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.
 
+> [!NOTE]
+> To view all the classic resources in your subscription, Open the **All Resources** blade and look for a **(Classic)** suffix after the resource name.
+
 ### What is Azure Resource Manager?
 
 Azure Resource Manager is the latest control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.