The Docs Now Ask Who You Are

August 14, 2026 · InfraScout Team

The product documentation now asks you to sign in with a Microsoft work or school account. If you followed a bookmark or a search result and landed on a Microsoft sign-in page instead of the page you wanted, that is what happened, and this post is the short version of how to get through it.

The blog you are reading stays open, as does the documentation home page and everything on www.infrascout.cloud. Only the documentation itself is gated.

Getting in

Any Microsoft Entra ID work or school account works, from any organization. There is no allowlist, no invitation, and no license check — if you sign in to Microsoft 365 at work, you can read the documentation, whether or not you are a customer yet.

You authenticate on Microsoft's own sign-in page, exactly as you do for any other work application, including whatever multi-factor and Conditional Access policies your organization applies. Microsoft then returns you to the page you were originally heading for.

The first time, you may see a consent prompt asking whether InfraScout may sign you in and read your basic profile. Approving it once is enough.

Personal Microsoft accounts — outlook.com, hotmail.com and the like — cannot be used. If your organization does not use Entra ID at all, write to us and we will find another way to get you the documentation.

If your organization requires administrator approval

Many tenants require an administrator to approve an application before anyone else may consent to it. If yours does, Microsoft tells you approval is needed rather than signing you in, and usually offers to send the request for you.

Your Entra ID administrator approves it once, for the whole organization, after which everyone signs in normally. The permission being requested is sign-in and basic profile, which is worth saying plainly when you forward the request.

What signing in does not do

Assessment tooling asking a security team for a tenant sign-in invites exactly one question, so here is the answer up front: the consent covers sign-in and your basic profile — your name, your email address, and the identifiers below. It reads no mail, no files, and no directory data, and it gives us no standing access to anything in your tenant.

Connecting InfraScout to a tenant so that it can actually assess it is a separate, deliberate step that an administrator performs, with permissions you review at the time. Reading the documentation is not that step and does not become it.

That distinction is why the full explanation lives on a public page rather than behind the gate it describes. An answer you can only read after signing in is not much of an answer.

What we record

Each time you sign in, we record your email address, your Entra ID user object identifier, your organization's tenant identifier, and the date and time. We keep those records for 90 days.

We do not record which pages you read, we do not use any of it for advertising or profiling, and it goes nowhere beyond our hosting provider. The full disclosure, including the legal basis, is § 3.5 of the Privacy Policy.

What we get out of it is narrow and worth stating: knowing which organizations read the documentation tells us which parts to invest in. The documentation also describes how to assess and remediate a customer's infrastructure in some detail, and we would rather it reached the people operating InfraScout than a crawler assembling a training corpus.

If you used to find the docs through Google

You will not any more. The gated pages are deliberately out of the search index — they answer with a sign-in redirect rather than content, so leaving them listed would only produce results that go nowhere.

Search inside the documentation still covers everything, once you are signed in. If you are trying to find a page you remember, that is the place to look.

If you cannot get in

Sign-in failures are almost always a tenant policy rather than a broken account. Pending administrator approval is the usual cause, followed by a Conditional Access rule that blocks applications from outside your organization.

Write to info@infrascout.cloud with the error Microsoft showed you and we will work out which one it is.