Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into nsg

Author: cherylmc

articles/azure-databricks/TOC.yml

@@ -37,14 +37,16 @@
   - name: Language guides
     items:
     - name: Python
-      href: /azure/databricks/languages/python
-      maintainContext: true
-    - name: Koalas
-      href: /azure/databricks/languages/koalas
-      maintainContext: true
+      items:
+      - name: Python overview
+        href: /azure/databricks/languages/python
+        maintainContext: true
+      - name: Koalas
+        href: /azure/databricks/languages/koalas
+        maintainContext: true
     - name: R
       items:
-      - name: R guide
+      - name: R overview
         href: /azure/databricks/spark/latest/sparkr/index
         maintainContext: true
       - name: SparkR overview
@@ -281,9 +283,6 @@
     - name: Databricks Runtime
       href: /azure/databricks/runtime/dbr
       maintainContext: true
-    - name: Databricks Runtime with Conda
-      href: /azure/databricks/runtime/conda
-      maintainContext: true
     - name: Databricks Runtime for Machine Learning
       href: /azure/databricks/runtime/mlruntime
       maintainContext: true
@@ -307,6 +306,9 @@
     - name: Get workspace, cluster, notebook, and job identifiers
       href: /azure/databricks/workspace/workspace-details
       maintainContext: true
+    - name: Migrate to per-workspace URLs
+      href: /azure/databricks/workspace/migrate-workspace-urls
+      maintainContext: true
   - name: Clusters
     items:
     - name: Clusters overview
@@ -452,9 +454,6 @@
       - name: Azure Data Lake Storage
         href: /azure/databricks/data/data-sources/azure/azure-datalake
         maintainContext: true
-      - name: Azure Data Lake Storage credential passthrough
-        href: /azure/databricks/data/data-sources/azure/adls-passthrough
-        maintainContext: true 
       - name: Cosmos DB
         href: /azure/databricks/data/data-sources/azure/cosmosdb-connector
         maintainContext: true 
@@ -1027,7 +1026,7 @@
         href: /azure/databricks/security/access-control/pool-acl
         maintainContext: true  
       - name: Jobs access control
-        href: /azure/databricks/security/access-control/jobs-acl
+        href: /azure/databricks/security/access-control/job-acl
         maintainContext: true
       - name: Table access control
         items:
@@ -1110,7 +1109,7 @@
       - name: Provision users and groups using SCIM
         href: /azure/databricks/administration-guide/users-groups/scim/index
         maintainContext: true
-      - name: Configure SCIM provisioning for AAD
+      - name: Configure SCIM provisioning for Azure AD
         href: /azure/databricks/administration-guide/users-groups/scim/aad
         maintainContext: true
     - name: Manage access control
@@ -1139,9 +1138,6 @@
       - name: Conditional access
         href: /azure/databricks/administration-guide/access-control/conditional-access
         maintainContext: true
-      - name: Enable Azure Data Lake Storage credential passthrough
-        href: /azure/databricks/administration-guide/access-control/credential-passthrough
-        maintainContext: true
     - name: Manage workspace objects and behavior
       items:
       - name: Manage workspaces overview
@@ -1619,21 +1615,35 @@
         maintainContext: true
       - name: Authentication
         items:
-        - name: Personal access tokens
+        - name: Azure Databricks personal access tokens
           href: /azure/databricks/dev-tools/api/latest/authentication
           maintainContext: true
-        - name: Azure Active Directory (AAD) tokens
+        - name: Azure Active Directory tokens
           items:
-          - name: AAD token authentication overview
+          - name: Azure AD token authentication overview
             href: /azure/databricks/dev-tools/api/latest/aad/index
             maintainContext: true
-          - name: Get an AAD token using the AAD Authentication Library
+          - name: Get an Azure AD token using the Azure AD Authentication Library
             href: /azure/databricks/dev-tools/api/latest/aad/app-aad-token
             maintainContext: true
-          - name: Get an AAD token using a service principal
+          - name: Get an Azure AD token using a service principal
             href: /azure/databricks/dev-tools/api/latest/aad/service-prin-aad-token
             maintainContext: true
