Connect Outlook & Teams to your Find Advice calendar

An administrator approves the LeadConnector app. This is a switch at organisation level. It is done once and it covers everyone, including people who join later.

Each advisor signs in as themselves and clicks Connect (Part 2). That is what actually links a diary. An administrator cannot do this on someone else’s behalf.

Copy the whole address below and replace the highlighted yourcompany.co.nz with your organisation’s Microsoft 365 domain — the part after the @ in your work email. Everything else stays exactly as it is.

• Ask Find Advice and we will send it to you already filled in for your organisation.
• Your own domain matters. It puts the approval in your directory. If an outside IT contractor opens a generic version of this link, the approval can land in their directory instead and quietly do nothing.

Sign in with an account holding one of the roles above. In a smaller firm that is often the advisor themselves — try it before assuming you need IT.

• You will know you have the right account when the screen says “Review for your organization” under “Permissions requested”. If it does not say that, this account cannot approve on behalf of everyone — use Option B or C.
• Using an outside IT provider? They must sign in with an administrator account that lives in your organisation — the sort that ends in your own domain — not their own company login. Most providers hold one for each client. Your domain is in the link precisely so a sign-in from the wrong directory is refused rather than quietly approving the app somewhere it does no good.

The screen lists seven permissions, all of them calendar or sign-in — they are set out in full further down this page. Microsoft also states plainly: “this app will get access to the specified resources for all users in your organization. No one else will be prompted to review these permissions.” That sentence is the whole point of this option. Click Accept.

• If you see anything about reading, writing or sending mail, stop and tell us — the link has been altered. The correct one asks for no mail access at all.

After you click Accept, Microsoft hands you back to LeadConnector, which will most likely show an error or a blank page. That is expected and harmless — the approval was already recorded when you clicked Accept. Do not click Accept a second time.

Go to https://entra.microsoft.com/ → Entra ID → Enterprise apps → All applications, open LeadConnector, then Permissions (under Security) → Admin consent tab. The calendar permissions should be listed there against your name. If that tab is empty, the approval did not save — run the link again.

The person follows Part 2, Step 1 until Microsoft says “Need admin approval”.

That link is on the block screen itself. Sign in with the administrator account. If the advisor is the administrator, they may simply see the approval screen instead of the block.

On the approval screen, tick “Consent on behalf of your organization” before clicking Accept. This is the step that makes it once-for-everyone instead of once-for-one-person.

• If you cannot see that tick box, stop and use Option A instead. Microsoft only shows it to a Global Administrator or Privileged Role Administrator — a Cloud Application Administrator does not get it, and accepting without it approves the app for that one person only. Everyone else stays blocked and you are back in the loop.

Go to Entra ID → Enterprise apps → Consent and permissions → Admin consent settings. Set “Users can request admin consent to apps they are unable to consent to” to Yes, choose who reviews requests, and click Save. It can take up to an hour to take effect.

• Make sure at least one reviewer also holds a role from the list above — otherwise nobody can approve.

They attempt the connection, type a short justification on the “Approval required” screen, and click Request approval. Reviewers are emailed.

Go to Entra ID → Enterprise apps → Admin consent requests (under Activity) and open the My Pending tab — actions can only be taken there, not on the “All” tab. Select LeadConnector, click Review permissions and consent, sign in, and click Accept.

• A reviewer can only act on requests raised after they were added as a reviewer. If a request predates that, have the person send a fresh one.

They are emailed that it was approved, and go back to Part 2 below. Approval does not complete the connection for them — they still click Connect once more.

On the app’s Permissions page, open the Admin consent tab. If a reviewer without a consent-granting role handled the request, it may have been denied or left pending rather than approved — and the tab will be empty.

Open LeadConnector → Properties. If Assignment required? is Yes, only assigned people can use it — add them under Users and groups → Add user/group. This is also the correct way to limit the app to a few staff rather than the whole organisation.

• Microsoft’s own note: an app that requires assignment must have its permissions consented by an administrator, even where user-consent policy would otherwise have allowed it.

Go to Enterprise apps → Consent and permissions → User consent settings. If this is set to Do not allow user consent, the sign-in step can still be refused on a fresh account even after the app itself is approved. Allowing user consent for apps from verified publishers is the usual middle ground — LeadConnector is a verified publisher.

• Careful with that middle option: it only permits permissions you have explicitly classified as low impact under Permission classifications. If the calendar permissions are not classified, it will not unblock anything on its own.
• Changing this setting only affects future sign-ins — consent already granted is unaffected.

A Conditional Access policy requiring MFA, a compliant or hybrid-joined device, or app-enforced restrictions can block the Microsoft sign-in itself — which looks identical to a consent problem. Have the person open https://mysignins.microsoft.com and look at their recent failed sign-ins for a Conditional Access failure. This is a common cause when it works for existing staff but not for a new starter.

A stale sign-in session can keep showing the old prompt. Sign out of Microsoft in that browser, then start Part 2 again.

In Find Advice, click Settings (the gear icon at the bottom-left).

Open Calendars, then click the Connections tab at the top.

Click + Add New, then Connect next to Outlook Calendar.

Sign in with your Microsoft work account and click Accept. Once your IT team has approved LeadConnector, the “Approval required” screen will not appear.

Go to Settings → My Profile and scroll to Calendar Configuration.

Click edit under Primary Calendar and set it to your Outlook calendar. This is the calendar Find Advice reads to avoid clashes, and writes new bookings into.

• Optional: add a Check for Conflicts calendar if you want a second diary checked for busy times.

In Settings → Calendars → Connections, scroll to the Video Conferencing section.

Click Add New (or Connect) next to Microsoft Teams, sign in with the same Microsoft work account, and approve.

• You can also connect it from Settings → My Profile → Video Conferencing.

Go to Settings → Calendars and click Edit on the calendar people book on.

Open the Meeting Details tab and scroll to the Team Members section.

Select the team member who has Teams connected, set their meeting location to Microsoft Teams, then click Save. A unique Teams link now generates for each new booking and is added to the calendar invite.

• Automatic Teams links work on Personal Booking, Round Robin, Collective and Service calendars.