Fix remaining audit items: SDK versions, archived links, style

- Update Java SDK versions: certificates 4.1.3→4.8.6, identity 1.2.0→1.18.2
- Replace archived /archive/blogs/kv/ links with current docs equivalents
- Update toc.yml blog link to Tech Community
- Modernize certificate-scenarios.md: remove KV abbreviations, fix informal
  style, replace 'we' usage, use contractions, proper [!NOTE] admonition,
  fix numbered list style, improve grammar throughout
- Add ai-usage: ai-assisted to certificate-scenarios.md

Co-authored-by: Copilot <[email protected]>

Author: msmbaldwin

articles/key-vault/certificates/about-certificates.md

@@ -130,7 +130,7 @@ Before a certificate issuer can be created in a key vault, an administrator must
 
 1. Create requester credentials for Key Vault to enroll (and renew) TLS/SSL certificates. This step provides the configuration for creating an issuer object of the provider in the key vault.  
 
-For more information on creating issuer objects from the certificate portal, see the [Key Vault Team Blog](/archive/blogs/kv/manage-certificates-via-azure-key-vault).  
+For more information on creating issuer objects from the certificate portal, see [Integrating Key Vault with certificate authorities](./how-to-integrate-certificate-authority.md).  
 
 Key Vault allows for the creation of multiple issuer objects with different issuer provider configurations. After an issuer object is created, its name can be referenced in one or multiple certificate policies. Referencing the issuer object instructs Key Vault to use the configuration as specified in the issuer object when it's requesting the X.509 certificate from the CA provider during certificate creation and renewal.  
 

articles/key-vault/certificates/certificate-scenarios.md

@@ -10,16 +10,17 @@ ms.date: 04/10/2026
 
 ms.author: mbaldwin
 ms.custom: sfi-image-nochange
+ai-usage: ai-assisted
 ---
 
 # Get started with Key Vault certificates
-This guideline helps you get started with certificate management in Key Vault.
 
-List of scenarios covered here:
+This article helps you get started with certificate management in Key Vault. It covers the following scenarios:
+
 - Creating your first Key Vault certificate
-- Creating a certificate with a Certificate Authority that is partnered with Key Vault
-- Creating a certificate with a Certificate Authority that is not partnered with Key Vault
-- Import a certificate
+- Creating a certificate with a certificate authority (CA) that is partnered with Key Vault
+- Creating a certificate with a CA that isn't partnered with Key Vault
+- Importing a certificate
 
 ## Certificates are complex objects
 Certificates are composed of three interrelated resources linked together as a Key Vault certificate; certificate metadata, a key, and a secret.
@@ -29,28 +30,29 @@ Certificates are composed of three interrelated resources linked together as a K
 
 
 ## Creating your first Key Vault certificate  
- Before a certificate can be created in a Key Vault (KV), prerequisite steps 1 and 2 must be successfully accomplished and a key vault must exist for this user / organization.  
+Before a certificate can be created in Key Vault, the following prerequisite steps must be completed and a key vault must exist for this user or organization.  
 
