Invitation accepted – now what? Why guests in Microsoft 365 need a starting point

Don't worry, this isn't about visitors at the front desk or guests at a backyard barbecue. We're talking about suppliers, partners, consultants and customers who work with your team inside your Microsoft 365 tenant.

The story usually goes like this: An employee adds an external contact to a team, or the invitation goes through a well-defined process, or someone quickly clicks through the Entra admin center thinking: "Eh, that'll do."

The invitation email arrives, the guest clicks "Accept", signs in, and a few seconds later they've arrived in your Microsoft 365 environment. Technically, at least, because this is exactly where the confusion really starts for many guests.

The first few seconds matter more than you'd think

The invitation process itself has become remarkably mature. Microsoft has put serious work into it over the past few years. The trouble shows up somewhere else: the question of where the guest actually lands.

More often than not, they end up somewhere between MyApps, an account picker, and the start page of their own tenant. Nowhere does it say "Welcome to Contoso, here's where you start." Instead, the guest is looking at app tiles and contexts that mostly send one message: "You'll figure it out somehow."

The people who send the invitation, or who later act as sponsors, are often completely unaware of this moment. If you work at a large company and rarely, if ever, are a guest in someone else's tenant, you never experience this kind of cluelessness first-hand. From the other side of the fence, a lot of things look far less self-explanatory. That's why improvements at exactly this point tend to be underestimated.

MyApps is a good example: in many organizations, the portal is barely curated. Guests see applications they do not need or are not even allowed to open. That's not a welcome, it's a toolbox without labels. A prominent link from there to the actual guest start page makes sense. But MyApps itself is not that start page.

Seasoned Microsoft 365 users shrug this off with a sigh. But anyone who doesn't hop between tenants every day the way other people switch browser tabs simply loses their bearings. And then they fall back on the very channel everyone wanted to move away from: email.

Why guests take the wrong turn so reliably

This has little to do with guests being careless; the problem is structural.

Microsoft 365 is a multi-tenant platform. When a guest opens a link, the client must decide which tenant to take them to. If there's already an active session in the user's home tenant, that context often takes precedence. As a result, when the guest clicks a Microsoft Teams link, they may, in the best case, end up in the wrong Teams tenant. In the worst case, they may not land in a usable Teams context at all. Microsoft itself documents that guest features in MS Teams only become available once the guest is a member of at least one team. Until then, the very step that makes your tenant visible to this guest in MS Teams is often missing. So, the channel exists but, from the guest's point of view, the link still leads nowhere. What happens next is all too familiar: a support ticket, a question to the project lead, a message to whoever sent the invite back then, or simply a retreat to email. A small orientation problem ends up creating work on several sides at once.

The pragmatic fix: a start page for guests

The good news first: you don't need heavy artillery for this problem.

A well-built SharePoint start page for guests does a surprising amount of work. It provides a reliable entry point, bundles the most important next steps and uses tenant-specific links to take guests straight into the right context. How exactly those URLs are built matters, but it's not the focus here.

The benefits boil down to three points:

• The page is quick to build and easy to keep up to date.

• It works from day one, even if MS Teams isn't fully usable for the guest in your tenant yet.

• It reduces support effort because it provides orientation before questions even come up.

Why the obvious alternatives rarely cut it

Other approaches look tempting at first glance, but they're rarely the better choice. Even the most carefully worded email only helps if it gets read, understood, and can still be found weeks later. Conditional Access makes access more secure, but not easier to navigate. And home-grown redirect apps or elaborate custom solutions may solve the problem in theory, but they usually create more operational overhead than the actual pain justifies.

If invitations are managed centrally, redirecting guests to the start page should be a built-in part of the process. If guests are invited ad hoc through MS Teams or SharePoint, however, the one moment where a clear signpost would help most goes to waste. In terms of immediate usability, things often work exactly as Microsoft intended: the team membership is there, and the guest can get started in MS Teams right away. The price, though, is often weaker governance, because this kind of access is created in a decentralized way and more or less in passing.