-          - name: Troubleshoot AAD access tokens
+          - name: Troubleshoot Azure AD access tokens
+            href: /azure/databricks/dev-tools/api/latest/aad/troubleshoot-aad-token
+          maintainContext: true
+        - name: Azure Active Directory (Azure AD) tokens
+          items:
+          - name: Azure AD token authentication overview
+            href: /azure/databricks/dev-tools/api/latest/aad/index
+            maintainContext: true
+          - name: Get an Azure AD token using the AAD Authentication Library
+            href: /azure/databricks/dev-tools/api/latest/aad/app-aad-token
+            maintainContext: true
+          - name: Get an Azure AD token using a service principal
+            href: /azure/databricks/dev-tools/api/latest/aad/service-prin-aad-token
+            maintainContext: true
+          - name: Troubleshoot Azure AD access tokens
             href: /azure/databricks/dev-tools/api/latest/aad/troubleshoot-aad-token
             maintainContext: true
       - name: Clusters
@@ -1666,7 +1676,7 @@
           - name: SCIM API (Users)
             href: /azure/databricks/dev-tools/api/latest/scim/scim-users
           - name: SCIM API (Groups)
-            href: /azure/databricks/dev-tools/api/latest/scim/scim-groups
+            href: /azure/databricks/dev-tools/api/latest/scim/scim-group
         maintainContext: true 
       - name: Secrets
         href: /azure/databricks/dev-tools/api/latest/secrets
@@ -1760,6 +1770,9 @@
       - name: Platform release notes 
         href: /azure/databricks/release-notes/product/index
         maintainContext: true
+      - name: May 2020
+        href: /azure/databricks/release-notes/product/2020/may
+        maintainContext: true
       - name: April 2020
         href: /azure/databricks/release-notes/product/2020/april
         maintainContext: true
@@ -1851,12 +1864,21 @@
         - name: Runtime releases
           href: /azure/databricks/release-notes/runtime/releases
           maintainContext: true
+        - name: Databricks Runtime 7.0 Genomics (Beta)
+          href: /azure/databricks/release-notes/runtime/7.0genomics
+          maintainContext: true
         - name: Databricks Runtime 7.0 ML (Beta)
           href: /azure/databricks/release-notes/runtime/7.0ml
           maintainContext: true
         - name: Databricks Runtime 7.0 (Beta)
           href: /azure/databricks/release-notes/runtime/7.0
           maintainContext: true
+        - name: Databricks Runtime 6.6 Genomics (Beta)
+          href: /azure/databricks/release-notes/runtime/6.6genomics
+          maintainContext: true
+        - name: Databricks Runtime 6.6 (Beta)
+          href: /azure/databricks/release-notes/runtime/6.6
+          maintainContext: true
         - name: Databricks Runtime 6.5
           href: /azure/databricks/release-notes/runtime/6.5
           maintainContext: true
@@ -1902,27 +1924,18 @@
         - name: Databricks Runtime 6.0
           href: /azure/databricks/release-notes/runtime/6.0
           maintainContext: true
-        - name: Databricks Runtime 6.0 with Conda
-          href: /azure/databricks/release-notes/runtime/6.0conda
-          maintainContext: true
         - name: Databricks Runtime 6.0 ML
           href: /azure/databricks/release-notes/runtime/6.0ml
           maintainContext: true
         - name: Databricks Runtime 5.5
           href: /azure/databricks/release-notes/runtime/5.5
           maintainContext: true 
-        - name: Databricks Runtime 5.5 with Conda
-          href: /azure/databricks/release-notes/runtime/5.5conda
-          maintainContext: true 
         - name: Databricks Runtime 5.5 ML
           href: /azure/databricks/release-notes/runtime/5.5ml
           maintainContext: true
         - name: Databricks Runtime 5.4
           href: /azure/databricks/release-notes/runtime/5.4
           maintainContext: true 
-        - name: Databricks Runtime 5.4 with Conda
-          href: /azure/databricks/release-notes/runtime/5.4conda
-          maintainContext: true 
         - name: Databricks Runtime 5.4 ML
           href: /azure/databricks/release-notes/runtime/5.4ml
           maintainContext: true
@@ -1938,21 +1951,12 @@
         - name: Databricks Runtime 5.2
           href: /azure/databricks/release-notes/runtime/5.2
           maintainContext: true 
-        - name: Databricks Runtime 5.2 ML
-          href: /azure/databricks/release-notes/runtime/5.2ml
-          maintainContext: true
         - name: Databricks Runtime 5.1
           href: /azure/databricks/release-notes/runtime/5.1
           maintainContext: true 
