#Metabliss mixed in key how to#

The result of having the end-user sign in is that your application is given an access token and a refresh token. Your end user needs to provide their credentials periodically in order for your application to maintain access. Your application is then able to access Azure resources with the same level of access as the end user that logged in.

This authentication mechanism is the recommended approach if you want an end user to sign in to your application via Azure AD.

#Metabliss mixed in key how to#

For instructions on how to retrieve the tenant ID, see Get the tenant ID. From the screenshot below, the domain name is, and the GUID within brackets is the tenant ID. You can retrieve it by hovering the mouse in the top-right corner of the Azure portal. For example, it is available from the Data Lake Storage Gen1 account blade. You can retrieve it from the Azure portal.

For instructions on Azure AD application configuration for service-to-service authentication, see Service-to-service authentication with Data Lake Storage Gen1 using Azure Active Directory.

This article talks about how to create an Azure AD native application for end-user authentication.

Service-to-service authentication (pick this option from the drop-down above)īoth these options result in your application being provided with an OAuth 2.0 token, which gets attached to each request made to Data Lake Storage Gen1 or Azure Data Lake Analytics.

Before authoring an application that works with Data Lake Storage Gen1 or Azure Data Lake Analytics, you must decide how to authenticate your application with Azure Active Directory (Azure AD). Azure Data Lake Storage Gen1 uses Azure Active Directory for authentication.