-**Step 1:** Certificate Authority (CA) Providers  
--   On-boarding as the IT Admin, PKI Admin or anyone managing accounts with CAs, for a given company (for example, Contoso) is a prerequisite to using Key Vault certificates.  
-    The following CAs are the current partnered providers with Key Vault. For more information, see [Partnered CA Providers](./create-certificate.md#partnered-ca-providers).   
+**Step 1:** Certificate authority (CA) providers  
+-   Onboarding as the IT admin, PKI admin, or anyone managing accounts with CAs, for a given company (for example, Contoso) is a prerequisite to using Key Vault certificates.  
+    The following CAs are the current partnered providers with Key Vault. For more information, see [Partnered CA providers](./create-certificate.md#partnered-ca-providers).   
     -   DigiCert - Key Vault offers OV TLS/SSL certificates with DigiCert.  
     -   GlobalSign - Key Vault offers OV TLS/SSL certificates with GlobalSign.  
 
-**Step 2:** An account admin for a CA provider creates credentials to be used by Key Vault to enroll, renew, and use TLS/SSL certificates via Key Vault.
+**Step 2:** An account admin for a CA provider creates credentials to be used by Key Vault to enroll, renew, and use TLS/SSL certificates.
 
 **Step 3a:** A Contoso admin, along with a Contoso employee (Key Vault user) who owns certificates, depending on the CA, can get a certificate from the admin or directly from the account with the CA.  
 
-- Begin an add credential operation to a key vault by [setting a certificate issuer](/rest/api/keyvault/certificates/set-certificate-issuer/set-certificate-issuer) resource. A certificate issuer is an entity represented in Azure Key Vault (KV) as a CertificateIssuer resource. It is used to provide information about the source of a KV certificate; issuer name, provider, credentials, and other administrative details.
+- Begin an add credential operation to a key vault by [setting a certificate issuer](/rest/api/keyvault/certificates/set-certificate-issuer/set-certificate-issuer) resource. A certificate issuer is an entity represented in Azure Key Vault as a CertificateIssuer resource. It provides information about the source of a Key Vault certificate: issuer name, provider, credentials, and other administrative details.
   - For example, MyDigiCertIssuer  
     -   Provider  
     -   Credentials – CA account credentials. Each CA has its own specific data.  
 
-    For more information on creating accounts with CA Providers, see the related post on the [Key Vault blog](/archive/blogs/kv/manage-certificates-via-azure-key-vault).  
+    For more information on creating accounts with CA Providers, see [Integrating Key Vault with certificate authorities](./how-to-integrate-certificate-authority.md).  
 
-**Step 3b:** Set up [certificate contacts](/rest/api/keyvault/certificates/set-certificate-contacts/set-certificate-contacts) for notifications. This is the contact for the Key Vault user. Key Vault does not enforce this step.  
+**Step 3b:** Set up [certificate contacts](/rest/api/keyvault/certificates/set-certificate-contacts/set-certificate-contacts) for notifications. This is the contact for the Key Vault user. Key Vault doesn't enforce this step.  
 
-Note - This process, through **Step 3b**, is a onetime operation.  
+> [!NOTE]
+> This process, through **Step 3b**, is a onetime operation.  
 
 ## Creating a certificate with a CA partnered with Key Vault
 
@@ -78,25 +80,25 @@ Note - This process, through **Step 3b**, is a onetime operation.
       -   Because of the delay to create, a cancel operation can be initiated. The cancel may or may not be effective.  
 
 ### Network security and access policies associated with integrated CA
-Key Vault service sends requests to CA (outbound traffic). Therefore, it’s fully compatible with firewall enabled key vaults. The Key Vault does not share access policies with the CA. The CA must be configured to accept signing requests independently. [Guide on integrating trusted CA](./how-to-integrate-certificate-authority.md)
+Key Vault service sends requests to the CA (outbound traffic). Therefore, it's fully compatible with firewall-enabled key vaults. Key Vault doesn't share access policies with the CA. The CA must be configured to accept signing requests independently. For more information, see [Integrating Key Vault with certificate authorities](./how-to-integrate-certificate-authority.md).
 
 ## Import a certificate  
- Alternatively – a cert can be imported into Key Vault – PFX or PEM.  
+Alternatively, you can import a certificate into Key Vault in PFX or PEM format.  
 
- Import certificate – requires a PEM or PFX to be on disk and have a private key. 
--   You must specify: vault name and certificate name (policy is optional)
+Importing a certificate requires a PEM or PFX file on disk that contains a private key. 
+-   You must specify the vault name and certificate name (policy is optional).
 
--   PEM / PFX files contains attributes that KV can parse and use to populate the certificate policy. If a certificate policy is already specified, KV will try to match data from PFX  / PEM file.  
+-   PEM and PFX files contain attributes that Key Vault can parse and use to populate the certificate policy. If a certificate policy is already specified, Key Vault tries to match data from the PFX or PEM file.  
 
--   Once the import is final, subsequent operations will use the new policy (new versions).  
+-   Once the import is final, subsequent operations use the new policy (new versions).  
 
--   If there are no further operations, the first thing the Key Vault does is send an expiration notice. 
+-   If there are no further operations, the first thing Key Vault does is send an expiration notice. 
 
--   Also, the user can edit the policy, which is functional at the time of import but contains defaults where no information was specified at import. For example, no issuer info  
+-   The user can also edit the policy, which is functional at the time of import but contains defaults where no information was specified at import. For example, no issuer info.  
 
 ### Formats of import we support
-Azure Key Vault supports .pem and .pfx certificate files for importing Certificates into Key vault.
-We support the following type of Import for PEM file format. A single PEM encoded certificate along with a PKCS#8 encoded, unencrypted key which has the following format:
+Azure Key Vault supports .pem and .pfx certificate files for importing certificates into a key vault.
+The following import format is supported for PEM files: a single PEM-encoded certificate along with a PKCS#8-encoded, unencrypted key in the following format:
 
 -----BEGIN CERTIFICATE-----
 
@@ -106,36 +108,36 @@ We support the following type of Import for PEM file format. A single PEM encode
 
 -----END PRIVATE KEY-----
 
-When you are importing the certificate, you need to ensure that the key is included in the file itself. If you have the private key separately in a different format, you would need to combine the key with the certificate. Some certificate authorities provide certificates in different formats, therefore before importing the certificate, make sure that they are either in .pem or .pfx format. 
+When you import a certificate, ensure that the key is included in the file itself. If you have the private key separately in a different format, you need to combine the key with the certificate. Some certificate authorities provide certificates in different formats, so before importing the certificate, make sure that it's in .pem or .pfx format. 
 
 
 >[!NOTE]
 >Ensure that no other meta data is present in the certificate file and that the private key not showing as encrypted.
 
 ### Formats of merge CSR we support
 
-Azure Key Vault supports PKCS#8 encoded certificate with below headers:
+Azure Key Vault supports PKCS#8 encoded certificates with the following headers:
 
 -----BEGIN CERTIFICATE-----
 
 -----END CERTIFICATE-----
 
 >[!NOTE]
-> P7B (PKCS#7) signed certificates chain, commonly used by Certificate Authorities (CAs), is supported as long as is base64 encoded. You may use [certutil -encode](/windows-server/administration/windows-commands/certutil#-encode) to convert to supported format.
+> P7B (PKCS#7) signed certificate chains, commonly used by certificate authorities (CAs), are supported as long as they're base64-encoded. You can use [certutil -encode](/windows-server/administration/windows-commands/certutil#-encode) to convert to a supported format.
 
 ## Creating a certificate with a CA not partnered with Key Vault  
- This method allows working with other CAs than Key Vault's partnered providers, meaning your organization can work with a CA of its choice.  
+This method allows working with CAs other than Key Vault's partnered providers, meaning your organization can work with a CA of its choice.  
 
 ![Create a certificate with your own certificate authority](../media/certificate-authority-1.png)  
 
  The following step descriptions correspond to the green lettered steps in the preceding diagram.  
 
-  (1) - In the diagram above, your application is creating a certificate, which internally begins by creating a key in your key vault.  
+  1. In the diagram, your application is creating a certificate, which internally begins by creating a key in your key vault.  
 
-  (2) - Key Vault returns to your application a Certificate Signing Request (CSR).  
+  1. Key Vault returns a Certificate Signing Request (CSR) to your application.  
 
-  (3) - Your application passes the CSR to your chosen CA.  
+  1. Your application passes the CSR to your chosen CA.  
 
-  (4) - Your chosen CA responds with an X509 Certificate.  
+  1. Your chosen CA responds with an X.509 certificate.  
 
-  (5) - Your application completes the new certificate creation with a merger of the X509 Certificate from your CA.
+  1. Your application completes the new certificate creation with a merger of the X.509 certificate from your CA.

articles/key-vault/certificates/quick-create-java.md

@@ -104,13 +104,13 @@ Open the *pom.xml* file in your text editor. Add the following dependency elemen
     <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-security-keyvault-certificates</artifactId>
-      <version>4.1.3</version>
+      <version>4.8.6</version>
     </dependency>
 
     <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-identity</artifactId>
-      <version>1.2.0</version>
+      <version>1.18.2</version>
     </dependency>
 ```
 

articles/key-vault/certificates/toc.yml

@@ -113,6 +113,6 @@ items:
   - name: Service updates
     href: https://azure.microsoft.com/updates/?product=key-vault
   - name: Blog
-    href: /archive/blogs/kv/
+    href: https://techcommunity.microsoft.com/tag/azure-key-vault
   - name: Product Feedback
     href: https://feedback.azure.com/d365community/forum/285c5ae0-f524-ec11-b6e6-000d3a4f0da0