-        - name: Databricks Runtime 5.1 ML 
-          href: /azure/databricks/release-notes/runtime/5.1ml
-          maintainContext: true
         - name: Databricks Runtime 5.0
           href: /azure/databricks/release-notes/runtime/5.0
           maintainContext: true 
-        - name: Databricks Runtime 5.0 ML 
-          href: /azure/databricks/release-notes/runtime/5.0ml
-          maintainContext: true
         - name: Databricks Runtime 4.3
           href: /azure/databricks/release-notes/runtime/4.3
           maintainContext: true
@@ -1962,9 +1966,6 @@
         - name: Databricks Runtime 4.1
           href: /azure/databricks/release-notes/runtime/4.1
           maintainContext: true 
-        - name: Databricks Runtime 4.1 ML 
-          href: /azure/databricks/release-notes/runtime/4.1ml
-          maintainContext: true
         - name: Databricks Runtime 4.0
           href: /azure/databricks/release-notes/runtime/4.0
           maintainContext: true

articles/key-vault/general/about-keys-secrets-certificates.md

@@ -42,7 +42,7 @@ Refer to the JOSE specifications for relevant data types for keys, encryption, a
 
 Objects stored in Key Vault are versioned whenever a new instance of an object is created. Each version is assigned a unique identifier and URL. When an object is first created, it's given a unique version identifier and marked as the current version of the object. Creation of a new instance with the same object name gives the new object a unique version identifier, causing it to become the current version.  
 
-Objects in Key Vault can be addressed using the current identifier or a version-specific identifier. For example, given a Key with the name `MasterKey`, performing operations with the current identifier causes the system to use the latest available version. Performing operations with the version-specific identifier causes the system to use that specific version of the object.  
+Objects in Key Vault can be addressed by specifing a version or by omitting version for operations on current version of the object. For example, given a Key with the name `MasterKey`, performing operations without specifing a version causes the system to use the latest available version. Performing operations with the version-specific identifier causes the system to use that specific version of the object.  
 
 Objects are uniquely identified within Key Vault using a URL. No two objects in the system have the same URL, regardless of geo-location. The complete URL to an object is called the Object Identifier. The URL consists of a prefix that identifies the Key Vault, object type, user provided Object Name, and an Object Version. The Object Name is case-insensitive and immutable. Identifiers that don't include the Object Version are referred to as Base Identifiers.  
 
@@ -58,7 +58,7 @@ Where:
 |-|-|  
 |`keyvault-name`|The name for a key vault in the Microsoft Azure Key Vault service.<br /><br /> Key Vault names are selected by the user and are globally unique.<br /><br /> Key Vault name must be a 3-24 character string, containing only 0-9, a-z, A-Z, and -.|  
 |`object-type`|The type of the object, "keys",  "secrets", or 'certificates'.|  
-|`object-name`|An `object-name` is a user provided name for and must be unique within a Key Vault. The name must be a 1-127 character string, containing only 0-9, a-z, A-Z, and -.|  
+|`object-name`|An `object-name` is a user provided name for and must be unique within a Key Vault. The name must be a 1-127 character string, starting with a letter and containing only 0-9, a-z, A-Z, and -.|  
 |`object-version`|An `object-version` is a system-generated, 32 character string identifier that is optionally used to address a unique version of an object.|  
 
 ## Next steps
@@ -67,4 +67,4 @@ Where:
 - [About secrets](../secrets/about-secrets.md)
 - [About certificates](../certificates/about-certificates.md)
 - [Authentication, requests, and responses](../general/authentication-requests-and-responses.md)
