Merge pull request #153388 from MicrosoftDocs/master

4/06 AM Publish

Author: huypub

articles/active-directory/manage-apps/delete-application-portal.md

@@ -46,7 +46,7 @@ To delete an application from your Azure AD tenant:
 
 ## Clean up resources
 
-When your done with this quickstart series, consider deleting the app to clean up your test tenant. Deleting the app was covered in this quickstart.
+When you are done with this quickstart series, consider deleting the app to clean up your test tenant. Deleting the app was covered in this quickstart.
 
 ## Next steps
 

articles/active-directory/managed-identities-azure-resources/media/overview/when-use-managed-identities.png

@@ -21,7 +21,7 @@ ms.collection: M365-identity-device-management
 
 # What are managed identities for Azure resources?
 
-A common challenge for developers is the management of secrets and credentials to secure communication between different services. On Azure, managed identities eliminate the need for developers having to manage credentials by providing an identity for the Azure resource in Azure AD and using it to obtain Azure Active Directory (Azure AD) tokens. This also helps accessing [Azure Key Vault](../../key-vault/general/overview.md) where developers can store credentials in a secure manner. Managed identities for Azure resources solves this problem by providing Azure services with an automatically managed identity in Azure AD.
+A common challenge for developers is the management of secrets and credentials used to secure communication between different components making up a solution. Managed identities eliminate the need for developers to manage credentials. Managed identities provide an identity for applications to use when connecting to resources that support Azure Active Directory (Azure AD) authentication. Applications may use the managed identity to obtain Azure AD tokens. For example, an application may use a managed identity to access resources like [Azure Key Vault](../../key-vault/general/overview.md) where developers can store credentials in a secure manner or to access storage accounts.
 
 What can a managed identity be used for?
 
@@ -30,7 +30,7 @@ What can a managed identity be used for?
 Here are some of the benefits of using Managed identities:
 
 - You don't need to manage credentials. Credentials are not even accessible to you.
-- You can use managed identities to authenticate to any resource that supports Azure Active Directory authentication including your own applications.
+- You can use managed identities to authenticate to any resource that supports [Azure Active Directory authentication](../authentication/overview-authentication.md) including your own applications.
 - Managed identities can be used without any additional cost.
 
 > [!NOTE]
@@ -59,7 +59,7 @@ The table below shows the differences between the two types of managed identitie
 
 ## How can I use managed identities for Azure resources?
 
-![some examples of how a developer may use managed identities to get access to resources from their code without managing authentication information](media/overview/azure-managed-identities-examples.png)
+![some examples of how a developer may use managed identities to get access to resources from their code without managing authentication information](media/overview/when-use-managed-identities.png)
 
 ## What Azure services support the feature?<a name="which-azure-services-support-managed-identity"></a>
 

articles/active-directory/managed-identities-azure-resources/overview.md

@@ -65,7 +65,7 @@ Once Privileged Identity Management is set up, you can learn your way around.
 | Task + Manage | Description |
 | --- | --- |
 | **My roles**  | Displays a list of eligible and active roles assigned to you. This is where you can activate any assigned eligible roles. |
-| **My requests** | Displays your pending requests to activate eligible role assignments. |
+| **Pending requests** | Displays your pending requests to activate eligible role assignments. |
 | **Approve requests** | Displays a list of requests to activate eligible roles by users in your directory that you are designated to approve. |
 | **Review access** | Lists active access reviews you are assigned to complete, whether you're reviewing access for yourself or someone else. |
 | **Azure AD roles** | Displays a dashboard and settings for Privileged role administrators to manage Azure AD role assignments. This dashboard is disabled for anyone who isn't a privileged role administrator. These users have access to a special dashboard titled My view. The My view dashboard only displays information about the user accessing the dashboard, not the entire organization. |

articles/active-directory/privileged-identity-management/pim-getting-started.md

