Approving Fennibi in Microsoft Entra ID — a guide for administrators
Which connection mode fits your organization, which permissions Fennibi requests, and how an administrator sets up exactly the access Fennibi needs — and no more.
published on 2026-11-03, updated on 2026-11-12
Fennibi reads your Power BI semantic models to document them and to answer questions from their
data. Your users connect Fennibi on fennibi.com under Account → Configuration → Fabric
connection. Depending on the mode you choose, Fennibi works under the identity of a signed-in
user, under a service principal of your own, or under two identities: the service principal or a
stored Microsoft connection for the documentation, the person signed in right now for the live
chat.
This guide helps you choose the mode and then walks you through its setup. No other application
and no other permission in your tenant is affected.
1. At a glance: what you decide and configure
- Choose the connection mode (section 2). It decides which identity Fennibi works under,
whether row-level security applies, and who needs a Power BI licence.
- Set up that mode: delegated, alone or combined with a personal sign-in (section 3),
delegated only while signed in (section 4), or a service principal, alone or combined with a
personal sign-in (section 5).
- Check the Power BI tenant settings (section 6).
- Give each identity the roles it needs: the connecting users, or the service principal in
the chosen workspaces (section 7).
- If you use standard reports, decide which models they may cover. Standard reports need a
service principal or a stored Microsoft connection, and every reader of the account sees the
same result (section 2).
- Optional: limit how long a connection stays valid and check Fennibi's access in your logs
(section 8).
2. Choose your connection mode
¹ Not needed if the workspace of the model is on a Fabric F64 (or larger) or Power BI Premium
capacity. There, a user with a free licence and the Viewer role can read the model. Check this
against your licensing before you rely on it.
² A scheduled documentation update is not a Power BI refresh of your semantic model.
Fennibi never refreshes a model or its data. On a schedule the user sets up, it reads the model's
structure again and updates the documentation, so that changes to the model (new measures,
tables or relationships) show up there.
Which mode fits
- To try Fennibi out: Delegated. One approval, done in a few minutes, and Fennibi sees
only what the person testing it sees.
- If your security policy is strict: a service principal. You choose the workspaces, you
own and rotate the credential, and the access does not depend on any one employee. If Fennibi
should hold no token for a person at all, Delegated, only while signed in is the alternative.
For the documentation under a service principal, it depends on the workspace, see the next two
points.
- In production on a Fabric or Premium capacity, the documentation belongs on a service
principal. The capacity is a prerequisite for this, not a promise: check it with a first
documentation run before you rely on it. For the live chat, the question is row-level security:
- No RLS on your models, or the chat may ignore it: Service principal for everything.
Chat users then need no Power BI licence, but every chat user of your Fennibi account
sees what the service principal sees.
- RLS has to apply in the chat: Service principal plus personal sign-in. The
documentation runs under the service principal, and every person asks their questions under
their own identity, with their own RLS roles. A question without a sign-in is refused, never
answered under the service principal.
- In production on Pro workspaces, the documentation belongs on a stored Microsoft
connection. Under a service principal, the documentation fails there in our tests with
Microsoft's error
PowerBINotLicensed. Under the connecting user with a Pro licence, it runs.
For the live chat, the question is again row-level security:
- No RLS on your models, or one person uses the account: Delegated. The chat runs under
the connecting user, who as an admin of the model sees everything.
- RLS has to apply in the chat: Delegated plus personal sign-in. The documentation runs
under the stored connection, and every person asks their questions under their own identity,
with their own RLS roles. A question without a sign-in is refused, never answered under the
stored connection.
Where the access lies: three ways
Whoever holds the access to your tenant reads your models themselves. So it is worth asking where
that access lies. There are three equal ways:
- Access at Fennibi. The client secret of your service principal or the refresh token of the
connecting user is stored encrypted at Fennibi. Schedules, standard reports and runs through
the API run at any time, with nothing running on your side.
- Access with you (Access stays with you (standalone bundle)). Fennibi knows only the
tenant id and client id of your app registration, no secret and no token. The secret stays
with the token broker of the locally installed standalone bundle in your network. It hands
Fennibi short-lived app tokens (valid for about 60 to 90 minutes): with every request from the
bundle, and for a due scheduled run when it asks for one, outbound. The consequence: a schedule
runs only while the bundle runs. If the broker is down, the run ends after 30 minutes without a
charge as "access at the customer not reachable". As with a service principal, row-level
security does not apply to the app. Setup in section 5.3.
- No lasting access (Delegated, only while signed in). Nothing is stored anywhere. Fennibi
works only while a person is signed in in the browser, and schedules pause. This fits trying
Fennibi out without an installation.
Standard reports
Standard reports run centrally, on a schedule or by hand, and every reader of the account sees
the same frozen result. They therefore always run under a fixed identity, also when a person
starts them: the service principal, or in the modes Delegated and Delegated plus personal
sign-in the stored Microsoft account. In
the mode Delegated, only while signed in there is no fixed identity. There, Fennibi refuses
them and says why.
Row-level security does not apply to the service principal. In that case, only include models and
measures in standard reports whose content every user of your Fennibi account may see.
Under a stored Microsoft account, its role in the workspace decides:
- Admin, Member or Contributor: RLS and OLS do not apply to this account. Every reader sees
unfiltered data, including from areas protected by RLS.
- Viewer: RLS and OLS apply. The report shows only this account's slice and still looks like
the full picture.
Fennibi does not distinguish between models with and without RLS here. Choosing the account is
your responsibility. Which account is connected is shown on the Fabric connection page. If
another account connects, approved reports stay approved, and their figures may change. If the
account's token expires, the runs stop until someone sets up the connection again. Anything that
should run under the person asking belongs in an own report in the live chat.
3. Setting up the delegated connection
This section applies to Delegated, to Delegated plus personal sign-in (section 3.5), to
Delegated, only while signed in (section 4) and to the personal sign-in of Service principal
plus personal sign-in (section 5). All of them use SemaDoc's Entra application, so one
approval covers them all.
If your tenant does not allow users to consent to applications themselves, the sign-in stops
with "Need admin approval". The steps below approve the SemaDoc application only and limit
who may use it.
3.1 What you are approving
SemaDoc's application requests delegated permissions only. Under them it always acts as the
signed-in user, never under an identity of its own, and sees only the workspaces and semantic
models that user can already see. Row-level security applies.
The application gets no write permission, no admin permission and no application
permission. Microsoft enforces these limits on every token: Fennibi cannot change, delete or
refresh a semantic model, cannot reach a workspace the signed-in user cannot reach, and has
no access to mail, files or other Microsoft 365 data. Every call Fennibi makes is either a
list of workspaces, semantic models, reports or refreshes or a read-only DAX query.
3.2 Approve Fennibi proactively (recommended)
You can approve Fennibi before anyone in your organization tries to connect. Open this link and
sign in as an administrator. It needs no tenant ID, because Microsoft takes the tenant from your
sign-in:
https://login.microsoftonline.com/organizations/adminconsent?client_id=5f3da981-a67d-4650-a539-4d5b0d8b5f76&redirect_uri=https://semadoc.io/en/entra-consent-done
- Microsoft shows the permission list from section 3.1. Check it and click Accept.
- Microsoft then takes you to a confirmation page on fennibi.com. It tells you whether the
consent was recorded and shows Microsoft's error message if it was not.
Your tenant now has an enterprise application for exactly this client ID, holding exactly
the permissions from section 3.1. Your user consent policy stays unchanged, so users still
cannot consent to any other application.
Check: open https://portal.azure.com/ → search for Microsoft Entra ID → Manage →
Enterprise applications → All applications → search for
5f3da981-a67d-4650-a539-4d5b0d8b5f76 → Security → Permissions. The tab Admin consent
lists the permissions from section 3.1.
Why there is no "add app" button in the portal: the Azure portal only shows applications
that already exist in your tenant. A third-party application appears there the moment its
consent is first granted, so the very first approval goes through the link above or through
a user request (section 3.3). Everything after that is done in the portal.
3.3 Alternative: let users request approval
If you prefer to approve on demand, users can send you a request when they connect:
- https://portal.azure.com/ → Microsoft Entra ID → Enterprise applications →
Security → Consent and permissions → Admin consent settings:
- Users can request admin consent to apps they are unable to consent to → Yes
- Who can review admin consent requests → add yourself or your admin group
- Save
- The user clicks Connect with Microsoft on fennibi.com, sees "Approval required", enters a
short justification and clicks Request approval.
- You receive an e-mail, or open Enterprise applications → Activity → Admin consent
requests. Open the request for SemaDoc, click Review permissions and consent, compare
the list with section 3.1 and click Accept.
The result is the same as in section 3.2.
3.4 Limit who may use Fennibi (recommended)
After approval, every user in your tenant could sign in to Fennibi. To allow specific people
only:
- https://portal.azure.com/ → Microsoft Entra ID → Enterprise applications →
All applications → open the SemaDoc application (search for the client ID).
- Manage → Properties → Assignment required? = Yes → Save.
- Manage → Users and groups → Add user/group → assign the users or, preferably, a
security group (e.g.
Fennibi Users).
Microsoft now rejects users who are not assigned at sign-in (error AADSTS50105), before
Fennibi is ever reached. To remove someone's access, remove them from the assignment or the
group.
Optional — Conditional Access: Microsoft Entra ID → Security → Conditional Access →
new policy whose Target resources is the SemaDoc application only, for example to require
MFA or a compliant device, or to limit how long a connection stays valid (section 8).
3.5 Delegated plus personal sign-in
Use this mode on Pro workspaces when row-level security has to apply in the chat. The
documentation runs under one stored Microsoft connection, as in Delegated, and every person asks
their questions under their own identity:
- Approve the SemaDoc application as in section 3.2 or 3.3, and limit it to the connecting
user and the chat users (section 3.4). One approval covers both sign-ins.
- The person whose permissions the documentation should use chooses Delegated plus personal
sign-in on the Fabric connection page and clicks Connect with Microsoft. The mode becomes
active only when this sign-in succeeds. Fennibi takes your tenant from it, so nobody enters a
tenant ID. This person needs semantic model admin rights for the documentation (section 7), so
RLS does not apply to them. An account that is already connected in Delegated switches by
saving: the stored connection, the model links and the schedules stay.
- Chat users click Sign in with Microsoft at the top right before they ask a question. The
sign-in works as in section 4, against the tenant of the stored connection: the token stays in
their browser tab, and Fennibi stores nothing for them.
What runs under which identity:
There is no fallback in either direction. A live question without a sign-in is refused, never
answered under the stored connection, which as an admin of the model would see past RLS. A
documentation run never uses a person's token. Each person sees only their own chats, reports and
measurement runs.
4. Setting up "Delegated, only while signed in"
This mode is for organizations that want Fennibi to reach their tenant only while a person is
at the screen. Approve the SemaDoc application as in section 3 first. Then:
- The user chooses Delegated, only while signed in on the Fabric connection page, enters
your tenant ID (a GUID, from Microsoft Entra ID → Overview → Tenant ID) and clicks
Sign in with Microsoft next to it. That saves the connection; Fennibi deletes any refresh
token it held for this account.
- Each later time they work with Fennibi, they click the Microsoft sign-in at the top right.
The sign-in runs in their own browser against your tenant, with Microsoft's normal rules for
MFA and Conditional Access.
- The access token stays in that browser tab until the tab is closed or the token expires after
about an hour, so the user stays signed in when they open another page or reload. It is kept
in the tab's session storage, never in a cookie or in storage that outlives the tab, and
Fennibi's servers store nothing. The refresh token never leaves the memory of the page it was
issued on. Once the kept token has expired, the tab signs in again without a prompt
(
prompt=none) against the user's existing Microsoft session: a short redirect to Microsoft
and back, about once an hour. If Microsoft needs the user for it (session expired, MFA due,
several accounts), the tab stays signed out until the user signs in again. Signing out of
Fennibi or of Microsoft in the header, or a token Fennibi rejects, removes the token from the
tab at once.
- Every live question carries the token with the request. Fennibi
uses it for that request and stores it nowhere.
- A documentation run the user starts receives the token sealed for that one run and deletes
it when the run ends, also when the run fails. A run that outlasts the token (about one hour)
stops and asks the user to sign in again.
In this mode, documentation runs read no sample values from your data, and every person in a
Fennibi account sees only their own chats and reports, because each works under their own
identity. Schedules are paused, runs through the API and standard reports are refused, because
nobody is signed in for them.
In the Entra sign-in logs you see each sign-in as an interactive sign-in of that user.
5. Setting up a service principal
With delegated permissions, Microsoft cannot limit Fennibi to particular workspaces. Fennibi can
reach everything the signed-in user can reach. With a service principal of your own, you
choose the workspaces yourself.
5.1 Service principal
In the Azure portal: create the app registration and its secret
- Open https://portal.azure.com/ → search for Microsoft Entra ID → Manage →
App registrations → New registration.
- Fill in the form and click Register:
- Name: a name you will recognize later, e.g.
Fennibi documentation
- Supported account types: Accounts in this organizational directory only (single
tenant)
- Redirect URI: leave empty. The service principal signs in with its secret, without a
browser.
- On the Overview page of the new registration, copy the Application (client) ID and the
Directory (tenant) ID. You enter both on fennibi.com in step 9.
- Manage → Certificates & secrets → tab Client secrets → New client secret. Enter a
description (e.g.
fennibi.com), choose an expiry and click Add.
- Copy the secret's Value right away — not the Secret ID next to it. The portal shows the
value only now and hides it once you leave the page. Note the expiry date: when the secret
expires, Fennibi can no longer sign in, and documentation runs stop until you enter a new one.
- Leave API permissions as they are. A service principal gets its Power BI access from the
tenant setting (section 6) and its workspace roles (step 8), not from API permissions on the
app registration.
In the Azure portal: put the service principal into a security group
- Microsoft Entra ID → Manage → Groups → New group:
- Group type: Security
- Group name: e.g.
Fennibi service principals
- Members → No members selected → search for the name from step 2 → Select
- Create
In Power BI
- In the Power BI admin portal, enable Service principals can use Fabric APIs for this
group only (section 6). A change to a tenant setting can take up to 15 minutes to apply.
Then open each workspace Fennibi should document → Manage access → Add people or
groups → search for the name from step 2 → role Contributor → Add. Add it only
to these workspaces. Contributor is needed to read a model's structure (section 7).
On fennibi.com
- Choose Account → Configuration → Fabric connection → Service principal and enter the tenant
ID, the client ID (both from step 3) and the secret value (step 5). Fennibi stores the secret
encrypted.
You own the credential: you rotate the secret, and you remove access by deleting the secret, the
app registration or its workspace membership. The service principal does not depend on any one
employee, so it keeps working when a person leaves.
Row-level security does not apply in this mode, because the service principal is not a
person. Every chat user of your Fennibi account sees the data the service principal sees, and
none of them needs a Power BI licence for it.
5.2 Service principal plus personal sign-in
Use this mode if the documentation should run under a service principal and the live chat under
each person's own identity, with their RLS roles:
- Set up the service principal as in section 5.1, steps 1 to 8.
- Approve the SemaDoc application for the chat users as in section 3, and limit it to them
(section 3.4).
- On fennibi.com choose Service principal plus personal sign-in and enter the tenant ID,
client ID and secret. Switching from Service principal keeps the secret, the model links
and the schedules.
- Chat users click Sign in with Microsoft at the top right before they ask a question. The
sign-in works as in section 4: the token stays in their browser tab, and Fennibi stores
nothing.
What runs under which identity:
There is no fallback in either direction. A live question without a sign-in is refused, not
answered under the service principal, and a documentation run never uses a person's token.
5.3 Access stays with you (standalone bundle)
Use this mode when no secret of your tenant shall lie at Fennibi and you run the standalone
bundle in your network:
- Set up the app registration as in section 5.1, steps 1 to 8. Do not enter the client
secret on fennibi.com; enter it only in the
.env.standalone file of your bundle.
- On fennibi.com, choose Access stays with you (standalone bundle) and enter the tenant id and
the client id. A secret sent along is refused, and switching from a service-principal mode
deletes the one stored there.
- Under Profile → API key, create a key in mode Token broker. It can only read waiting
scheduled runs and hand them a token. It cannot read models or chat.
- Start the token broker in the bundle. The steps are in the bundle's README.
Fennibi checks every token before it sends a query: signature, tenant, app, the Power BI
audience and that it is an app token. A token of a foreign tenant or a foreign app never serves
your account. A token the broker hands for a scheduled run stays at Fennibi only while that run
lasts.
6. Power BI tenant settings
Open https://app.powerbi.com/ → gear icon → Admin portal → Tenant settings. Enable
these settings, either for the entire organization or for a security group that contains the
identities Fennibi works under:
The two integration settings are enabled by default in Power BI. You only need to act if
your organization has turned them off. Note that they apply to every tool, not only to Fennibi.
What is not needed: no XMLA read/write setting on a capacity and no XMLA connection of your
own. Fennibi does not connect to the XMLA endpoint itself. It only calls the Power BI REST API.
The exception concerns the capacity itself: the documentation under a service principal requires
a workspace on a Fabric or Premium capacity. On Pro workspaces, use the mode Delegated or
Delegated plus personal sign-in for it (section 2).
7. Permissions and licences
Fennibi can never do more than the identity it works under. What that identity needs depends on
the feature:
Some optional structure queries may additionally require the Admin role on the workspace. If
the identity lacks it, Fennibi skips that part, notes it in the run report and continues.
Further prerequisites for a person who connects or signs in:
A Power BI licence cannot be assigned to a service principal, and a person's licence does not
apply to it. The condition therefore sits on the workspace: the documentation under a service
principal requires a Fabric or Premium capacity, and on Pro workspaces it fails in our tests
(section 2).
8. When Fennibi accesses your tenant
In the modes Delegated and Delegated plus personal sign-in, offline_access means that
Fennibi keeps a refresh token for the connecting user, encrypted at rest and never written to a log. Fennibi also stores that user's
sign-in name, encrypted in the same way, so that the Fabric connection page shows whose
permissions apply. Logging out of fennibi.com does
not delete it. Only ending the connection does (section 9). In the service-principal modes,
Fennibi keeps your client secret instead, encrypted in the same way.
Fennibi accesses your tenant in these cases:
Nothing else runs in the background. You do not have to take our word for it:
- Fennibi's own access log on the page Fabric access (link View Fabric access on the
page Fabric connection) lists every access to your tenant:
when, on whose trigger, for what purpose, under which identity and with how many Power BI calls.
It holds no queries, values or tokens and keeps 90 days, so you can match it line by line
against the two Microsoft logs below.
- Microsoft Entra sign-in logs → Non-interactive user sign-ins, filtered on application
5f3da981-a67d-4650-a539-4d5b0d8b5f76, list every time Fennibi renews a user's token. Sign-ins
of your service principal appear under Service principal sign-ins, filtered on its client ID.
- The Power BI activity log (Microsoft Purview audit) lists every query Fennibi runs under
that user or service principal.
- A Conditional Access policy with Session → Sign-in frequency for the SemaDoc application
limits how long a delegated connection stays valid. After that period the user must sign in
again, and scheduled documentation updates pause until they do.
If you do not want Fennibi to hold a token for a person at all, choose Delegated, only while
signed in (section 4) or one of the service-principal modes (section 5).
9. Revoking access
Every option below takes effect at Fennibi's next request.
SemaDoc's application (delegated modes and the personal sign-in): under
https://portal.azure.com/ → Microsoft Entra ID → Enterprise applications → SemaDoc:
- One user: Users and groups → remove the assignment.
- Everyone, temporarily: Properties → Enabled for users to sign in? = No.
- Everyone, permanently: Properties → Delete. This removes the consent and makes every
refresh token that Fennibi holds for your tenant invalid.
Your service principal: delete its client secret or the app registration, or remove it from
a workspace to take just that workspace away.
On fennibi.com, a user can end a delegated connection at any time under Account → Configuration
→ Fabric connection → Disconnect. Fennibi then deletes the stored refresh token and sign-in name. Switching the
connection to a delegated mode deletes a stored client secret. Deleting the Fennibi account
deletes both. Where Fennibi only holds a token in the browser tab, there is nothing to delete:
access ends when the user signs out or closes the tab.
Tags: Power BI, Microsoft Entra ID, Admin consent, Service principal, Row-level security, Security, Semantic Model