Skip to content

Commit 3275f76

Browse files
authored
Merge pull request #276538 from mehasharma/faq-vetting
add changes to faq
2 parents 4cc4812 + 0926d8f commit 3275f76

File tree

4 files changed

+146
-57
lines changed

4 files changed

+146
-57
lines changed

articles/trusted-signing/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@
2222
href: how-to-cert-revocation.md
2323
- name: Renew Trusted Signing identity validation
2424
href: how-to-renew-identity-validation.md
25+
- name: Change Pricing Tier
26+
href: how-to-change-sku.md
2527
- name: Tutorials
2628
items:
2729
- name: Assign roles in Trusted Signing

articles/trusted-signing/faq.yml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,8 @@ sections:
3838
3939
- question: What if I fail identity validation?
4040
answer: |
41-
- Ensure you did not miss an email verification link sent to the primary email address shared during Identity Validation request creation. The link expires in 7 days, so you need to create a new Identity Validation request.
41+
- Organizations with a year founded date, less than 3 years cannot be onboarded at the moment and will fail Identity Validation.
42+
- For Organizations, with year founded date more than 3 years: Ensure you did not miss an email verification link sent to the primary email address shared during Identity Validation request creation. The link expires in 7 days, so you need to create a new Identity Validation request.
4243
- If the failure is not to due to missed email verification; then the Microsoft validation team wasn't able to make a determination about your request based on the information that you provided (even after you provided more documentation when we request it), we can't onboard you to Trusted Signing. In this scenario, we recommend that you delete your Trusted Signing account so that you aren't billed for unused resources.
4344
- question: What if I need assistance with Identity Validation?
4445
answer: |
@@ -70,6 +71,7 @@ sections:
7071
- question: What do I do if my identity validation expired?
7172
answer: |
7273
Failure to renew identity validation before the expiration date stops certificate renewal, effectively halting the signing process associated with those specific certificate profiles. To continue signing by using the Trusted Signing service, you need to create another identity validation and associate it with the certificate profiles.
74+
7375
- name: Signing
7476
questions:
7577
- question: What types of files can be signed with Trusted Signing?
@@ -156,7 +158,13 @@ sections:
156158
| Error code (-2147024885/0x8007000b) | For MSIX signing, indicates that the publisher in the manifest file doesn't match the certificate subject. Check the publisher that's listed in the manifest file. |
157159
| No error codes, SignTool silently fails | Ensure that the relevant .NET runtime version is installed. |
158160
| Azure.Identity.CredentialUnavailableException | You might see this error in [environments outside Azure](https://github.com/Azure/azure-sdk-for-net/issues/29471). If you are working outside of Azure, we recommend that you add "exclude ManagedIdentity". |
159-
161+
- name: Cost Management and Billing
162+
questions:
163+
- question: How do I view usage costs and billing information for Trusted Signing resources?
164+
answer: |
165+
Review resource usage costs under your selected Subscription > Cost Management and for further details follow [Cost Management](https://learn.microsoft.com/azure/cost-management-billing/costs/).
166+
Review billing information under your selected Subscription > Billing and for further details follow [Billing](https://learn.microsoft.com/azure/cost-management-billing/manage/).
167+
160168
- name: Unenroll from the Trusted Signing service
161169
questions:
162170
- question: How do I unenroll from Trusted Signing?
Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: Change SKU selection
3+
description: How-to change your SKU for Trusted Signing account.
4+
author: mehasharma
5+
ms.author: mesharm
6+
ms.service: trusted-signing
7+
ms.topic: how-to
8+
ms.date: 05/30/2024
9+
---
10+
11+
12+
# Select or change Trusted Signing SKU (Pricing tier)
13+
14+
Trusted Signing provides a choice between two pricing tiers: Basic and Premium. Both tiers are tailored to offer the service at an optimal cost, suitable for any signing scenario.
15+
16+
## SKU (Pricing tier) overview
17+
18+
Each pricing tier provides varying options for the number of certificate profile types available and the monthly allocation of signatures.
19+
20+
| Subscription level | Basic | Premium |
21+
| :------------------- | :------------------- |:---------------|
22+
| Price(monthly) | **$9.99 / account** | **$99.99 / account** |
23+
| Quota (signatures / month) | 5,000 | 100,000 |
24+
| Price after quota is reached | $0.005 / signature | $0.005 / signature |
25+
| Certificate Profiles | 1 of each available type | 10 of each available type |
26+
| Public-Trust Signing | Yes | Yes |
27+
| Private-Trust Signing | Yes | Yes |
28+
29+
**Note**: The pricing tier is also referred to as the SKU.
30+
31+
32+
## Change SKU
33+
34+
You can change the SKU for a Trusted Signing account at any time by upgrading to Premium or downgrading to Basic. This change can be done from both the Azure portal and from Azure CLI.
35+
36+
- SKU updates are effective from next billing cycle.
37+
- SKU limitations for updated SKU are enforced after the update is successful.
38+
- Downgrade to Basic:
39+
- The Basic SKU allows only one certificate profile of each type. For example, if you have two certificate profiles of type Public Trust, you need to delete any one profile to be eligible to downgrade. Same applies for other certificate profile types as well.
40+
- Upgrade to Premium:
41+
- There are no limitations when you upgrade to the Premium SKU from Basic SKU.
42+
- After changing the SKU, you're required to manually refresh the Account Overview section to see the updated SKU under SKU (Pricing tier). (This limitation is known, and being actively worked on to resolve).
43+
44+
# [Azure portal](#tab/sku-portal)
45+
46+
To change the SKU (Pricing tier) from the Azure portal, follow these steps:
47+
48+
1. Sign in to the Azure portal.
49+
2. Navigate to your Trusting Signing account in the Azure portal.
50+
3. On the account Overview page, locate the current **SKU (Pricing tier)**.
51+
4. Select the current SKU selection hyperlink. Your current selection is highlighted in the "choose pricing tier" window.
52+
5. Select the SKU you want to update to (for example, downgrade to Basic or upgrade to Premium) and select **Update**.
53+
54+
55+
# [Azure CLI](#tab/sku-cli)
56+
57+
To change the SKU with Azure CLI, use the following command:
58+
59+
```
60+
az trustedsigning update -n MyAccount -g MyResourceGroup --sku Premium
61+
```
62+
---
63+
64+
## Cost Management and Billing
65+
66+
**Cost Management**
67+
68+
View and estimate the cost of your Trusted Signing resource usage.
69+
1. In the Azure portal, search **Subscriptions**.
70+
2. Select the **Subscription**, where you have created Trusted Signing resources.
71+
3. Select Cost Management from the menu on the left. Learn more about using [Cost Management](https://learn.microsoft.com/azure/cost-management-billing/costs/).
72+
4. For Trusted Signing, you can see costs associated to your Trusted Signing account.
73+
74+
**Billing**
75+
76+
View Invoice for Trusted Signing service.
77+
1. In the Azure portal, search **Subscriptions**.
78+
2. Select the **Subscription**, where you have created Trusted Signing resources.
79+
3. Select Billing from the menu on the left. Learn more about [Billing](https://learn.microsoft.com/azure/cost-management-billing/manage/).

0 commit comments

Comments
 (0)