Solutions like EasyLife 365 Collaboration can also round up these spontaneously created guest accounts after the fact and bring them into managed processes. For the sponsor, however, that often means doing the work twice: first the quick setup, then the proper cleanup. That's why self-service offerings really shine where sponsors can stay in their familiar work environment instead of having to switch to a central request or ticketing system.

Secure, without adding friction

When it comes to security, the picture is clearer than it might seem at first: multi-factor authentication for guests makes sense. But in many cases, there's no need to force guests to register additional methods in your own tenant. Trusting the MFA from their home tenant is often the more practical route: just as secure, with far less friction.

What belongs on a page like this

At Workoho, this page is often called the Entrance Area. Not a "dashboard", not a "portal", and certainly not an "intranet site for externals". Simply the place where a guest instantly knows: “I'm in the right place and here's what comes next.”

Orientation beats completeness

A good guest start page doesn't need to show everything. Above all, it needs to be clear:

• A short welcome with context: who sent the invitation, and what is the collaboration about?

• One clear first step instead of an endless list of twenty links

• A curated selection of the few tools and resources that are genuinely needed in the first week

• Links for self-service and transparency, such as the guest account, terms of use, security information or leaving the organization

• Current notices or news, so a second visit is worth it too

• A real contact person with a name and a way to reach them, not an anonymous shared mailbox

Findability, look and language

A few design decisions have more impact than you'd expect:

• The page should be easy to find again, ideally through a memorable address or even the tenant's SharePoint root site, for example https://contoso.sharepoint.com.

• A consistent look pays off. Logo, navigation, colors, and a visible company name instantly answer the question: whose environment have I landed in?

• For internationally operating companies, English as the default language of the site collection is usually the safest foundation. Additional language versions at page level are still highly recommended.

• Audience targeting is worth it, so not everyone gets the same view. A finer distinction often makes sense, for example between internal employees, regular guests and partners with their own .ext account, who often use several accounts in parallel while staying on their own employer's devices.

Bottom line: the page isn't meant to impress; it's meant to orient. If a guest knows within two minutes where they are, what to do next and who to ask, the page has done its job.

Small detail, big impact: showing the sponsor

At the latest when something goes wrong, guests ask themselves a very simple question: who do I turn to now?

The invitation email usually doesn't come completely out of the blue. There's often been prior contact, some coordination, or at least a heads-up that an invitation is on its way. So, the guest frequently knows the inviter's name.

Later on, though, the email is only of limited help. It mainly tells you who clicked "Invite" on a particular day, not who is responsible today. Maybe the invitation came from a process, maybe it was delegated internally, maybe the project changed hands, or the person no longer works at the company. The email captures a moment, not reliable ownership. And yet that ownership is often already recorded in the directory: in Microsoft Entra, stored as the sponsors of the guest account. By default, however, this information isn't visible to the guest.

The Guest Sponsor Info Web Part by Workoho

This is exactly where Workoho's Guest Sponsor Info Web Part comes in. It's a free, open-source web part for SharePoint, built specifically for this purpose: guests see on their start page who their sponsors are and how to reach them. The web part reads the Entra profile of the guest currently visiting the page, determines their current sponsors, and automatically displays names, roles, and contact details. No per-guest maintenance, no manually kept contact lists, no copying names into page text. If several sponsors are assigned, the guest sees everyone responsible and can decide for themselves whom to contact.

If the web part is also configured to show the sponsors' managers, the guest at least sees their names and gets a better sense of which part of the organization they're working with. For privacy reasons, direct contact details of those managers remain hidden.

How reliable this assignment is in day-to-day practice, however, doesn't depend on the web part, but on the governance process behind it. The web part becomes especially valuable where guests would otherwise be stuck in a gray zone: when MS Teams isn't available to them in the tenant yet. The web part can detect this state and handle chat or call features accordingly, instead of letting guests happily click buttons that would currently lead nowhere. And because the web part works best when the page around it is well built too, Workoho has put together a dedicated ideas page with suitable building blocks, deep-link patterns, and self-service links: Landing Page Ideas

More about the Guest Sponsor Info Web Part: Guest Sponsor Info

