docs: Freshness review for premium-deploy-certificates-enterprise-ca.md

- Updated ms.date to 12/31/2025
- Improved clarity and consistency throughout article
- Fixed numbered list formatting (all items use '1.')
- Simplified language (removed 'you should', changed 'navigate' to 'go')
- Improved readability in validation steps

Author: duongau

articles/firewall/premium-deploy-certificates-enterprise-ca.md

@@ -5,7 +5,7 @@ author: duau
 ms.service: azure-firewall
 services: firewall
 ms.topic: how-to
-ms.date: 02/03/2022
+ms.date: 12/31/2025
 ms.author: duau
 ms.custom: sfi-image-nochange
 # Customer intent: "As a network administrator, I want to deploy and configure Enterprise CA certificates for Azure Firewall Premium, so that I can enable TLS inspection and ensure secure traffic management within my organization's network."
@@ -14,54 +14,54 @@ ms.custom: sfi-image-nochange
 # Deploy and configure Enterprise CA certificates for Azure Firewall
 
 
-Azure Firewall Premium includes a TLS inspection feature, which requires a certificate authentication chain. For production deployments, you should use an Enterprise PKI to generate the certificates that you use with Azure Firewall Premium. Use this article to create and manage an Intermediate CA certificate for Azure Firewall Premium.
+Azure Firewall Premium includes a TLS inspection feature, which requires a certificate authentication chain. For production deployments, use an Enterprise PKI to generate the certificates that you use with Azure Firewall Premium. Use this article to create and manage an Intermediate CA certificate for Azure Firewall Premium.
 
 For more information about certificates used by Azure Firewall Premium, see [Azure Firewall Premium certificates](premium-certificates.md).
 
 ## Prerequisites
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin.
 
