Merge pull request #272076 from mehasharma/meha-publicpreviewedits

Meha publicpreviewedits

Author: v-dirichards

articles/trusted-signing/how-to-cert-revocation.md

@@ -1,15 +1,14 @@
 ---
 title: Revoke a certificate profile in Trusted Signing 
-description: how-to revoke a Trusted Signing certificate from Azure portal. 
+description: How-to revoke a Trusted Signing certificate from Azure portal. 
 author: mehasharma 
 ms.author: mesharm 
-ms.service: azure-code-signing 
+ms.service: trusted-signing 
 ms.topic: how-to 
-ms.date: 03/31/2024 
+ms.date: 04/12/2024 
 ---
 
 
-
 # Revoke a certificate profile in Trusted Signing
 
 Certificate revocation is an act of invalidating a certificate. Once a certificate is successfully revoked, all the files signed with a revoked certificate become invalid from the selected revocation date and time. 
@@ -58,4 +57,4 @@ Complete these steps to revoke a certificate profile from Trusted Signing:
 11.	Once the certificate is successfully revoked:
     - The status is updated for the thumbprint that was revoked.
     - An email is sent to the email addresses provided during Identity Validation. 
-    
+    

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

@@ -3,34 +3,54 @@ title: Access signed transactions in Trusted Signing
 description: How-to access signed transactions in Trusted Signing in Azure portal. 
 author: mehasharma 
 ms.author: mesharm 
-ms.service: azure-code-signing 
+ms.service: trusted-signing 
 ms.topic: how-to 
-ms.date: 04/01/2024 
+ms.date: 04/12/2024 
 ---
 
 # Access signed transactions in Trusted Signing
 
-Review the details of the signing requests executed by Trusted Signing in Azure portal. 
-Currently there are four different options enabled:  
-- Log Analytics workspace  
-- Storage Account  
-- Event Hub  
-- Partner Solution   
+Azure Monitor’s Diagnostic Settings enable you to route platform metrics, resource logs, and the activity log to various destinations. For each Azure resource, you need to configure its own diagnostic setting. Similarly, each Trust Signing account should have its own settings established.
+Currently there are four different options enabled:
+
+- **Log Analytics workspace**: A Log Analytics workspace serves as a distinct environment for log data. Each workspace has its own data repository and configuration. It’s the designated destination for sending your data. If you haven’t already set up a workspace, create one before proceeding. For additional details, refer to the [Log Analytics workspace Overview.](https://learn.microsoft.com/azure/azure-monitor/logs/log-analytics-workspace-overview) 
+- **Storage Account**: An Azure storage account houses all your Azure Storage data objects, including blobs, files, queues, and tables. It offers a unique namespace for your Azure Storage data, accessible globally via HTTP or HTTPS. When setting up your storage account, follow these steps:
+  - Select your Subscription: Choose the appropriate subscription.
+  - Choose a Storage Account: Specify the storage account where you want to store your data.
+  - Azure Storage Lifecycle Policy: Utilize the Azure Storage Lifecycle Policy to manage how long your logs are retained.
+For additional information, refer to the [Storage account Overview](https://learn.microsoft.com/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json)
+- **Event Hub**: Azure Event Hubs is a cloud-native data streaming service that can handle millions of events per second with low latency. It seamlessly streams data from any source to any destination. When configuring it, you can specify the subscription to which the event hub belongs. For additional information, refer to the [Event Hubs Overview](https://learn.microsoft.com/azure/event-hubs/event-hubs-about)
+- **Partner Solution**: You can send platform metrics and logs to certain Azure Monitor partners.
+
+Remember, each setting can have no more than one of each of the destination types. If you need to delete a resource, rename, or move a resource, or migrate it across resource groups or subscriptions, first delete its diagnostic settings.
+
+For more detailed information, you can refer to the official Microsoft documentation on [Diagnostic settings in Azure Monitor](https://learn.microsoft.com/azure/azure-monitor/essentials/diagnostic-settings) and [Creating diagnostic settings in Azure Monitor.](https://learn.microsoft.com/azure/azure-monitor/essentials/create-diagnostic-settings)
 
 Following is an example of how to view signing transactions through storage account.
+
 ## Prerequisites:  
+
 - Ability to create storage accounts in a subscription. (Note: The billing of storage accounts is separate from Trusted Signing resources.)  
 - Sign in to the Azure portal.
 
-## Send signed transactions to storage account 
-Follow the steps to access and send sign transactions to your storage account:  
-1.	Follow this guide to create Storage Accounts, Create a storage account - Azure Storage | Microsoft Learn, in the same region as your trusted signing account (Basic storage account is sufficient)  
-2.	Navigate to your trusted signing account in the Azure portal.
-3.	On the trusted signing account overview page, locate **Diagnostics Settings** under Monitoring section. 
-    1.	Select Diagnostics Settings on the left-side blade and click **+ Add diagnostic setting** link on the left side.
-    2.	From **Diagnostics setting** page, select **Sign Transactions** category and choose ‘Archive to a storage account’ option and select the subscription and Storage account that you newly created or already have. 
-    4.	After selecting subscription & storage account, click **Save**. This action brings you to previous page where it displays list of all diagnostics settings created for this code sign account.  
-    5.	After creating a diagnostic setting, wait for 10-15 mins before the events begin to get ingested to the newly created storage account.  
-    6.	Navigate to the storage account created in step 1. In this example, we will use storage account **storagetestneu1**.  
-    7.	From storage account resource, navigate to **Containers** under **Data storage**. 
-    8.	From the list, select container named **insights-logs-signtransactions** and navigate to the date and time you're looking to download the log.    
+## Send signing transactions to storage account
+
+Follow the steps to access and send signing transactions to your storage account:  
+
+1. Follow this guide to create Storage accounts, [Create a storage account - Azure Storage | Microsoft Learn](https://learn.microsoft.com/azure/storage/common/storage-account-create?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json), in the same region as your trusted signing account (Basic storage account is sufficient).
+2. Navigate to your trusted signing account in the Azure portal.
+3. On the trusted signing account overview page, locate **Diagnostics Settings** under Monitoring section.
+
+:::image type="content" source="media/trusted-signing-diagnostic-settings.png" alt-text="Screenshot of trusted-signing-diagnostic-settings." lightbox="media/trusted-signing-diagnostic-settings.png":::
+
+4. Select Diagnostics Settings on the left-side blade and click **+ Add diagnostic setting** link on the left side.
+5. From **Diagnostics setting** page, select **Sign Transactions** category and choose ‘Archive to a storage account’ option and select the subscription and Storage account that you newly created or already have.
+
+:::image type="content" source="media/trusted-signing-select-storage-account-subscription.png" alt-text="Screenshot of trusted-signing-select-storage-account-subscription." lightbox="media/trusted-signing-select-storage-account-subscription.png":::
+
+
+6. After selecting subscription & storage account, click **Save**. This action brings you to previous page where it displays list of all diagnostics settings created for this code sign account.  
+7. After creating a diagnostic setting, wait for 10-15 mins before the events begin to get ingested to the newly created storage account.  
+Navigate to the storage account created previously.  
+8. From storage account resource, navigate to **Containers** under **Data storage**.
+9. From the list, select container named **insights-logs-signtransactions** and navigate to the date and time you're looking to download the log.