<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Entra-Id on Daniyal Ahmed | Red Team &amp; Cloud Security</title><link>https://daniyalahmed.dev/tags/entra-id/</link><description>Recent content in Entra-Id on Daniyal Ahmed | Red Team &amp; Cloud Security</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</managingEditor><webMaster>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</webMaster><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://daniyalahmed.dev/tags/entra-id/index.xml" rel="self" type="application/rss+xml"/><item><title>Entra Default User Permissions: The Open App Registration Problem</title><link>https://daniyalahmed.dev/posts/entra-default-user-permissions-the-open-app-registration-problem/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><author>daniyal.ahmed@microtechx.com (Daniyal Ahmed)</author><guid>https://daniyalahmed.dev/posts/entra-default-user-permissions-the-open-app-registration-problem/</guid><description>In your Entra ID tenant right now, every one of your users can register an application, assign it Mail.Read permission, consent to it themselves, and start reading their own email programmatically with no admin approval, no alert, and no audit flag. That is the default configuration Microsoft ships. This article asks: who has already done this, what did they access, and how do you find out?
This is not a vulnerability in the traditional sense.</description></item></channel></rss>