Skip to main content

2 posts tagged with "Entra ID"

Identity, entitlements, and auth for agent and data apps.

View All Tags

Signing in is not authorization: app access is not agent access

· 6 min read
Sai Prudhvi Neelakantam
Senior Consultant, Data Engineering & AI at Evidi

Most “AI app” demos collapse three different questions into one login button:

  1. Can this person open the shell?
  2. Which agents are they allowed to talk to?
  3. Which knowledge are they allowed to see, download, or ground answers on?

In a real enterprise agent webapp, those are three different control planes. Treat them as one and you get either a security hole or a support nightmare.

Official Microsoft identity platform diagram: single-page app calling a web API

Figure 1. SPA calling a web API. Authentication gets you a token; authorization still has to happen on the API. Source: Microsoft Learn: authentication flows and app scenarios.

Knowledge RBAC for enterprise agents: same gates for chat, browse, and citations

· 5 min read
Sai Prudhvi Neelakantam
Senior Consultant, Data Engineering & AI at Evidi

An agent that answers from documents is only as trustworthy as the document permissions behind it.

Teams often lock the chat endpoint carefully, then leave library browse and citation PDF downloads open to anyone who can sign in. That is not a knowledge boundary. That is a second door with a nicer UI.

Create an app role in Microsoft Entra

*Figure 1. Product capabilities belong as app roles on the API. Source: Microsoft Learn: add app roles.