Signing in with Microsoft
ApptiveGrid can be used with an existing Microsoft account — through the Continue with Microsoft button on the login page. No separate password is set.
For work and school accounts, your own organization's IT decides which external applications may sign people in. If that is restricted, sign-in may stop with Approval required. Nothing is wrong with your account — an approval is missing in Microsoft Entra.
This page is meant to be passed on
You can send it to your IT department as it is. The second part holds everything they need for the decision: the permissions requested, the application ID, and the path through the Microsoft Entra portal.
For users
- Open app.apptivegrid.de and choose Continue with Microsoft.
- If Approval required appears and your organization offers it, you can send the request straight from that dialog with a justification.
- If the dialog doesn't offer that, contact your IT department and pass this page along.
Once the approval is granted, other people in your organization can sign in as well, in principle. Your IT can additionally limit access to specific users or groups; if Assignment required is switched on in Microsoft Entra, sign-in works only for the people assigned there.
If instead you get Sorry, but we're having trouble signing you in with a code like AADSTS7000112, ApptiveGrid is explicitly blocked in your organization. That, too, can only be lifted there — pass this page along as well.
Always take the same route
An account created through Microsoft has no password of its own at ApptiveGrid. Always sign in using that same button. → Account and sign-in
For IT administrators
ApptiveGrid is an application for capturing, analyzing, and sharing structured data (operated by ApptiveGrid GmbH). For sign-in, it uses Microsoft Entra ID as the identity provider, via standard OpenID Connect.
The Microsoft password is never passed to ApptiveGrid. Sign-in happens entirely at Microsoft. What comes back are the OpenID Connect claims needed to identify the user: a user identifier, the name, and — where it is held in Microsoft Entra — the email address.
What is requested
| Application (client) ID | c5bf8ba8-b06b-4d90-a16b-3598f50d9950 |
| Permissions | openid, profile, email |
| Redirect URI | https://app.apptivegrid.de/auth/callback/microsoft |
| Protocol | OpenID Connect, authorization code |
These are the three standard scopes for sign-in only:
| Permission | Meaning |
|---|---|
openid | Identify and sign in the user securely |
profile | Basic profile information about the signed-in user |
email | Email address, where available from Microsoft |
This gives ApptiveGrid no access to mailboxes, files, calendars, or Teams, and no way to read or change Microsoft 365 data through Microsoft Graph.
Which message is it
There are three distinct cases, and they call for three different fixes:
| Message | Cause | Fix |
|---|---|---|
Approval required — AADSTS90094 | Administrator consent is missing | Routes 1 to 3 |
Application '…' (ApptiveGrid) is disabled — AADSTS7000112 | The entry exists, but sign-in is turned off for it | Re-enabling a disabled application |
… is not assigned to a role for the application — AADSTS50105 | Assignment required is set to Yes, but the person isn't assigned | Limiting it to certain people |
Why consent is missing
In many organizations, user consent for external applications is restricted or switched off entirely — the setting sits under Enterprise applications → Consent and permissions. Administrator consent for ApptiveGrid may then be required. In the sign-in logs, this usually shows up as AADSTS90094.
Route 1 · Approve the pending request
If someone submitted the request from the sign-in dialog, it's waiting in the Microsoft Entra admin center under Identity → Applications → Enterprise applications → Admin consent requests.
Route 2 · Grant consent directly
Enterprise applications → ApptiveGrid → Permissions → Grant admin consent for {organization}.
Route 3 · If ApptiveGrid isn't in the directory yet
If nobody has tried yet, there's no entry either. This call creates it and grants consent in one step — <tenant> being the tenant ID or the domain name:
https://login.microsoftonline.com/<tenant>/adminconsent?client_id=c5bf8ba8-b06b-4d90-a16b-3598f50d9950Re-enabling a disabled application
AADSTS7000112: Application 'c5bf8ba8-b06b-4d90-a16b-3598f50d9950' (ApptiveGrid) is disabled.
Nothing is missing here in terms of consent. ApptiveGrid is already in the directory, but sign-in is switched off for that entry. The switch:
Enterprise applications → ApptiveGrid → Properties → Enabled for users to sign-in? to Yes.
The block is a decision, not a fault
That switch doesn't move to No on its own. Check within your team whether the application was blocked deliberately — under an app governance policy, for instance — before you flip it back.
The block applies only within your own tenant. To users it looks like an outage at ApptiveGrid, even though nothing has changed outside the organization.
Limiting it to certain people
Consent initially applies to the whole organization. If only part of the workforce should use ApptiveGrid:
Enterprise applications → ApptiveGrid → Properties → Assignment required? to Yes. Then assign the intended people or groups under Users and groups.
Revoking
Enterprise applications → ApptiveGrid → Properties → Delete. Sign-in through Microsoft is blocked again immediately.
There are no costs on the Microsoft side
The clearance is a consent, not a license. ApptiveGrid's own plan is booked per Space, independently of this. → Seats
Provisioning users automatically (SCIM)
Beyond sign-in, ApptiveGrid supports SCIM: Microsoft Entra creates the user accounts in ApptiveGrid itself and keeps them current. The set of accounts then follows the organization's directory instead of being maintained by hand.
| Identity provider | Microsoft Entra ID |
| What is transferred | Users and groups |
| Available on | the Enterprise plan |
Setup happens together with us. Enquiries to support@apptivegrid.de.
Groups are not yet a permission
Organization groups that come across are shown on the person's profile. Access to a Space is still granted through roles, not through group membership.
Common questions
Can ApptiveGrid see our mailboxes or files? No. The only scopes requested are openid, profile, and email; there is no access through Microsoft Graph.
Are passwords passed to ApptiveGrid? No. Sign-in happens entirely at Microsoft. Only the sign-in confirmation and the claims identifying the user are passed on.
Does the clearance create accounts automatically? It permits sign-in. An ApptiveGrid account only comes into being once someone actually signs in.
Does this apply to personal Microsoft accounts too? No. The restriction only affects work and school accounts belonging to an Entra tenant.
Ours shows as disabled — did Microsoft do that? No. Enabled for users to sign-in is set within your own tenant, by a person or by a policy.
Can we review the clearance later? Yes. The application then sits under Enterprise applications with every permission granted, and the sign-ins appear in the sign-in log.