Merge pull request #288277 from TacoTechSharma/changename

added new alias

Author: Jill Grant

articles/trusted-signing/how-to-renew-identity-validation.md

@@ -1,38 +1,35 @@
 ---
-title: Renew a Trusted Signing identity validation
-description: Learn how to renew a Trusted Signing identity validation. 
-author: mehasharma 
+title: Renew Trusted Signing Identity Validation
+description: How-to rerenew a Trusted Signing Identity Validation. 
+author: TacoTechSharma
 ms.author: mesharm 
 ms.service: trusted-signing 
 ms.topic: how-to 
 ms.date: 04/12/2024 
 ---
 
-# Renew a Trusted Signing identity validation
+# Renew Trusted Signing Identity Validation 
 
-On the **Identity validation** pane, you can check the expiration date of your identity validation. You can renew your Trusted Signing identity validation 60 days before the expiration date. A reminder notification to renew your identity validation is sent to the primary and secondary email addresses for the Trusted Signing account.
+You can check the expiration date of your Identity Validation on the Identity Validation page. You can renew your Trusted Signing Identity Validation **60 days** before the expiration. A notification is to the primary and secondary email addresses with the reminder to renew your Identity Validation.
+**Identity Validation can only be completed in the Azure portal – it can not be completed with Azure CLI.**
 
-You can complete identity validation *only* in the Azure portal. You can't complete identity validation by using the Azure CLI.
+>[!Note]
+>Failure to renew Identity Validation before the expiration date will stop certificate renewal, effectively halting the signing process associated with those specific certificate profiles.
+>EKU does not change when you renew Identity Validation. 
 
-> [!NOTE]
-> If you don't renew your identity validation before the expiration date, certificate renewal stops. The signing process that's associated with the specific certificate profiles is effectively halted.
+1. Navigate to your Trusted Signing account in the [Azure portal](https://portal.azure.com/).
+2. Confirm you have the **Trusted Signing Identity Verifier role**.
+    - To learn more about Role Based Access management (RBAC) access management, see [Assigning roles in Trusted Signing](tutorial-assign-roles.md).
+3. From either the Trusted Signing account overview page or from Objects, select **Identity Validation**.
+4. Select the Identity Validation request that needs to be renewed. Select **Renew** on the top. 
 
-1. In the [Azure portal](https://portal.azure.com/), go to your Trusted Signing account.
-1. Confirm that you're assigned the Trusted Signing Identity Verifier role.
+:::image type="content" source="media/trusted-signing-renew-identity-validation.png" alt-text="Screenshot of trusted signing renew identity-validation button.png." lightbox="media/trusted-signing-renew-identity-validation.png":::
 
-   To learn about managing access by using role-based access control (RBAC), see [Assign roles in Trusted Signing](tutorial-assign-roles.md).
-1. On the Trusted Signing account **Overview** pane or on the resource menu under **Objects**, select **Identity validations**.
-1. Select the identity validation request that you want to renew. On the menu bar, select **Renew**.
-
-   :::image type="content" source="media/trusted-signing-renew-identity-validation.png" alt-text="Screenshot that shows the Renew option for an identity validation request." lightbox="media/trusted-signing-renew-identity-validation.png":::
-
-   If you encounter validation errors when you renew by selecting the **Renew** button or if the identity validation request is expired, create a new identity validation request. To learn more about creating a new identity validation, see the [Set up Trusted Signing quickstart](quickstart.md).
-1. Verify that after you renew a request, the identity validation status is **Completed**.
-1. To ensure that you can continue to use your existing *metadata.json* file:
-
-   1. On the Trusted Signing account **Overview** pane or on the resource menu under **Objects**, select **Certificate profiles**.
-   1. On the **Certificate profiles** pane, delete the existing certificate profile that's associated with the expiring identity validation.
-   1. Create a new certificate profile that has the same name.
-   1. Select the identity validation.
-
-      When the certificate profile is successfully created, signing resumes without any other configuration changes.
+5. If you encounter validation errors while renewing through the renew button or if Identity Validation is Expired, you need to create a new Identity Validation. 
+    - To learn more about creating new Identity Validation, see [Quickstart](quickstart.md). 
+6. After the Identity Validation status changes to Completed.
+7. To ensure you can continue with your existing metadata.json.
+    - Navigate back to the trusted signing account overview page or from Objects, select **Certificate Profile**.
+    - On the **Certificate Profiles**, delete the existing cert profile associated to the Identity Validation expiring soon:
+    - Create new cert profile with the same name.
+    - Select the Identity Validation from the pull-down. Once the certificate profile is created successfully, signing resumes requiring no configuration changes on your end.

articles/trusted-signing/how-to-sign-history.md

@@ -1,7 +1,7 @@
 ---
 title: Access signed transactions in Trusted Signing 
 description: Learn how to access signed transactions in Trusted Signing in the Azure portal. 
-author: mehasharma 
+author: meha 
 ms.author: mesharm 
 ms.service: trusted-signing 
 ms.topic: how-to 
@@ -49,22 +49,22 @@ To complete the steps in this article, you need:
 To access and send signing transactions to your storage account:  
 
 1. In the Azure portal, go to your Trusted Signing account.
-1. On the Trusted Signing account **Overview** pane, in the resource menu under **Monitoring**, select **Diagnostic settings**.
-1. On the **Diagnostic settings** pane, select **+ Add diagnostic setting**.
+2. On the Trusted Signing account **Overview** pane, in the resource menu under **Monitoring**, select **Diagnostic settings**.
+3. On the **Diagnostic settings** pane, select **+ Add diagnostic setting**.
 
    :::image type="content" source="media/trusted-signing-diagnostic-settings.png" alt-text="Screenshot that shows adding a diagnostic setting." lightbox="media/trusted-signing-diagnostic-settings.png":::
 
 1. On the **Diagnostic setting** pane:
 
    1. Enter a name for the diagnostic setting.
-   1. Under **Logs** > **Categories**, select the **Sign Transactions** checkbox.
-   1. Under **Destination details**, select the **Archive to a storage account** checkbox.
-   1. Select the subscription and storage account that you want to use.
+   2. Under **Logs** > **Categories**, select the **Sign Transactions** checkbox.
+   3. Under **Destination details**, select the **Archive to a storage account** checkbox.
+   4. Select the subscription and storage account that you want to use.
 
    :::image type="content" source="media/trusted-signing-select-storage-account-subscription.png" alt-text="Screenshot that shows configuring a diagnostic setting for a storage account." lightbox="media/trusted-signing-select-storage-account-subscription.png":::
 
-1. Select **Save**. A pane displays a list of all diagnostic settings that were created for this code signing account.  
-1. After you create a diagnostic setting, wait for 10 to 15 minutes for the events to begin to be ingested in the storage account you created.  
-1. Go to the storage account.  
-1. In your storage account resource menu under **Data storage**, go to **Containers**.
-1. In the list, select the container named `insights-logs-signtransactions`. Go to the date and time you want to view to download the log.
+2. Select **Save**. A pane displays a list of all diagnostic settings that were created for this code signing account.  
+3. After you create a diagnostic setting, wait for 10 to 15 minutes for the events to begin to be ingested in the storage account you created.  
+4. Go to the storage account.  
+5. In your storage account resource menu under **Data storage**, go to **Containers**.
+6. In the list, select the container named `insights-logs-signtransactions`. Go to the date and time you want to view to download the log.