Merge pull request #208278 from MicrosoftDocs/main

Daily Publishing 8/17 10AM

Author: JiayueHu

articles/active-directory/authentication/concept-authentication-passwordless.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 06/23/2022
+ms.date: 08/17/2022
 
 ms.author: justinha
 author: justinha
@@ -129,7 +129,7 @@ The following providers offer FIDO2 security keys of different form factors that
 | Octatco                   | ![y]              | ![y]| ![n]| ![n]| ![n]           | https://octatco.com/                                                                                |
 | OneSpan Inc.              | ![n]              | ![y]| ![n]| ![y]| ![n]           | https://www.onespan.com/products/fido                                                               |
 | Swissbit                  | ![n]              | ![y]| ![y]| ![n]| ![n]           | https://www.swissbit.com/en/products/ishield-fido2/                                                 |
-| Thales Group              | ![n]              | ![y]| ![y]| ![n]| ![n]           | https://cpl.thalesgroup.com/access-management/authenticators/fido-devices                           |
+| Thales Group              | ![n]              | ![y]| ![y]| ![n]| ![y]           | https://cpl.thalesgroup.com/access-management/authenticators/fido-devices                           |
 | Thetis                    | ![y]              | ![y]| ![y]| ![y]| ![n]           | https://thetis.io/collections/fido2                                                                 |
 | Token2 Switzerland        | ![y]              | ![y]| ![y]| ![n]| ![n]           | https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key               |
 | TrustKey Solutions        | ![y]              | ![y]| ![n]| ![n]| ![n]           | https://www.trustkeysolutions.com/security-keys/                                                    |

articles/active-directory/manage-apps/hide-application-from-user-portal.md

@@ -8,10 +8,12 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.workload: identity
 ms.topic: how-to
-ms.date: 07/21/2022
+ms.date: 08/17/2022
 ms.author: lenalepa
 ms.reviewer: ergreenl
 ms.collection: M365-identity-device-management
+zone_pivot_groups: enterprise-apps-all
+
 #customer intent: As an admin, I want to hide an enterprise application from user's experience so that it is not listed in the user's Active directory access portals or Microsoft 365 launchers
 ---
 
@@ -27,6 +29,8 @@ Learn how to hide enterprise applications in Azure Active Directory. When an app
 
 ## Hide an application from the end user
 
