Merge pull request #175214 from MicrosoftDocs/master

Merge master to live, 4 AM

Author: ttorble

.openpublishing.redirection.json

@@ -223,6 +223,11 @@
       "redirect_url": "/azure/azure-arc/kubernetes/quickstart-connect-cluster",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/cognitive-services/whats-new-docs.md",
+      "redirect_url": "/azure/cognitive-services/what-are-cognitive-services",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/cognitive-services/Ink-Recognizer/concepts/send-ink-data.md",
       "redirect_url": "/previous-versions/azure/cognitive-services/Ink-Recognizer/concepts/send-ink-data",

CODEOWNERS

@@ -1,26 +1,29 @@
 # Testing the new code owners feature in GitHub. Please contact Cory Fowler if you have questions.
+#
+# Help: https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+# Background: https://github.blog/2017-07-06-introducing-code-owners/
+# NOTE: The people you choose as code owners must have _write_ permissions for the repository. When the code owner is a team, that team must be _visible_ and it must have _write_ permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership.
 
-# Horizontals
-
-## Azure Policy: Samples and Compliance Controls
+# Azure Policy: Samples and Compliance Controls
 /articles/**/policy-reference.md @DCtheGeek
 /articles/**/security-controls-policy.md @DCtheGeek
 /includes/policy/ @DCtheGeek
 
 # Azure Monitor
