AINIQ for Copilot is planned for a later phase.
Microsoft Copilot, Teams, and AppSource are part of the roadmap, but they are not part of the current rollout.
What AINIQ does here
A future enterprise wrapper that still uses the same AINIQ identity, billing, and privacy center.
A Teams and Copilot experience built on the same AINIQ product foundation.
A staged rollout that expands into Microsoft channels later.
Permissions requested
Copilot packaging is deferred until the wrapper, enterprise tenant story, and support model are ready.
AINIQ is waiting until the integration can deliver a complete product experience.
Work happening now will help support Copilot later.
How data is handled
AINIQ keeps privacy, revocation, and billing control centralized at ainiq.app.
Future enterprise wrappers will build on the same secure AINIQ account foundation.
Microsoft support will expand later as customer demand and support readiness grow.
Billing and account model
Copilot will not get a separate identity silo or duplicate billing model.
The base AINIQ account remains the system of record for access, consent, and monetization.
Marketplace packaging starts only after earlier channels show repeat paid usage.