Informotion, a Sydney-based consultancy specializing in records management, has been named to two separate ISG 2026 Microsoft partner quadrants — a dual nod that landed on July 21 and immediately redrew the competitive map. The firm is now cited for both Azure Data Transformation and AI Services and Microsoft Productivity and Business Process Services, putting it in the ring with global integrators while spotlighting a blunt reality: enterprise AI safety begins not with a better model, but with classified, de-duplicated, and permissioned data.
The Recognition That Rewires Partner Hierarchy
The ISG Provider Lens assessments aren’t casual shout-outs. They rank providers across increasingly tangled Microsoft service categories, evaluating market presence, capabilities, customer experience, and delivery strength. Landing in one quadrant is a solid credential; landing in two that span opposite ends of the stack — from data engineering and AI plumbing to business workflow redesign — signals a credible seat at the table for any firm driving production AI.
Informotion’s placement in Azure Data Transformation and AI Services covers enterprise data platforms, analytics, AI engineering, and governance — think Microsoft Fabric, OneLake, Power BI, Azure AI Foundry, and agent architectures. The company’s signature, according to its own description, is a sequence of discovery, classification, enrichment, and remediation before a single model is trained or a Copilot prompt is tested.
The Microsoft Productivity and Business Process Services quadrant looks at how partners redesign work itself — workflow automation, knowledge management, low-code application design, and change management across Microsoft 365, Dynamics 365, and Power Platform. Here, Informotion is judged on its ability to take that scrubbed, governed information and wire it into compliant case management, agent-assisted approvals, or Power Platform apps that don’t explode the corporate risk profile.
Both quadrants have been shifting closer together for two years. Enterprise projects no longer stop at “we built a chatbot”; they demand that the bot know which SharePoint document is authoritative, run inside the right Entra ID boundary, trigger a Power Automate flow that updates Dynamics 365, and leave a defensible record trail. Few partners — and almost no boutique shops — could credibly claim both halves. Informotion just did.
What This Means for Your AI Rollout
The practical impact depends on which chair you occupy in an organization.
For business and IT leaders who are eyeing Microsoft 365 Copilot or custom agents, the message is unbending: your AI initiative is only as good as the information estate it drinks from. If a confidential strategy doc sits in a SharePoint site with outdated permissions, Copilot won’t breach the permission model — it will merely surface that doc faster, exposing a weakness that manual search had hidden. That means access reviews, content classification, and duplication cleanup are not pre-work you can skip; they are the work that decides whether your AI project succeeds or becomes a liability.
For governance, compliance, and records teams, the recognition marks a career inflection. You are no longer the people who manage retention schedules in the background. You are being asked to define which sources an agent may use, what evidence it must capture, and how its outputs align with regulator expectations. In government, banking, pharma, and utilities — all sectors Informotion explicitly serves — that shift is already happening. Your team should be at the AI design table from day one, not looped in after a pilot is built.
For everyday Microsoft 365 users, the impact will be invisible but real. When your organization eventually deploys an agent, the difference between a tool that saves time and one that creates verification busywork will trace back to whether someone did the discovery and remediation properly. Expect some AI programs to start with internal “data cleanup” pushes that might look like delay but will determine whether the assistant gives you the current contract or the obsolete boilerplate.
How We Got Here: AI’s Governance Reckoning
The trail to this moment began in 2023, when enterprises rushed to plug large language models into corporate content. Early Copilot demos wowed boards but fell apart in production because nobody had dealt with legacy sprawl: millions of obsolete documents, oversharing, unlabeled sensitive data, and zero clarity on which version of a policy was canonical.
Microsoft itself fueled the shift. In the fall of 2024, the company began emphasizing “AI-ready data” in its partner guidance and made Microsoft Purview capabilities a cornerstone of Copilot deployment readiness. By 2025, ISG had reshaped its evaluation criteria to heavily weigh a provider’s ability to prepare data for AI consumption, not just stand up infrastructure.
Informotion rode this wave with a 2013 pedigree in records management and enterprise content management — disciplines that had been viewed as administrative overhead before generative AI made them gatekeepers of trust. The firm’s 2024 acquisition of InTouch broadened its delivery capacity across Australia, the UK, and Ireland, giving it the heft to bid for projects that once defaulted to global integrators.
What to Do Now: A Practical Governance Checklist
If your organization is anywhere near a Copilot or agent deployment in the next twelve months, start with these concrete actions:
- Inventory your data estates. Identify every SharePoint site, Teams team, OneDrive account, legacy file share, and business system holding content that could be surfaced by AI. You can’t govern what you can’t see.
- Classify and label. Apply sensitivity labels and retention tags that reflect actual business risk and regulatory categories. Don’t boil the ocean — prioritize workspaces and document types most likely to hit an agent’s retrieval scope.
- Remediate oversharing. Run access reviews on broad SharePoint groups, inherited permissions, guest links, and abandoned team sites. Copilot respects permissions, so overly permissive access becomes a conversational embarrassment at scale.
- Designate authoritative sources. For each key decision domain (HR policies, contracts, product specs), decide which folder or system holds the record you want an agent to trust. Mark it clearly, and deprecate stale copies.
- Select partners who bridge both worlds. Whether you go boutique or global, demand evidence that a provider can not only build an agent but also explain how they’ll prove to a regulator that the agent used the right data, logged its actions, and didn’t stray from policy.
- Start with human-in-the-loop agents. Automate recommendations before irreversible actions. Let humans review, say, a case summary or a draft approval, while your team gathers accuracy metrics and refines the underlying data.
- Plan for ongoing stewardship. Governance isn’t a clean-before-launch task. Budget for continuous monitoring of permissions, content freshness, and agent outputs, because colleagues will keep creating new files and new Teams tomorrow.
Outlook: Governance Becomes the Control Plane
The Informotion nod is a market signal, not a finish line. Expect three shifts in the coming months:
- Boutique firms will multiply in the ISG quadrants. Other records-savvy shops will follow, forcing large integrators to acquire or partner for governance depth.
- Microsoft will tighten the screw. Look for Copilot deployment blockers unless Purview policies are in place, much like Microsoft 365 now nudges admins toward security defaults.
- Agent sprawl will demand governance automation. As enterprises spin up tens of agents via Copilot Studio, the real job will be maintaining an inventory, enforcing retirement rules, and auditing cross-agent interactions — work that fits Informotion’s “records-to-agent execution” promise.
If the governance work gets done right, Windows and Office users may never need to know it happened. They’ll just ask a question and get a useful answer, instead of a compliance incident.