small changes to docs for versioning and instructions

Author: microsoftshawarma

articles/trusted-signing/faq.yml

@@ -47,6 +47,12 @@ sections:
       - question: What if I fail identity validation?
         answer: | 
           If more documentation is required for identity validation, you're asked to provide those documents on the Azure portal. Otherwise, we recommend checking for an email sent to the listed address for email validation. However, if your organization fails identity validation we can't onboard you to Trusted Signing. We recommend you delete your Trusted Signing account so you don't get billed for unused resources.
+      - question: What is the cost of using Trusted Signing?
+        answer: | 
+          For the beginning of Public Preview until June 2024 Trusted Signing will be free. You will still be prompted to select a Basic or Premium SKU when you create your account and we will throttle signing requests.
+      - question: What are my support options when onboarding to Trusted Signing?
+        answer: | 
+          If you are a managed customer on Azure and have a support plan you can create a support ticket with the service on the Azure portal to be assisted by Azure customer support. Otherwise, we recommend you go to Microsoft Q&A or StackOverflow under the tag Trusted-Signing to ask questions.  
   - name: Certificate Profiles
     questions:
       - question: What if my Trusted Signing subject name is different than my old cert and my MSIX's package name is now different? 

articles/trusted-signing/how-to-signing-integrations.md

@@ -66,7 +66,7 @@ The components that SignTool.exe uses to interface with Trusted Signing require
 
 ### Download and install Trusted Signing Dlib package
 Complete these steps to download and install the Trusted Signing Dlib package (.ZIP):
-1.	Download the [Trusted Signing Dlib package](https://www.nuget.org/packages/Azure.CodeSigning.Client). 
+1.	Download the [Trusted Signing Dlib package](https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client). 
 
 2.	Extract the Trusted Signing Dlib zip content and install it onto your signing node in a directory of your choice. You’re required to install it onto the node you’ll be signing files from with SignTool.exe.
 
@@ -113,11 +113,11 @@ Trusted Signing certificates have a 3-day validity, so timestamping is critical
 ## Use other signing integrations with Trusted Signing 
 This section explains how to set up other not [SignTool](#set-up-signtool-with-trusted-signing) signing integrations with Trusting Signing.
 
-* GitHub Action – To use the GitHub action for Trusted Signing, visit [Azure Code Signing · Actions · GitHub Marketplace](https://github.com/marketplace/actions/azure-code-signing) and follow the instructions to set up and use GitHub action.
+* GitHub Action – To use the GitHub action for Trusted Signing, visit [Trusted Signing · Actions · GitHub Marketplace](https://github.com/azure/trusted-signing-action) and follow the instructions to set up and use GitHub action.
 
-* ADO Task – To use the Trusted Signing AzureDevOps task, visit [Azure Code Signing - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.AzureCodeSigning) and follow the instructions for setup.
+* ADO Task – To use the Trusted Signing AzureDevOps task, visit [Trusted Signing - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.TrustedSigning&ssr=false#overview) and follow the instructions for setup.
 
-* PowerShell for Authenticode – To use PowerShell for Trusted Signing, visit [PowerShell Gallery | AzureCodeSigning 0.2.15](https://www.powershellgallery.com/packages/AzureCodeSigning/0.2.15) to install the PowerShell module. 
+* PowerShell for Authenticode – To use PowerShell for Trusted Signing, visit [PowerShell Gallery | Trusted Signing 0.3.8](https://www.powershellgallery.com/packages/TrustedSigning/0.3.8) to install the PowerShell module. 
 
 * Azure PowerShell – App Control for Business CI Policy - App Control for Windows [link to CI policy signing tutorial].
 

articles/trusted-signing/tutorial-assign-roles.md

@@ -31,7 +31,7 @@ Complete the following steps to assign roles in Trusted Signing.
 2.	Select on the **Roles** tab and search "Trusted Signing". You can see in the screenshot below the two custom roles.
 ![Screenshot of Azure portal UI with the Trusted Signing custom RBAC roles.](./media/trusted-signing-rbac-roles.png)
 
-3. To assign these roles, select on the **Add** drop down and select **Add role assignment**. Follow the [Assign roles in Azure](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal?tabs=current) guide to assign the relevant roles to your identities.
+3. To assign these roles, select on the **Add** drop down and select **Add role assignment**. Follow the [Assign roles in Azure](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal?tabs=current) guide to assign the relevant roles to your identities. _Note that you will need at least a Contributor role to create a Trusted Signing account and certificate profile._
 
 ## Related content 
 * [What is Azure role-based access control (RBAC)?](https://docs.microsoft.com/azure/role-based-access-control/overview)