Skip to content

Commit d255359

Browse files
added new alias
1 parent f5d2608 commit d255359

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ You can check the expiration date of your Identity Validation on the Identity Va
1515

1616
>[!Note]
1717
>Failure to renew Identity Validation before the expiration date will stop certificate renewal, effectively halting the signing process associated with those specific certificate profiles.
18-
>EKU does not change when renew Identity Validation.
18+
>EKU does not change when you renew Identity Validation.
1919
2020
1. Navigate to your Trusted Signing account in the [Azure portal](https://portal.azure.com/).
2121
2. Confirm you have the **Trusted Signing Identity Verifier role**.
2222
- To learn more about Role Based Access management (RBAC) access management, see [Assigning roles in Trusted Signing](tutorial-assign-roles.md).
2323
3. From either the Trusted Signing account overview page or from Objects, select **Identity Validation**.
2424
4. Select the Identity Validation request that needs to be renewed. Select **Renew** on the top.
2525

26-
:::image type="content" source="media/trusted-signing-renew-identity-validation.png" alt-text="Screenshot of trusted-signing-renew-identity-validation.png." lightbox="media/trusted-signing-renew-identity-validation.png":::
26+
:::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":::
2727

2828
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.
2929
- To learn more about creating new Identity Validation, see [Quickstart](quickstart.md).

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Access signed transactions in Trusted Signing
33
description: Learn how to access signed transactions in Trusted Signing in the Azure portal.
4-
author: mehasharma
4+
author: meha
55
ms.author: mesharm
66
ms.service: trusted-signing
77
ms.topic: how-to
@@ -49,22 +49,22 @@ To complete the steps in this article, you need:
4949
To access and send signing transactions to your storage account: 
5050

5151
1. In the Azure portal, go to your Trusted Signing account.
52-
1. On the Trusted Signing account **Overview** pane, in the resource menu under **Monitoring**, select **Diagnostic settings**.
53-
1. On the **Diagnostic settings** pane, select **+ Add diagnostic setting**.
52+
2. On the Trusted Signing account **Overview** pane, in the resource menu under **Monitoring**, select **Diagnostic settings**.
53+
3. On the **Diagnostic settings** pane, select **+ Add diagnostic setting**.
5454

5555
:::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":::
5656

5757
1. On the **Diagnostic setting** pane:
5858

5959
1. Enter a name for the diagnostic setting.
60-
1. Under **Logs** > **Categories**, select the **Sign Transactions** checkbox.
61-
1. Under **Destination details**, select the **Archive to a storage account** checkbox.
62-
1. Select the subscription and storage account that you want to use.
60+
2. Under **Logs** > **Categories**, select the **Sign Transactions** checkbox.
61+
3. Under **Destination details**, select the **Archive to a storage account** checkbox.
62+
4. Select the subscription and storage account that you want to use.
6363

6464
:::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":::
6565

66-
1. Select **Save**. A pane displays a list of all diagnostic settings that were created for this code signing account. 
67-
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. 
68-
1. Go to the storage account. 
69-
1. In your storage account resource menu under **Data storage**, go to **Containers**.
70-
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.
66+
2. Select **Save**. A pane displays a list of all diagnostic settings that were created for this code signing account. 
67+
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. 
68+
4. Go to the storage account. 
69+
5. In your storage account resource menu under **Data storage**, go to **Containers**.
70+
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.

0 commit comments

Comments
 (0)