Microsoft 365
Security, identity, licensing and governance assessment.
Product roadmap
Direction with honest boundaries.
This roadmap separates the live product, customer activation work, product priorities and long-term platform ideas. It intentionally carries no delivery dates and should not be read as a contractual commitment.
How to read this roadmap
NowUsable in the product today
ActivationBuilt, with customer prerequisites
Next / LaterPriorities and candidates, not promises
VisionLong-term direction only
79
Live checks
63 run with the standard read-only connection; the rest use optional sources.
13
Coverage categories
Across the current Google Workspace assessment.
4
Executive risk areas
Identity, Security, Collaboration, Storage & Licenses
2
Live ecosystems
Google Workspace and Atlassian Cloud are available today.
NowAvailable now
Google Workspace and Atlassian Cloud assessments
The live product turns authorized Google Workspace and Atlassian Cloud metadata into prioritized risk, governance and cost evidence.
- 79 Google Workspace checks across 13 categories, from identity and email security to managed devices and SKU-level licenses.
- Executive reporting with a weighted risk score, area scores, Gemini readiness and annual savings modeled from your license and storage costs.
- Atlassian Cloud assessment for Jira, Confluence, Marketplace apps and backup readiness, with optional organization-level security depth.
- Scan history, change alerts, CSV export, PDF reports in English or German, and synthetic demo tenants.
ActivationAdditional setup
Optional Drive, Shared Drive and Chrome visibility
These data paths are implemented, but real coverage depends on customer-controlled Google administration and prerequisites.
- A service account and administrator-approved Domain-Wide Delegation are required for Drive metadata.
- Shared Drive governance uses the same optional Drive metadata authorization.
- Chrome extension visibility requires Chrome Enterprise Core plus managed-profile reporting or browser enrollment.
- Unavailable sources remain explicit coverage gaps; they are not treated as passing checks.
NextPlanned
Make the assessment easier to activate and deliver
Near-term priorities focus on the existing Google Workspace product. Scope and order follow customer evidence, not a fixed launch promise.
- Reduce setup friction and make optional coverage prerequisites easier to validate.
- Refine management reporting around ownership, effort and remediation sequencing.
- Improve partner delivery workflows for repeatable assessments and customer handoff.
- Strengthen coverage explanations so every skipped or partial signal is visible.
LaterPlanned
Evaluate scope-dependent Google Workspace depth
These candidates require customer demand, technical validation and, in some cases, additional Google permissions or external assurance.
- Delegated-role detail for administrators and admin groups.
- Administrator policy signals such as password and context-aware access policies.
- Additional calendar, alerting and governance evidence where permissions are proportionate.
- Restricted Gmail settings, labels, DLP or retention coverage only after an explicit security and business decision.
Vision
A shared assessment model across more digital ecosystems.
The following areas are platform vision only. They are not available, not scheduled, and not included in a TenantOne purchase today.
Direction, subject to validation
Salesforce
Configuration, access and data-governance assessment.
Browser Security
A broader browser posture beyond today’s Chrome visibility.
SaaS Security
Cross-application exposure and governance signals.
Backup
Coverage, retention and recovery-readiness evidence.
AI Governance
Data exposure, access controls and AI adoption readiness.
Roadmap principles
Customer evidence shapes priority.
Additional access must earn its value.
Coverage gaps stay visible.
Vision is labeled before it is sold.
Priorities may change as Google APIs, verification requirements, customer needs and security considerations evolve. Only capabilities explicitly described as available should be treated as part of the current product.
Start with evidence
Start with the product that exists today.
Use the synthetic Google Workspace demo to inspect the current assessment, report and findings before discussing any optional setup.