Troubles installing Waldo? It might be a permissions thing

Applicable plans: ❎ The free plan, ❎ The complete plan

When you first try to use Waldo in Microsoft 365, you might run into a few speed bumps — all depending on how your organization has set up app permissions and policies.

This guide shows you what to expect, what you'll see, and who to contact to get things moving. 💡

1. Waldo is listed, but not available in the Teams app store

What you see:
You search for Waldo in Teams, and the button says Request approval instead of Add.

Why it happens:
Your company’s Teams policies block or filter third-party apps.

Who to contact:
Your Microsoft 365 Administrator or Teams Administrator.
If you click Request approval, they’ll see it marked as “Requested” in the Teams Admin Portal.

2. User consent is disabled

What you see:
You try to access Waldo, and a pop-up asks for permissions — but you can’t continue.

or
 

Why it happens:
Your organization doesn’t allow users to grant app permissions themselves.

Who to contact:
Your Microsoft 365 Administrator or Azure Identity Administrator.

3. You see “Need admin approval”

What you see:
You try to log in to Waldo, and you hit a screen saying:
“Need admin approval – Waldo requires permission to access your organization’s resources.”

Why it happens:
Only administrators can approve those permissions — and you’re not one.

Who to contact:
Your Microsoft 365 Global Administrator.

4. You’re not assigned to the Waldo app

What you see:
You see Waldo in your app list and try to log in. You click Let the magic begin!… but nothing happens.

Why it happens:
Your organization uses Azure Entra (formerly Azure AD) and requires user assignment.
You haven't been assigned to Waldo yet.

Who to contact:
Your Azure Identity Administrator.

5. You can’t access the Waldo admin portal

What you see:
You try to open admin.hellowaldo.app but get blocked.

Why it happens:
Waldo is already installed and managed by someone in your company. There’s only one configuration per tenant.

Who to contact:
Ask your existing Waldo admin(s) — they’re listed on the admin portal.

🧭 Key Takeaway

Most blocks come down to one of these three things:

• 🔐 Org-wide security or consent policies
• 🧑‍💼 Admin-only permissions
• 🧩 Waldo is already installed by someone else in your company

Here’s a quick cheat sheet:

👉 Now you not only know what’s happening — you know who can help fix it.

Let me know if you’d like to add visuals or screenshots — but if there are many, we may want to split them into a separate article for easier maintenance.