-To use an Enterprise CA to generate a certificate to use with Azure Firewall Premium, you must have the following resources: 
+To use an Enterprise CA to generate a certificate to use with Azure Firewall Premium, you need the following resources: 
 
 - an Active Directory Forest 
 - an Active Directory Certification Services Root CA with Web Enrollment enabled 
 - an Azure Firewall Premium with Premium tier Firewall Policy 
 - an [Azure Key Vault](premium-certificates.md#azure-key-vault) 
 - a Managed Identity with Read permissions to **Certificates and Secrets** defined in the Key Vault Access Policy 
 
-## Create a new Subordinate Certificate Template
+## Create a new subordinate certificate template
 
 1. Run `certtmpl.msc` to open the Certificate Template Console.
-2. Find the **Subordinate Certification Authority** template in the console.
-3. Right-click on the **Subordinate Certification Authority** template and select **Duplicate Template**.
-4. In the **Properties of New Template** window, go to the **Compatibility** tab and set the appropriate compatibility settings or leave them as default.
-5. Go to the **General** tab, set the **Template Display Name** (for example: `My Subordinate CA`), and adjust the validity period if necessary. Optionally, select the **Publish certificate in Active Directory** checkbox.
-6. In the **Settings** tab, ensure the required users and groups have read and `enroll` permissions.
-7. Navigate to the **Extensions** tab, select **Key Usage**, and select **Edit**.
+1. Find the **Subordinate Certification Authority** template in the console.
+1. Right-click on the **Subordinate Certification Authority** template and select **Duplicate Template**.
+1. In the **Properties of New Template** window, go to the **Compatibility** tab and set the appropriate compatibility settings or leave them as default.
+1. Go to the **General** tab, set the **Template Display Name** (for example: `My Subordinate CA`), and adjust the validity period if necessary. Optionally, select the **Publish certificate in Active Directory** checkbox.
+1. In the **Settings** tab, ensure the required users and groups have read and `enroll` permissions.
+1. Navigate to the **Extensions** tab, select **Key Usage**, and select **Edit**.
    - Ensure that the **Digital signature**, **Certificate signing**, and **CRL signing** checkboxes are selected.
    - Select the **Make this extension critical** checkbox and select **OK**.
 
    :::image type="content" source="media/premium-deploy-certificates-enterprise-ca/certificate-template-key-usage-extension.png" alt-text="Screenshot of certificate template key usage extensions.":::
-8. Select **OK** to save the new certificate template.
-9. Ensure the new template is enabled so it can be used to issue certificates.
+1. Select **OK** to save the new certificate template.
+1. Ensure the new template is enabled so it can be used to issue certificates.
 
 ## Request and export a certificate
 
-1. Access the web enrollment site on the Root CA, usually `https://<servername>/certsrv` and select **Request a Certificate**.
+1. Access the web enrollment site on the Root CA, usually `https://<servername>/certsrv`, and select **Request a Certificate**.
 1. Select **Advanced Certificate Request**.
 1. Select **Create and Submit a Request to this CA**.
 1. Fill out the form using the Subordinate Certification Authority template created in the previous section.
    :::image type="content" source="media/premium-deploy-certificates-enterprise-ca/advanced-certificate-request.png" alt-text="Screenshot of advanced certificate request":::
 1. Submit the request and install the certificate.
-1. Assuming this request is made from a Windows Server using Internet Explorer, open **Internet Options**.
+1. Assuming you make this request from a Windows Server using Internet Explorer, open **Internet Options**.
 1. Navigate to the **Content** tab and select **Certificates**.
 
-1. Select the certificate that was just issued and then select **Export**.
+1. Select the certificate that the CA issued and then select **Export**.
 
 1. Select **Next** to begin the wizard. Select **Yes, export the private key**, and then select **Next**.
 
-1. .pfx file format is selected by default. Uncheck **Include all certificates in the certification path if possible**. If you export the entire certificate chain, the import process to Azure Firewall will fail.
+1. The wizard selects the .pfx file format by default. Uncheck **Include all certificates in the certification path if possible**. If you export the entire certificate chain, the import process to Azure Firewall fails.
 
 1. Assign and confirm a password to protect the key, and then select **Next**.
 
@@ -71,23 +71,23 @@ To use an Enterprise CA to generate a certificate to use with Azure Firewall Pre
 
 ## Add the certificate to a Firewall Policy
 
-1. In the Azure portal, navigate to the Certificates page of your Key Vault, and select **Generate/Import**.
+1. In the Azure portal, go to the Certificates page of your Key Vault, and select **Generate/Import**.
 
-1. Select **Import** as the method of creation, name the certificate, select the exported .pfx file, enter the password, and then select **Create**.
+1. Select **Import** as the creation method. Enter a name for the certificate, select the exported .pfx file, enter the password, and then select **Create**.
 
-1. Navigate to the **TLS Inspection** page of your Firewall policy and select your Managed identity, Key Vault, and certificate.
+1. Go to the **TLS Inspection** page of your Firewall policy and select your Managed identity, Key Vault, and certificate.
 
 1. Select **Save**.
 
 ## Validate TLS inspection
 
-1. Create an Application Rule using TLS inspection to the destination URL or FQDN of your choice.  For example: `*bing.com`.
+1. Create an Application Rule that uses TLS inspection for the destination URL or FQDN of your choice. For example: `*bing.com`.
 
-1. From a domain-joined machine within the Source range of the rule, navigate to your Destination and select the lock symbol next to the address bar in your browser. The certificate should show that it was issued by your Enterprise CA rather than a public CA.
+1. From a domain-joined machine within the source range of the rule, go to your destination and select the lock symbol next to the address bar in your browser. The certificate should show that your Enterprise CA issued it rather than a public CA.
    :::image type="content" source="media/premium-deploy-certificates-enterprise-ca/browser-certificate.png" alt-text="Screenshot showing the browser certificate":::
 1. Show the certificate to display more details, including the certificate path.
    :::image type="content" source="media/premium-deploy-certificates-enterprise-ca/certificate-details.png" alt-text="certificate details":::
-1. In Log Analytics, run the following KQL query to return all requests that have been subject to TLS Inspection:
+1. In Log Analytics, run the following KQL query to return all requests that are subject to TLS Inspection:
    ```
    AzureDiagnostics 
    | where ResourceType == "AZUREFIREWALLS"