+:::zone pivot="portal"
+
 Use the following steps to hide an application from My Apps portal and Microsoft 365 application launcher.
 
 1. Sign in to the [Azure portal](https://portal.azure.com) as the global administrator for your directory.
@@ -38,12 +42,15 @@ Use the following steps to hide an application from My Apps portal and Microsoft
 1. Select **No** for the **Visible to users?** question.
 1. Select **Save**.
 
+:::zone-end
+
 > [!NOTE]
 > These instructions apply only to Enterprise applications.
 
-## Use Azure AD PowerShell to hide an application
+:::zone pivot="aad-powershell"
 
-To hide an application from the My Apps portal, you can manually add the HideApp tag to the service principal for the application. Run the following [AzureAD PowerShell](/powershell/module/azuread/#service_principals) commands to set the application's **Visible to Users?** property to **No**.
+
+To hide an application from the My Apps portal, you can manually add the HideApp tag to the service principal for the application. Run the following AzureAD PowerShell commands to set the application's **Visible to Users?** property to **No**.
 
 ```PowerShell
 Connect-AzureAD
@@ -54,6 +61,53 @@ $tags = $servicePrincipal.tags
 $tags += "HideApp"
 Set-AzureADServicePrincipal -ObjectId $objectId -Tags $tags
 ```
+:::zone-end
+
+:::zone pivot="ms-powershell"
+
+To hide an application from the My Apps portal, you can manually add the HideApp tag to the service principal for the application. Run the following Microsoft Graph PowerShell commands to set the application's **Visible to Users?** property to **No**.
+
+```PowerShell
+Connect-MgGraph
+
+$servicePrincipal = Get-MgServicePrincipal -ServicePrincipalId $objectId
+$tags = $servicePrincipal.tags
+$tags += "HideApp"
+Update-MgServicePrincipal -ServicePrincipalID  $objectId -Tags $tags
+```
+:::zone-end
+
+:::zone pivot="ms-graph"
+
+To hide an enterprise application using [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer), run the following queries.
+
+1. Get the application you want to hide.
+
+   ```http
+   GET https://graph.microsoft.com/v1.0/servicePrincipals/5f214ccd-3f74-41d7-b683-9a6d845eea4d
+   ```
+1. Update the application to hide it from users.
+
+   ```http
+   PATCH https://graph.microsoft.com/v1.0/servicePrincipals/5f214ccd-3f74-41d7-b683-9a6d845eea4d/
+   ```
+
+    Supply the following request body.
+
+    ```json
+    {
+        "tags": [
+        "HideApp"
+        ]
+    }
+    ```
+   
+   >[!WARNING]
+   >If the application has other tags, you must include them in the request body. Otherwise, the query will overwrite them.
+
+:::zone-end
+
+:::zone pivot="portal"
 
 ## Hide Microsoft 365 applications from the My Apps portal
 
@@ -66,6 +120,7 @@ Use the following steps to hide all Microsoft 365 applications from the My Apps
 1. For **Users can only see Office 365 apps in the Office 365 portal**, select **Yes**.
 1. Select **Save**.
 
+:::zone-end
 ## Next steps
 
 - [Remove a user or group assignment from an enterprise app](./assign-user-or-group-access-portal.md)

articles/active-directory/manage-apps/view-applications-portal.md

@@ -77,4 +77,4 @@ If you created a test application named **Azure AD SAML Toolkit 1** that was use
 
 Learn how to delete an enterprise application.
 > [!div class="nextstepaction"]
-> [Delete an application](add-application-portal.md)
+> [Delete an application](delete-application-portal.md)

articles/active-directory/saas-apps/lucid-all-products-provisioning-tutorial.md

@@ -0,0 +1,159 @@
+---
+title: 'Tutorial: Configure Lucid (All Products) for automatic user provisioning with Azure Active Directory | Microsoft Docs'
+description: Learn how to automatically provision and de-provision user accounts from Azure AD to Lucid (All Products).
+services: active-directory
+documentationcenter: ''
+author: twimmers
+writer: Thwimmer
+manager: beatrizd
+ms.assetid: 54a47643-8703-4ab9-96a5-a803b344ccc4
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.devlang: na
+ms.topic: tutorial
+ms.date: 07/20/2022
+ms.author: Thwimmer
+---
+
+# Tutorial: Configure Lucid (All Products) for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both Lucid (All Products) and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Lucid (All Products)](https://www.lucid.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+
+
+## Capabilities supported
+> [!div class="checklist"]
+> * Create users in Lucid (All Products).
+> * Remove users in Lucid (All Products) when they do not require access anymore.
+> * Keep user attributes synchronized between Azure AD and Lucid (All Products).
+> * Provision groups and group memberships in Lucid (All Products).
+> * [Single sign-on](./lucid-tutorial.md) to Lucid (All Products) (recommended)
+
+## Prerequisites
+
+The scenario outlined in this tutorial assumes that you already have the following prerequisites:
+
+* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md). 
+* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
+* A user account in Lucid (All Products) with Admin rights.
+* Confirm that you are on an Enterprise account with an up-to-date pricing plan. To upgrade, please contact our sales team.
+* Contact your Lucidchart Customer Success Manager so that they can enable SCIM for your account.
+
+## Step 1. Plan your provisioning deployment
+1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
+1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+1. Determine what data to [map between Azure AD and Lucid (All Products)](../app-provisioning/customize-application-attributes.md). 
+
+## Step 2. Configure Lucid (All Products) to support provisioning with Azure AD
+
+1. Log in to [Lucid Admin Console](https://lucid.app/). Navigate to **Admin**.
+1. Click **App integration** in the left-hand menu.
+1. Select the **SCIM** tile.
+1. Click **Generate Token**. Lucid will populate the **Bearer Token** text field with a unique code for you to share with Azure.Copy and save the **Bearer token**. This value will be entered in the **Secret Token** * field in the Provisioning tab of your Lucid(All Products) application in the Azure portal.
+
+	![Screenshot of token generation.](media/lucid-all-products-provisioning-tutorial/generate-token.png)
+
+## Step 3. Add Lucid (All Products) from the Azure AD application gallery
+
+Add Lucid (All Products) from the Azure AD application gallery to start managing provisioning to Lucid (All Products). If you have previously setup Lucid (All Products) for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+
+## Step 4. Define who will be in scope for provisioning 
+
+The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+* If you need additional roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
+
+
+## Step 5. Configure automatic user provisioning to Lucid (All Products) 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in Lucid (All Products) based on user and/or group assignments in Azure AD.
+
+### To configure automatic user provisioning for Lucid (All Products) in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
+
+1. In the applications list, select **Lucid (All Products)**.
+
+	![Screenshot of the Lucid (All Products) link in the Applications list.](common/all-applications.png)
+
+1. Select the **Provisioning** tab.
+
+	![Screenshot of Provisioning tab.](common/provisioning.png)
+
+1. Set the **Provisioning Mode** to **Automatic**.
+
+	![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
+
+1. Under the **Admin Credentials** section, input your Lucid (All Products) Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Lucid (All Products). If the connection fails, ensure your Lucid (All Products) account has Admin permissions and try again.
+
+ 	![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
+
+1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
+
+	![Screenshot of Notification Email.](common/provisioning-notification-email.png)
+
+1. Select **Save**.
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Lucid (All Products)**.
+
+1. Review the user attributes that are synchronized from Azure AD to Lucid (All Products) in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Lucid (All Products) for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the Lucid (All Products) API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+    |Attribute|Type|Supported for filtering|Required by Lucid (All Products)|
+    |---|---|---|---|
+    |userName|String|✓|✓
+    |emails[type eq "work"].value|String||✓
+    |active|Boolean||
+    |name.givenName|String||
+    |name.familyName|String||
+    |urn:ietf:params:scim:schemas:extension:lucid:2.0:User:billingCode|String||
+    |urn:ietf:params:scim:schemas:extension:lucid:2.0:User:productLicenses.Lucidchart|String||
+    |urn:ietf:params:scim:schemas:extension:lucid:2.0:User:productLicenses.Lucidspark|String||
+    |urn:ietf:params:scim:schemas:extension:lucid:2.0:User:productLicenses.LucidscaleExplorer|String||
+    |urn:ietf:params:scim:schemas:extension:lucid:2.0:User:productLicenses.LucidscaleCreator|String||
+
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Lucid (All Products)**.
+
+1. Review the group attributes that are synchronized from Azure AD to Lucid (All Products) in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Lucid (All Products) for update operations. Select the **Save** button to commit any changes.
+
+    |Attribute|Type|Supported for filtering|Required by Lucid (All Products)|
+    |---|---|---|---|
+    |displayName|String|✓|✓
+    |members|Reference||    
+
+1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+1. To enable the Azure AD provisioning service for Lucid (All Products), change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
+
+1. Define the users and/or groups that you would like to provision to Lucid (All Products) by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Provisioning Scope](common/provisioning-scope.png)
+
+1. When you are ready to provision, click **Save**.
+
+	![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
+
+This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. 
+
+## Step 6. Monitor your deployment
+Once you've configured provisioning, use the following resources to monitor your deployment:
+
+* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
+* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
+* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).  
+
+
+## More resources
+
+* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
+* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+
+## Next steps
+
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/media/lucid-all-products-provisioning-tutorial/generate-token.png

@@ -2898,8 +2898,10 @@
         href: linkedinelevate-provisioning-tutorial.md
       - name: LinkedIn Sales Navigator
         href: linkedinsalesnavigator-provisioning-tutorial.md
+      - name: Lucid (All Products)
+        href: lucid-all-products-provisioning-tutorial.md
       - name: Lucidchart
-        href: lucidchart-provisioning-tutorial.md
+        href: lucidchart-provisioning-tutorial.md        
       - name: Leapsome
         href: leapsome-provisioning-tutorial.md
       - name: LogicGate

articles/active-directory/saas-apps/toc.yml

@@ -827,13 +827,23 @@ The response contains the following properties
 
 | Property | Type | Description |
 | -------- | -------- | -------- |
-|`attestations`| [idTokenAttestation](#idtokenattestation-type) or [idTokenHintAttestation](#idtokenhintattestation-type) and/or [verifiablePresentationAttestation](#verifiablepresentationattestation-type) and/or [selfIssuedAttestation](#selfissuedattestation-type) and/or [accessTokenAttestation](#accesstokenattestation-type) (array) | describing supported inputs for the rules |
+|`attestations`| [attestions](#attestations-type)| describing supported inputs for the rules |
 |`validityInterval` | number | this value shows the lifespan of the credential |
 |`vc`| vcType array | types for this contract |
 |`customStatusEndpoint`| [customStatusEndpoint] (#customstatusendpoint-type) (optional) | status endpoint to include in the verifiable credential for this contract |
 
 If the property `customStatusEndpoint` property isn't specified then the `anonymous` status endpoint is used.
 
+#### attestations type
+
+| Property | Type | Description |
+| -------- | -------- | -------- |
+|`idTokens`| [idTokenAttestation](#idtokenattestation-type) (array) (optional) | describes id token inputs|
+|`idTokenHints`| [idTokenHintAttestation](#idtokenhintattestation-type) (array) (optional) | describes id token hint inputs |
+|`presentations`| [verifiablePresentationAttestation](#verifiablepresentationattestation-type) (array) (optional) | describes verifiable presentations inputs |
+|`selfIssued`| [selfIssuedAttestation](#selfissuedattestation-type) (array) (optional) | describes self issued inputs |
+|`accessTokens`| [accessTokenAttestation](#accesstokenattestation-type) (array) (optional) | describes access token inputs |
+
 #### idTokenAttestation type
 
 | Property | Type | Description |