-/articles/azure-monitor/* @bwren
-/articles/azure-monitor/agents @bwren
-/articles/azure-monitor/alerts @rboucher
-/articles/azure-monitor/app @bwren @lgayhardt
-/articles/azure-monitor/autoscale @rboucher
-/articles/azure-monitor/containers @bwren
-/articles/azure-monitor/essentials @bwren @rboucher
-/articles/azure-monitor/insights @bwren @rboucher @lgayhardt
-/articles/azure-monitor/logs @bwren
-/articles/azure-monitor/visualize @bwren @lgayhardt
-/articles/azure-monitor/vm @bwren
-/articles/advisor @rboucher
-/articles/service-health @rboucher
+articles/azure-monitor/* @bwren
+articles/azure-monitor/agents @bwren
+articles/azure-monitor/alerts @rboucher @abbyMSFT
+articles/azure-monitor/app @bwren 
+articles/azure-monitor/autoscale @rboucher
+articles/azure-monitor/containers @bwren
+articles/azure-monitor/essentials @bwren @rboucher
+articles/azure-monitor/insights @bwren @rboucher 
+articles/azure-monitor/logs @bwren @abbyMSFT
+articles/azure-monitor/visualize @bwren  @rboucher
+articles/azure-monitor/vm @bwren
+articles/advisor @rboucher
+articles/service-health @rboucher
+
 
 # Azure Active Directory
 /articles/active-directory-b2c/ @msmimart @yoelhor
@@ -83,6 +86,6 @@
 /articles/healthcare-apis/ @ginalee-dotcom
 
 # Configuration
-*.json @SyntaxC4 @snoviking @martinekuan
-.acrolinx-config.edn @MonicaRush @martinekuan
-articles/zone-pivot-groups.yml @SyntaxC4 @snoviking @martinekuan
+*.json @SyntaxC4 @snoviking
+.acrolinx-config.edn @MonicaRush 
+articles/zone-pivot-groups.yml @SyntaxC4 @snoviking

articles/active-directory-b2c/extensions-app.md

@@ -36,7 +36,7 @@ If you accidentally deleted the b2c-extensions-app, you have 30 days to recover
 1. Log in to the site as a global administrator for the Azure AD B2C directory that you want to restore the deleted app for. This global administrator must have an email address similar to the following: `username@{yourTenant}.onmicrosoft.com`.
 1. Issue an HTTP GET against the URL `https://graph.microsoft.com/beta/directory/deleteditems/microsoft.graph.application`. This operation will list all of the applications that have been deleted within the past 30 days.
 1. Find the application in the list where the name begins with 'b2c-extensions-app’ and copy its `objectid` property value.
-1. Issue an HTTP POST against the URL `https://graph.microsoft.com/beta/directory/deleteditems/{id}/restore`. Replace the `{OBJECTID}` portion of the URL with the `objectid` from the previous step.
+1. Issue an HTTP POST against the URL `https://graph.microsoft.com/beta/directory/deleteditems/{id}/restore`. Replace the `{id}` portion of the URL with the `objectid` from the previous step.
 
 You should now be able to [see the restored app](#verifying-that-the-extensions-app-is-present) in the Azure portal.
 

articles/active-directory/governance/deploy-access-reviews.md

@@ -190,10 +190,10 @@ The administrative role required to create, manage, or read an Access Review dep
 
 | Resource type| Create and manage Access Reviews (Creators)| Read Access Review results |
 | - | - | -|
-| Group or application| Global Administrator <p>User Administrator| Creators and Security Administrator |
-| Privileged roles in Azure AD| Global Administrator <p>Privileged Role Administrator| Creators <p>Security Reader<p>Security Administrator |
-| Privileged roles in Azure (resources)| Global Administrator<p>User Administrator<p>Resource Owner| Creators |
-| Access package| Global Administrator<p>Creator of Access Package| Global Administrator only |
+| Group or application| Global Administrator <p>User Administrator<p>Identity Governance Administrator<p>Privileged Role Admin (only reviews on for Azure AD role-assignable groups)<p>Group owner ([if enabled by an admin]( create-access-review.md#allow--group-owners-to-create-and-manage-access-reviews-preview))| Global Administrator<p>Global Reader<p>User Administrator<p>Identity Governance Administrator<p>Privileged Role Admin<p>Security Reader<p>Group owner ([if enabled by an admin]( create-access-review.md#allow--group-owners-to-create-and-manage-access-reviews-preview)) |
+|Azure AD roles| Global Administrator <p>Privileged Role Administrator|  Global Administrator<p>Global Reader<p>User Administrator<p>Privileged Role Admin<p> <p>Security Reader |
+| Azure resource roles| Global Administrator<p>Resource Owner| Global Administrator<p>Global Reader<p>User Administrator<p>Privileged Role Admin<p> <p>Security Reader  |
+| Access package| Global Administrator<p>User Administrator<p>Identity Governance Administrator| Global Administrator<p>Global Reader<p>User Administrator<p>Identity Governance Administrator<p> <p>Security Reader  |
 
 For more information, see [Administrator role permissions in Azure Active Directory](../roles/permissions-reference.md).
 

articles/active-directory/verifiable-credentials/TOC.yml

@@ -8,14 +8,12 @@
 - name: Tutorials
   expanded: true
   items:
-  - name: Get started with verifiable credentials
-    href: get-started-verifiable-credentials.md
-  - name: Configure verifiable credentials in your tenant
-    items:
-    - name: 1 - Set up Verifiable Credentials issuer in your own Azure AD
-      href: enable-your-tenant-verifiable-credentials.md
-    - name: 2- Connect your verifiable credentials issuer to your own Azure AD
-      href: issue-verify-verifiable-credentials-your-tenant.md
+  - name: Set up the Verifiable Credentials service
+    href: verifiable-credentials-configure-tenant.md
+  - name: Issue a verifiable credential
+    href: verifiable-credentials-configure-issuer.md
+  - name: Verify a Verifiable Credential
+    href: verifiable-credentials-configure-verifier.md
 - name: Concepts
   expanded: true
   items:
@@ -32,6 +30,8 @@
       href: plan-issuance-solution.md
     - name: Plan your verification solution
       href: plan-verification-solution.md
+  - name: Using the Request Service REST API
+    href: get-started-request-api.md
   - name: How to customize your credentials
     href: credential-design.md
   - name: Manage credential revocation
@@ -49,6 +49,15 @@
     href: https://didvc-issuer-sample.azurewebsites.net/
   - name: Sample Verifier
     href: https://didvc-verifier-sample.azurewebsites.net/
+- name: Reference
+  expanded: true
+  items:
+  - name: What's new
+    href: whats-new.md
+  - name: Issuance API specification
+    href: issuance-request-api.md
+  - name: Presentation API specification
+    href: presentation-request-api.md
 - name: Resources
   expanded: true
   items:

articles/active-directory/verifiable-credentials/decentralized-identifier-overview.md

@@ -82,7 +82,7 @@ Enables real people to use decentralized identities and Verifiable Credentials.
 An API that connects to our ION node to look up and resolve DIDs using the ```did:ion``` method and return the DID Document Object (DDO). The DDO includes DPKI metadata associated with the DID such as public keys and service endpoints. 
 
 **5. Azure Active Directory Verified Credentials Service**
-An issuance and verification API and open-source SDK for [W3C Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) that are signed with the ```did:ion``` method. They enable identity owners to generate, present, and verify claims. This forms the basis of trust between users of the systems.
+An issuance and verification service in Azure and a REST API for [W3C Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) that are signed with the ```did:ion``` method. They enable identity owners to generate, present, and verify claims. This forms the basis of trust between users of the systems.
 
 ## A sample scenario
 

articles/active-directory/verifiable-credentials/enable-your-tenant-verifiable-credentials.md

@@ -10,7 +10,8 @@ ms.topic: tutorial
 ms.subservice: verifiable-credentials
 ms.date: 06/24/2021
 ms.author: barclayn
-ms.reviewer: 
+ms.reviewer:
+ROBOTS: NOINDEX 
 
 # Customer intent: As an administrator, I want the high-level steps that I should follow so that I can quickly start using verifiable credentials in my own Azure Active Directory.