Skip to content

Commit fa83ece

Browse files
Merge pull request #272792 from microsoftshawarma/main
fixing faq
2 parents 9ad81a4 + 396e055 commit fa83ece

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/trusted-signing/faq.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,11 +49,11 @@ sections:
4949
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.
5050
- question: What is the cost of using Trusted Signing?
5151
answer: |
52-
For Public Preview Trusted Signing is free for now. You'll still be prompted to select a Basic or Premium SKU when you create your account and we throttle signing requests.
52+
For Public Preview Trusted Signing is free for now. You'll still be prompted to select a Basic or Premium SKU when you create your account.
5353
- question: What are my support options when onboarding to Trusted Signing?
5454
answer: |
5555
If you're a managed customer on Azure, and have a support plan you can create a support ticket with the service on the Azure portal and 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.
56-
- name: Certificate Profiles
56+
- name: Certificate Profiles and Identity Validation
5757
questions:
5858
- question: What if my Trusted Signing subject name is different than my old cert and my MSIX's package name is now different?
5959
answer: |

articles/trusted-signing/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
### YamlMime:Landing
22

33
title: Trusted Signing # < 60 chars
4-
summary: Trusted Signing is a Microsoft fully managed end-to-end code signing solution for third party developers # < 160 chars
4+
summary: Trusted Signing is a Microsoft fully managed end-to-end signing solution for third party developers # < 160 chars
55

66
metadata:
77
title: Trusted Signing documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
8-
description: Trusted Signing is a Microsoft fully managed end-to-end code signing solution for third party developers. The service is currently in a preview state. # Required; article description that is displayed in search results. < 160 chars.
8+
description: Trusted Signing is a Microsoft fully managed end-to-end signing solution for third party developers. The service is currently in a preview state. # Required; article description that is displayed in search results. < 160 chars.
99
ms.service: azure-code-signing #Required; use either service or product per approved list.
1010
ms.topic: landing-page # Required
1111
author: microsoftshawarma #Required; your GitHub user alias, with correct capitalization.

0 commit comments

Comments
 (0)