Sponsors help, but they don't maintain themselves

The sponsor entry in Entra is valuable, but it doesn't update itself. With many invitation paths, the inviting person is simply set as the first sponsor. That's a usable starting point, but it's no substitute for a proper process for maintenance, handover, and backup.

The model usually only becomes robust when at least two sponsors are defined right at invitation time: a primary contact and a named backup. There's no built-in mechanism that keeps track when a sponsor changes departments, leaves the company or hands over responsibility. And while five sponsors on one guest account may sound great on paper, it feels different in practice: when lots of people are responsible, often nobody really feels responsible in the end.

With Microsoft Entra ID Governance, Microsoft does offer tools for access reviews and entitlement management. Functionally, that's strong, but organizationally and in terms of licensing, it's quite a high barrier for many mid-sized companies. EasyLife 365 Collaboration goes far beyond plain guest management. The solution brings guests, resources, and governance together in a single model and also manages the different types of Microsoft 365 groups, such as Teams, SharePoint team sites, and similar collaboration spaces, rather than in isolation from one another. Sponsors can be set up properly at invitation time and then maintained along with backups, reviews, and lifecycle rules. This turns the sponsor displayed on the start page into a reliable process rather than just a nice visual.

Workoho is a Platinum Partner for EasyLife 365 and brings hands-on experience from implementation and ongoing development. In a nutshell: EasyLife 365 takes care of governance inside the organization, and the Guest Sponsor Info Web Part makes it visible to guests.

Read more about EasyLife 365 Collaboration or directly book a product demo with Workoho.

And then there are the .ext accounts

A classic stumbling block for this kind of governance is the well-known .ext account. As soon as they come into play, the question arises: is a well-managed guest account enough, or does this partner need an additional internal account for externals after all, with its own license and extended permissions?

Depending on the company, these accounts are called .ext, vendor, partner or something else entirely. They aren't wrong per se but, it gets problematic when they become the norm out of habit or don't really belong to anyone organizationally. For employees, HR provides a clear trigger at some point. For partner accounts, that trigger is often missing. Extensions then get rubber-stamped in batches at long intervals, even though hardly anyone is close enough to the project to weed things out properly. And when the person left the partner company long ago, the customer side doesn't reliably find out.

A good guest governance process provides the basis for these decisions and brings responsibility back to where the collaboration actually happens. It makes it clearer which collaborations can get by with guest access, which resources depend on them, and where, by exception, more is needed. And if an .ext account really is required, it too should be tied to clear rules, reviews, and a real lifecycle instead of just running along indefinitely.

On this foundation, you can manage not only the guests themselves but also the associated resources and sharing permissions systematically. The real leverage often only becomes visible afterwards: anyone who builds further processes on top of it, or aligns existing ones with it, can cut unnecessary licenses and accounts while improving security at the same time. It's rare for the same steps to both save money and reduce risk. Here, that's often exactly what happens. So, the guest start page isn't just a friendly entry point, it's the visible tip of a much bigger topic.

More than a matter of usability

A good start page for guests isn't just about convenience, it's about governance too.

When guests set off without guidance, they quickly end up in the wrong places: personal OneDrives as makeshift project storage, informal Teams chats instead of structured channels, or external tools outside of any policy. A clear start page steers those first steps in the right direction. At the same time, it sends a message to the outside world: at this company, external collaboration is planned, guided, and taken seriously, not improvised.

Sound familiar?

This is exactly the kind of challenge Workoho helps with. As a Platinum Partner for EasyLife 365, the team works with IT departments that don't just want to allow external collaboration but want to design it well: transparent, practical and without unnecessary overhead.

"Hand over the slides and disappear" isn't Workoho's style. The team sees itself more as mountain guides: assessing the situation, planning the route, heading out together, adjusting along the way, and, in the end, making sure customers can safely walk the path on their own in the future. If an external IT service provider is also involved, that's no obstacle, it's usually just part of reality.

If your guests often ask something along the lines of "I've accepted the invitation. Now what?", that's not a side issue. It's time for a pragmatic conversation, for example with Workoho.