@@ -0,0 +1,148 @@
+---
+title: 'Tutorial: Configure Boxcryptor 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 Boxcryptor.
+services: active-directory
+documentationcenter: ''
+author: Zhchia
+writer: Zhchia
+manager: beatrizd
+
+ms.assetid: 656de6d6-399e-4346-a07e-0e5fefb0b4ee
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: article
+ms.date: 04/02/2021
+ms.author: Zhchia
+---
+
+# Tutorial: Configure Boxcryptor for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both Boxcryptor and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Boxcryptor](https://www.boxcryptor.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](../manage-apps/user-provisioning.md). 
+
+
+## Capabilities Supported
+> [!div class="checklist"]
+> * Create users in Boxcryptor
+> * Remove users in Boxcryptor when they do not require access anymore
+> * Keep user attributes synchronized between Azure AD and Boxcryptor
+> * Provision groups and group memberships in Boxcryptor
+> * [Single sign-on](https://docs.microsoft.com/azure/active-directory/saas-apps/boxcryptor-tutorial) to Boxcryptor (recommended)
+
+## Prerequisites
+
+The scenario outlined in this tutorial assumes that you already have the following prerequisites:
+
+* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) 
+* A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). 
+* Boxcryptor Single sign-on enabled [subscription](https://www.boxcryptor.com/pricing/for-teams).
+
+## Step 1. Plan your provisioning deployment
+1. Learn about [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning).
+2. Determine who will be in [scope for provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
+3. Determine what data to [map between Azure AD and Boxcryptor](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes). 
+
+## Step 2. Configure Boxcryptor to support provisioning with Azure AD
+To configure provisioning on Boxcryptor, reach out to your Boxcryptor account manager or the [Boxcryptor support team](mailto:[email protected]) who will enable provisioning on Boxcryptor and reach out to you with your Boxcryptor Tenant URL and Secret Token. These values will be entered in the **Tenant URL** and **Secret Token** field in the Provisioning tab of your Boxcryptor application in the Azure portal.
+
+## Step 3. Add Boxcryptor from the Azure AD application gallery
+
+Add Boxcryptor from the Azure AD application gallery to start managing provisioning to Boxcryptor. If you have previously setup Boxcryptor 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](https://docs.microsoft.com/azure/active-directory/manage-apps/add-gallery-app). 
+
+## 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). 
+
+* When assigning users and groups to Boxcryptor, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](https://docs.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps) to add additional roles. 
+
+* 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts). 
+
+
+## Step 5. Configure automatic user provisioning to Boxcryptor 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
+
+### To configure automatic user provisioning for Boxcryptor in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Enterprise applications blade](common/enterprise-applications.png)
+
+2. In the applications list, select **Boxcryptor**.
+
+	![The Boxcryptor link in the Applications list](common/all-applications.png)
+
+3. Select the **Provisioning** tab.
+
+	![Provisioning tab](common/provisioning.png)
+
+4. Set the **Provisioning Mode** to **Automatic**.
+
+	![Provisioning tab automatic](common/provisioning-automatic.png)
+
+5. Under the **Admin Credentials** section, input your Boxcryptor Tenant URL and Secret Token retrieved earlier in Step 2. Click **Test Connection** to ensure Azure AD can connect to Boxcryptor. If the connection fails, ensure your Boxcryptor account has Admin permissions and try again.
+
+ 	![Token](common/provisioning-testconnection-tenanturltoken.png)
+
+6. 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.
+
+	![Notification Email](common/provisioning-notification-email.png)
+
+7. Select **Save**.
+
+8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Boxcryptor**.
+
+9. Review the user attributes that are synchronized from Azure AD to Boxcryptor in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Boxcryptor for update operations. If you choose to change the [matching target attribute](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes), you will need to ensure that the Boxcryptor API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for Filtering|
+   |---|---|---|
+   |userName|String|✓|
+   |preferredLanguage|String|
+   |name.givenName|String|
+   |name.familyName|String|
+   |externalId|String|
+   |addresses[type eq "work"].country|String|
+
+10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Boxcryptor**.
+
+11. Review the group attributes that are synchronized from Azure AD to Boxcryptor in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Boxcryptor for update operations. Select the **Save** button to commit any changes.
+
+      |Attribute|Type|Supported for Filtering|
+      |---|---|---|
+      |displayName|String|✓|
+      |externalId|String|
+      |members|Reference|
+
+12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../manage-apps/define-conditional-rules-for-provisioning-user-accounts.md).
+
+13. To enable the Azure AD provisioning service for Boxcryptor, change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
+
+14. Define the users and/or groups that you would like to provision to Boxcryptor by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Provisioning Scope](common/provisioning-scope.png)
+
+15. 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:
+
+1. Use the [provisioning logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs) to determine which users have been provisioned successfully or unsuccessfully
+2. Check the [progress bar](https://docs.microsoft.com/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user) to see the status of the provisioning cycle and how close it is to completion
+3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-quarantine-status).  
+
+## Additional resources
+
+* [Managing user account provisioning for Enterprise Apps](../manage-apps/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](../manage-apps/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/boxcryptor-provisioning-tutorial.md

@@ -15,6 +15,9 @@ ms.author: Zhchia
 
 The objective of this tutorial is to show you the steps you need to perform in GitHub and Azure AD to automatically provision and de-provision user accounts from Azure AD to GitHub.
 
+> [!NOTE]
+> The Azure AD provisioning integration relies on the [GitHub SCIM API](https://developer.github.com/v3/scim/), which is available to [GitHub Enterprise Cloud](https://help.github.com/articles/github-s-products/#github-enterprise) customers on the [GitHub Enterprise billing plan](https://help.github.com/articles/github-s-billing-plans/#billing-plans-for-organizations).
+
 ## Prerequisites
 
 The scenario outlined in this tutorial assumes that you already have the following items:
@@ -27,7 +30,7 @@ The scenario outlined in this tutorial assumes that you already have the followi
 * SCIM provisioning to a single organization is supported only when SSO is enabled at the organization level
 
 > [!NOTE]
-> The Azure AD provisioning integration relies on the [GitHub SCIM API](https://developer.github.com/v3/scim/), which is available to [GitHub Enterprise Cloud](https://help.github.com/articles/github-s-products/#github-enterprise) customers on the [GitHub Enterprise billing plan](https://help.github.com/articles/github-s-billing-plans/#billing-plans-for-organizations).
+> This integration is also available to use from Azure AD US Government Cloud environment. You can find this application in the Azure AD US Government Cloud Application Gallery and configure it in the same way as you do from public cloud.
 
 ## Assigning users to GitHub
 

articles/active-directory/saas-apps/github-provisioning-tutorial.md

@@ -2149,6 +2149,8 @@
         href: bonusly-provisioning-tutorial.md
       - name: Box
         href: box-userprovisioning-tutorial.md
+      - name: Boxcryptor
+        href: boxcryptor-provisioning-tutorial.md
       - name: Bpanda
         href: bpanda-provisioning-tutorial.md
       - name: Brivo Onair Identity Connector

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

@@ -28,7 +28,7 @@ Azure PCK caching service:
 
 ## Is SGX attestation supported by Azure Attestation in non-Azure environments
 
-Azure Attestation depends on the security baseline stated by Azure PCK caching service to validate the TEEs. Azure PCK caching service is currently designed to support only Azure Confidential computing nodes. 
+No. Azure Attestation depends on the security baseline stated by Azure PCK caching service to validate the TEEs. Azure PCK caching service is currently designed to support only Azure Confidential computing nodes. 
 
 ## What validations does Azure Attestation perform for attesting SGX enclaves
 

articles/attestation/faq.md

@@ -92,9 +92,6 @@ If a hop is red, it signifies that it is part of at-least one unhealthy path. NP
 ### How does fault localization in Performance Monitor work?
 NPM uses a probabilistic mechanism to assign fault-probabilities to each network path, network segment, and the constituent network hops based on the number of unhealthy paths they are a part of. As the network segments and hops become part of more number of unhealthy paths, the fault-probability associated with them increases. This algorithm works best when you have many nodes with NPM agent connected to each other as this increases the data points for calculating the fault-probabilities.
 
-### How can I create alerts in NPM?
-Currently, creating alerts from the NPM UI is failing due to a known issue. Please [create alerts manually](../alerts/alerts-log.md).
-
 ### What are the default Log Analytics queries for alerts
 Performance monitor query
 

articles/azure-monitor/insights/network-performance-monitor-faq.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 04/05/2021
+ms.date: 04/06/2021
 ms.author: b-juche
 ---
 # FAQs About Azure NetApp Files
@@ -87,10 +87,6 @@ Azure NetApp Files is an Azure native service. All PUT, POST, and DELETE APIs ag
 
 For the complete list of API operations, see [Azure NetApp Files REST API](/rest/api/netapp/).
 
-### How do I audit file access on Azure NetApp Files NFS (v3 and v4.1) volumes?
-
-You can configure audit logs on the client side. All read, write, and attribute changes are logged. 
-
 ### Can I use Azure policies with Azure NetApp Files?
 
 Yes, you can create [custom Azure policies](../governance/policy/tutorials/create-custom-policy-definition.md).