Roadmap
What is planned for Atlas next. Order reflects priority, not dates. Shipped changes are listed in the GitHub releases.
- In progress
Calendars
Calendar backup, restore, listing, and verification, with recurring series, exceptions, and file attachments (issue #134). Exchange backup already covers mail and contacts. See Calendar backup.
- In progress
Microsoft Teams
Channel messages with replies, reactions, and edits, membership, channel settings, and tabs. Backup and verification are available; restore is pending. Team files are covered by SharePoint backup.
- Planned
Certificate authentication
Sign-in with a certificate instead of a client secret (issue #778). It is the prerequisite for site and library permissions and folder colours, which Microsoft 365 accepts only through the SharePoint REST API. Sharing on files and folders is already covered, see Sharing.
- Planned
Shortcuts to shared folders
Shortcuts in OneDrive do not appear in Microsoft Graph's change listing, so a backup misses them today. Capturing them needs a separate scan (issue #777).
- Planned
Microsoft Entra ID
Versioned export of users, groups, roles, app registrations and Conditional Access policies, with a reviewed, diff-based reapply path.
- Planned
Recovery into a clean tenant
Restore a compromised or lost tenant's data into a different tenant, with a mapping from old identities to new ones. Builds on the Entra ID export. Restoring one owner or site into another tenant already works with
--target-profileand the SDK'screateTenant. - Exploring
Argon2id key derivation
A memory-hard alternative to scrypt. Existing tenants move over with
atlas keys rewrap, without re-encrypting data. - Exploring
Microsoft Planner
Plans, buckets, tasks and their details, read app-only with
Tasks.Read.All. Restore recreates them as new objects. - Exploring
Power BI
Reports and semantic models exported per workspace through the Power BI REST API. Read app-only once a Power BI administrator enables Allow service principals to use Power BI APIs and the app is a member or admin of each workspace. No Microsoft Graph permission covers it.
Constraints that shape the plan
Teams. Scope is channel content: messages with replies and reactions, team and channel membership, tabs, and channel configuration.
- Each channel has its own sync checkpoint. A channel that cannot be read incrementally is read in full, without failing the run.
- Reading channel messages app-only may require Microsoft's protected API approval for
ChannelMessage.Read.All. - Restore is export-only, because Microsoft Graph cannot repost a message with its original author and timestamp.
- 1:1, group, and meeting chats are out of scope. They hold personal conversations with separate legal and retention obligations, bulk access goes through the metered
getAllMessagesexport API, and every user's chats would have to be listed separately.
Certificate authentication. Site and library permissions and folder colours can be read but not written with a client secret. The SharePoint REST API that writes them requires certificate authentication, so both wait on it.
Entra ID. Restore means reapplying configuration, not recovering bytes: a recreated policy or app gets a new object ID, and client secrets cannot be read back. Atlas will never overwrite a live directory silently. Microsoft keeps deleted directory objects for only 30 days and keeps no history of Conditional Access changes, which is the gap Atlas fills.
Clean-tenant recovery. Object IDs differ between tenants, so every owner, mailbox, and site needs an explicit mapping before anything is written. Unmapped identities are reported, never guessed. A single cross-tenant restore already takes its target explicitly. What is missing is the tenant-wide mapping that drives every owner at once.
Planner. Microsoft Graph cannot report Planner changes incrementally, so each run re-reads plans and compares ETags. Recreated tasks get new IDs, completion history cannot be written back, and task comments live in the group's conversations rather than in Planner. Premium plans (Planner Plan 1 and up) use a different API and are out of scope.
Power BI. Power BI is not part of Microsoft Graph, so the permissions on the Atlas app registration do not cover it. A Power BI administrator must enable Allow service principals to use Power BI APIs in the tenant settings, and the app must be added to each workspace as a member or admin. Personal workspaces (My Workspace) cannot be read by a service principal.
Suggest a feature
Send ideas to info@wisecom.fi or open an issue on GitHub. Wisecom prioritizes the roadmap against its own business goals, so not every request will be scheduled. When a suggestion fits both sides, we may build it.
The most direct way to shape the engine is to contribute. Pull requests are welcome; start with CONTRIBUTING.md.

