It’s common for web, desktop, or even mobile applications to require access to protected resources in their environment. This may be custom Web APIs, Microsoft Graph or some other third-party service. In the episode, Principal PM Kyle Marsh joins Christos to give us a better understanding on how we can use Microsoft Authentication Library (MSAL) to secure our daemon services with the OAuth 2.0 client credentials flow. [01:07] - What is MSAL? [02:26] - How does MSAL compare to ADAL? [05:07] - MSAL Language support [05:44] - What is the definition of a service? [07:55] - Granting access scopes and permissions to a service [15:07] - Differences with other app types and dynamic scopes [17:17] - MSAL demo Overview of Microsoft Authentication Library (MSAL) https://docs.microsoft.com/azure/active-directory/develop/msal-overview?WT.mc_id=ondotnet-c9-cephilli Microsoft identity platform and the OAuth 2.0 client credentials flow https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow?WT.mc_id=ondotnet-c9-cephilli Acquire a token and call Microsoft Graph API using console app's identity https://docs.microsoft.com/azure/active-directory/develop/quickstart-v2-netcore-daemon?WT.mc_id=ondotnet-c9-cephilli Client Credentials grant sample code https://github.com/azure-samples/active-directory-dotnetcore-daemon-v2?WT.mc_id=ondotnet-c9-cephilli