<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure AD on Anything About IT</title><link>https://www.verboon.info/tags/azure-ad/</link><description>Recent content in Azure AD on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2020 14:14:12 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/azure-ad/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitoring Service principal sign-ins with AzureAD and Azure Sentinel</title><link>https://www.verboon.info/2020/10/monitoring-service-principal-sign-ins-with-azuread-and-azure-sentinel/</link><pubDate>Sat, 10 Oct 2020 14:14:12 +0000</pubDate><guid>https://www.verboon.info/2020/10/monitoring-service-principal-sign-ins-with-azuread-and-azure-sentinel/</guid><description>&lt;p&gt;Here is a conversation between Jeffrey (Developer) and Marc (IT Admin) working for ECorp Ltd.&lt;/p&gt;
&lt;p&gt;
 &lt;img src="images/101020_1404_MonitoringS1.png" alt=""&gt;

&lt;/p&gt;
&lt;p&gt;Looks familiar? Take a look in your Azure Active directory, how many applications do you have there? In an ideal world you maintain an inventory of all these applications somewhere in your asset management database so that you know who is the owner of the Application and what it is used for and what API permissions are granted. As for the client secret, this should be stored in a Vault.&lt;/p&gt;</description></item><item><title>How to monitor your Azure AD emergency account with Cloud App Security</title><link>https://www.verboon.info/2019/01/how-to-monitor-your-azure-ad-emergency-account-with-cloud-app-security/</link><pubDate>Wed, 09 Jan 2019 21:11:35 +0000</pubDate><guid>https://www.verboon.info/2019/01/how-to-monitor-your-azure-ad-emergency-account-with-cloud-app-security/</guid><description>&lt;p&gt;As a best practice you should have at least one or two emergency accounts in your Azure Active Directory. You would use these accounts in the event where due to a configuration mistake you inadvertently locked yourself out of the Azure Active Directory or when for some reason you can&amp;rsquo;t use MFA that should be enabled on all administrative accounts.&lt;/p&gt;
&lt;p&gt;For more guidance about creating emergency accounts I suggest you read &lt;a href="https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-emergency-access"&gt;Manage emergency access accounts in Azure AD&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Stay in Control of AzureAD Enterprise Application registrations with Cloud App Security</title><link>https://www.verboon.info/2018/12/stay-in-control-of-azuread-enterprise-application-registrations-with-cloud-app-security/</link><pubDate>Mon, 10 Dec 2018 22:33:04 +0000</pubDate><guid>https://www.verboon.info/2018/12/stay-in-control-of-azuread-enterprise-application-registrations-with-cloud-app-security/</guid><description>&lt;p&gt;Azure Active Directory provides a simple process that provides users with a single sign-on (SSO) experience for accessing cloud-based applications using their AzureAD identity. This is a great capability as it removes the need for users to manage multiple identities while enterprises keep visibility and if needed control over which applications are used by their employees.&lt;/p&gt;
&lt;p&gt;By default, all users within Azure Active Directory have the rights to register an application and users can allow consent to apps accessing company data on their behalf.&lt;/p&gt;</description></item></channel></rss>