Supervised pilot
A supervised pilot on your own customers, scoped and costed before any tenant is connected.
The pilot runs Impactfold on a few customers you choose, alongside the way your team checks today, so you can judge from real evidence whether it saves work and whether you trust its results.
What you get from it
For every customer in scope, a result you can check against your own: Affected with the evidence, Safe for this change with what was read, or Unknown with the reason. Where something is Affected, the complete path through remediation to a verified closure. At the end, a written account of every scan, every state change and the audit trail behind them.
A pilot may find nothing to fix. Whether any customer is Affected depends on your customers' environments, not on the pilot. A complete, evidence-backed Safe is also a useful result.
Who it fits best
IT service providers that manage Microsoft 365 for many customer organizations, with engineers who triage vendor changes customer by customer. The fit is strongest from roughly 25 customer tenants, where checking by hand costs the most.
Smaller providers are welcome where the need is real: several customers with mailbox integrations, a customer already asking about EWS, or a change you cannot check by hand in time. Tell us about it in the form.
What it cannot cover yet
- Other vendors
- Only Microsoft 365 has a connector today.
- Other Microsoft checks
- The one validated check is EWS application consent.
- National clouds
- GCC, GCC High, DoD and 21Vianet tenants are not supported.
- Changes made for you
- Impactfold never writes to a tenant. Your engineers make the change; a scan verifies it.
Scope
- Customers
- A small set you choose, each connected only with its own administrator's consent. More can follow once you trust the results.
- Check
- EWS application consent in Microsoft 365, including Microsoft's phased EWS disablement in Exchange Online from 1 October 2026.
- Access
- Application-only and read-only. The permissions are listed on the security page.
- Working mode
- Your engineers compare Impactfold's results with their own checks. Impactfold creates no tickets and sends nothing to your customers.
What you provide
- One named person to operate the workspace and review the rule, usually a senior engineer, with a Microsoft work account.
- For each customer in scope, an administrator who can grant tenant-wide consent from a link.
- An engineer to act on any Affected finding, so the verification step is real.
- Your own check of the same customers, and honest feedback where the results differ.
What Advina Labs provides
- The deployment and its Microsoft connector registration, configured for your workspace, or support for running it on your own host.
- The rule, with a written account of what it detects and what it cannot.
- The person who wrote the rule, on the call for the first consent, the first finding and the first verified closure.
- A written account at the end, including every disagreement with your own checks.
Onboarding
Two to three working days to a first customer result, once the starting point is in place.
The starting point: the pilot agreement is signed, and your deployment is running with its connector registration. Setting that up comes first; how long it takes depends on where the deployment runs, and it is agreed with you.
Inputs needed on day 1
- Your operator, available to sign in and set up the workspace.
- The first customer's Microsoft 365 tenant name or ID.
- That customer's administrator, available to review and approve the consent request.
Then
Day 1: connect
Operator signs in, workspace created with no sample data, consent link sent, connection verified.
Day 2: first scan
Your operator reviews and approves the rule version. The first customer scan records a result with its evidence.
After that: fix and verify
If a finding is Affected, your engineer makes the change and a verifying scan closes it. Repeat for each customer in scope.
These durations assume people are available when needed. Waiting on an administrator's consent, on Microsoft, or on DNS and certificates takes longer than the product's own steps, so they are a plan, not a guarantee.
Commercial terms
Agreed in writing before any customer tenant is connected.
Scope, duration and total cost, including any hosting cost, are agreed in a written pilot agreement before any customer tenant is connected. Sending an enquiry or having a first conversation creates no charge and no commitment.
Request a pilot
Ask for a first conversation.
Only your name, work email and company are required. The reply comes from vivek@theimpactfold.com, normally within one business day.