-- [Key Vault Developer's Guide](../general/developers-guide.md)
+- [Key Vault Developer's Guide](../general/developers-guide.md)

articles/key-vault/general/group-permissions-for-apps.md

@@ -104,6 +104,9 @@ Id                    : 1cef38c4-388c-45a9-b5ae-3d88375e166a
 ...
 ```
 
+> [!WARNING]
+> Azure Ad Groups does not support Managed Identities. Only service and user principals are supported.
+
 #### Users
 
 You can also add an individual user to an key vault's access control policy. **We do not recommend this.** We instead encourage you to add users to an Azure AD group, and add the group on the policies.

articles/spatial-anchors/concepts/anchor-relationships-way-finding.md

@@ -68,7 +68,7 @@ You can continue this procedure for more anchors and more sessions over time.
 
 ### Verify anchor connections
 
-The app can verify that two anchors are connected by issuing a query for nearby anchors. When the query's result contains the target anchor, the anchor connection is verified. If the anchors aren't connected, the app can try to connect them again.
+The app can verify that two anchors are connected by issuing a query for nearby anchors, which you do by setting the `NearAnchorCriteria` on a `CloudSpatialAnchorWatcher`. When the query's result contains the target anchor, the anchor connection is verified. If the anchors aren't connected, the app can try to connect them again.
 
 Here are some reasons why anchors might fail to connect:
 

articles/spatial-anchors/concepts/guidelines-effective-anchor-experiences.md

@@ -13,11 +13,15 @@ ms.service: azure-spatial-anchors
 
 # Create an effective anchor experience by using Azure Spatial Anchors
 
-This article provides guidelines and considerations to help you effectively create and locate anchors by using Spatial Anchors.
+This article provides guidelines and considerations to help you effectively create and locate anchors by using Azure Spatial Anchors.
+
+## Anchor improvement over time
+
+With Azure Spatial Anchors, each time you locate anchors, we attempt to improve the quality of future locate operations. We do this by using the environment data collected to augment the visual information on the anchors we are looking for. This process runs under the hood and is an offline optimization run by the Azure Spatial Anchors service to optimize for your environment. The additional data gathered during each operation builds a stronger understanding of the environment. This improves quality and allows you to better locate anchors through environment change, time passing, and for users looking at anchors from different angles and perspectives.
 
 ## Good anchors
 
-Spatial Anchors helps you create good anchors. It's important to invest time in either educating or guiding users in your user experience (UX) to create good anchors. By investing in creating good anchors up front, you help end users to reliably find anchors:
+While Azure Spatial Anchors does attempt to improve the quality of anchors over time, it is also important to invest time in either educating or guiding users in your user experience (UX) to create good anchors. By investing in creating good anchors up front, you help end users to reliably find anchors:
 
 - Across different devices.
 - At various times.
@@ -96,7 +100,7 @@ Visual tracking systems rely on the visual features in an environment. The more
 
 Follow the general guidelines in this section to build a UX that encourages a useful scan of the environment.
 
-First, if the user doesn't locate an anchor within a few seconds, the app should encourage users to move the device to capture more perspectives. The app can also encourage users to move themselves around the environment to scan for the anchor from more perspectives. The more feature perspectives that the device sees, the better.
+First, if the user doesn't locate an anchor within a few seconds, the app should encourage users to move the device to capture more perspectives. The app can also encourage users to move themselves around the environment to scan for the anchor from more perspectives. The more feature perspectives that the device sees, the better, as it will increase the likelihood that an anchor is located, and it will also collect more environment data that will be used to improve the quality of the anchor.
 
 For target scenarios, ask the user to move around the target to view it from different perspectives. In other words, ask the user to capture the target from new perspectives until the anchor is located.
 

articles/spatial-anchors/overview.md

@@ -25,7 +25,7 @@ These precise points of interest are referred to as Spatial Anchors.
 
 Some example use cases enabled by Spatial Anchors include:
 
-- [Multi-user experiences](tutorials/tutorial-share-anchors-across-devices.md). Spatial Anchors makes it easy for people in the same place to participate in multi-user mixed reality applications. For example, two people can start a game of mixed reality chess by placing a virtual chess board on a table. Then, by pointing their device at the table, they can view and interact with the virtual chess board together.
+- [Multi-user experiences](tutorials/tutorial-share-anchors-across-devices.md). Azure Spatial Anchors makes it easy for people in the same place to participate in multi-user mixed reality applications. For example, two people can start a game of mixed reality chess by placing a virtual chess board on a table. Then, by pointing their device at the table, they can view and interact with the virtual chess board together.
 
 - [Way-finding](concepts/anchor-relationships-way-finding.md). Developers can also connect Spatial Anchors together creating relationships between them. For example, an app may include an experience that has two or more points of interest that a user must interact with to complete a task. Those points of interest can be created in a connected fashion. Later, when the user is completing the multi-step task, the app can ask for anchors that are nearby the current one to direct the user towards the next step in the task.
 
@@ -36,7 +36,7 @@ sections provide information about getting started with building apps using Azur
 
 ## Next steps
 
-Create your first app with Spatial Anchors.
+Create your first app with Azure Spatial Anchors.
 
 > [!div class="nextstepaction"]
 > [Unity (HoloLens)](quickstarts/get-started-unity-hololens.md)