Skip to content
New Dailybot 3 is live. Read the launch
Troubleshooting microsoft-teams Admin it-admin Member

Microsoft Teams login issues with Dailybot (sign-in loops, tenant errors, admin consent)

Microsoft Teams login issues with Dailybot (sign-in loops, tenant errors, admin consent)

Microsoft Teams sign-in has more failure modes than the other chat platforms because of tenant policies, conditional access, and the Azure AD / Entra ID consent flow. Almost every “can’t log in” ticket falls in one of the buckets below.

Quick triage

What you see Go here
“Need admin approval” / “admin consent required” Admin consent
Sign-in loops back to login without an error Sign-in loop
AADSTS50105 / AADSTS65001 / AADSTS70001 Tenant errors
Multiple tenants and the wrong one is picked Multiple tenants
Dailybot disappeared from Teams entirely Dailybot disappeared

By default, Microsoft tenants require an administrator to approve third-party apps that ask for tenant-wide access. If you saw “Need admin approval” and you are not an admin:

  1. Send your tenant admin (IT / Microsoft 365 admin) the install link for Dailybot.
  2. Ask them to consent on behalf of the tenant.
  3. Once consented, you can sign in normally.

If you are the admin:

  1. Sign in to admin.microsoft.com or the Entra admin center.
  2. Open Enterprise applications -> search Dailybot.
  3. Grant consent (or use the Grant admin consent for your-tenant button on the app permission page).
  4. Make sure users can sign in (it is not blocked) and the app is in the right group assignment.

Sign-in loop

Symptoms: clicking “Sign in with Microsoft” returns you to the login screen with no error.

Common causes:

Cause Fix
Third-party cookies blocked Allow cookies for dailybot.com and microsoftonline.com.
Browser extension blocking OAuth Try incognito; disable privacy extensions.
Wrong Microsoft account active in your browser Sign out of all Microsoft accounts, then sign in only with the work one.
Cached Teams token expired Sign out of Teams, sign back in, then retry Dailybot.

If the loop persists in Chrome incognito on a clean profile, escalate to support with timing and screenshots.

Tenant or conditional access error

Common AADSTS codes:

Code What it usually means
AADSTS50105 User is not assigned a role for the app – assign Dailybot to the user / group in Entra.
AADSTS65001 User has not consented (or admin consent is needed) – see Admin consent.
AADSTS70001 App not found in tenant – the Dailybot app is not registered in this tenant, install it from the Teams app store first.
AADSTS530003 Device not compliant with conditional access – contact IT.
AADSTS50020 User account is in a different tenant – use the correct work account.

Share the full error code and message with your IT admin; they can resolve all of these in the Entra admin center.

Multiple tenants

If your Microsoft account is invited to several tenants (employer + customer + consulting client), Microsoft may sign you in to the wrong one.

  1. Sign out of Microsoft everywhere.
  2. Open Dailybot at https://app.dailybot.com/.
  3. Click Sign in with Microsoft.
  4. Pick the correct work account matching the org where Dailybot is installed.

If you are using the Teams desktop client, the active tenant is the one currently selected in Teams’ top bar – switch tenants in Teams first, then open the Dailybot tab.

Dailybot disappeared from Teams

Possible reasons:

  • A tenant admin removed the app from approved apps.
  • A team admin removed the Dailybot tab/bot from a specific team.
  • A change in app permission policy in Teams admin center hid Dailybot from users.

To restore:

  1. Admin: open the Microsoft Teams admin center -> Manage apps -> search Dailybot.
  2. Confirm the app status is Allowed.
  3. Check App permission policies assigned to users include Dailybot.
  4. Check App setup policies – you can pin Dailybot for users.
  5. Ask the member to re-add Dailybot from the Teams app store.

Resetting the connection completely

If nothing else works, disconnect and reconnect:

  1. Admin removes Dailybot from the Microsoft Teams admin center (or the user removes it from their Teams sidebar).
  2. Wait a few minutes for revocation to propagate.
  3. Re-install Dailybot from the Teams app store or the Microsoft Teams setup guide.
  4. Sign in fresh.

See Disconnect and reconnect for the generic version.

When to escalate to support

Include:

  • Tenant name (domain) and admin contact.
  • Exact error code if one is shown (AADSTS...).
  • Whether the issue affects only you or many users.
  • Whether other third-party Teams apps work (rules out tenant-wide block).
  • Screenshots of the error and the browser URL bar.

Then contact Dailybot support from Help / Contact in the product or on the website.