Microsoft has quietly added a roadmap entry promising that government customers using the new Outlook for Windows will finally be able to import calendar and contact data from PST files directly into a mailbox. The feature, tracked under Microsoft 365 roadmap ID 486840, targets General Availability in July 2026—a date that underscores both the complexity of bringing legacy file support to the modern Outlook client and the cautious pace of feature rollout in regulated cloud environments.

The roadmap item, decoded

Roadmap 486840 appeared in late March 2025 with a single terse statement: “Users of new Outlook for Windows in GCC will be able to import calendar and contact data from PST files into a mailbox.” No documentation link, no preview build number, no indication of which exact PST formats will be supported or whether email import will follow. The “Last Modified” field shows it was updated around March 24, 2025, but Microsoft has not elaborated publicly beyond the roadmap card.

Importantly, the entry limits itself to calendar and contact import—not emails, tasks, notes, or journal entries that legacy PST files often contain. It also specifies GCC, which is the baseline Government Community Cloud tier for US federal, state, and local entities, as well as authorized contractors. Higher-security clouds like GCC High and DoD are not mentioned, though the feature could trickle down once proven.

What it actually does—and doesn’t do

The new Outlook for Windows, which began replacing the classic Win32 client in 2024, is essentially a web-powered shell. It lacks native COM add-in support, offline archive capabilities, and—until now—any direct PST import workflow. For government users, this has been a critical gap. Many agencies have decades of archived PST files containing calendar entries and contacts that must be migrated into Exchange Online mailboxes to meet compliance or operational needs.

Roadmap 486840 promises a native, server-side-friendly way to ingest that data. Instead of the classic method where Outlook opens a PST as a data file and copies items locally, the new feature appears to push data directly into the mailbox, presumably via a cloud-based process. This aligns with Microsoft’s broader strategy of reducing local client dependencies and keeping data in the tenant boundary—an important security consideration for government workloads.

However, the roadmap explicitly excludes email import. That may be addressed separately, or Microsoft may steer users toward existing PST email import tools already available for Exchange Online via the compliance center or AzCopy-based bulk ingestion. The narrow scope suggests that delivering a reliable, secure mechanism for structured data types like calendar and contacts was the priority, perhaps because those items are harder to re-create from alternative formats.

What July 2026 means for your migration timeline

For GCC administrators, a 16-month wait from today is both a relief and a headache. It’s a relief because it ends the indefinite uncertainty of whether PST support would ever arrive. It’s a headache because many migration projects are already underway, and workarounds—manual recreation, third-party tools, or hybrid classic-Outlook coexistence—must remain in place for at least another year.

If you’re a government employee or contractor still sitting on a desktop full of PST archives, the message is clear: don’t delete those files. The import pipeline is coming, but it won’t be ready until mid-2026. In the meantime, if you need to access those calendars and contacts today, your options remain:

  • Keep a classic Outlook client (perpetual or volume-licensed) running alongside the new Outlook to open PST files and manually copy items.
  • Use a third-party migration tool that connects to Exchange Web Services (EWS) to push PST data into a mailbox—though many such tools require admin privileges and are not free.
  • For calendars only, consider exporting to ICS files from the classic client and then importing into Outlook on the web, though this can be lossy for recurring appointments or attachments.

For CIOs and IT planners, the July 2026 date should be added to project schedules now. It aligns roughly with the end-of-support timeline for Office perpetual products (though those dates have shifted before). If your agency plans to fully transition users to the new Outlook by 2026, this feature removes one of the last blockers—but only if you don’t need PST email import integrated into the client.

How we got here: PST support and the new Outlook’s rocky road

PST files have been a staple of Outlook data portability for over two decades. The classic Outlook desktop app could open, browse, and import from PSTs of almost any vintage, including older ANSI-format files and password-protected archives. When Microsoft announced the “One Outlook” vision—a unified, web-rendered client built on Edge WebView2—it initially communicated that PST support would come later. That “later” turned into a multi-year saga.

The commercial cloud (non-GCC) received limited PST read-only access in early 2025, but even there, the feature was restricted to opening PSTs as read-only data files without import functionality. Full import capabilities for commercial tenants are still not generally available as of this writing, though a similar roadmap item for the commercial cloud (ID 182255) promises “PST file support for reading, searching, and accessing PST email messages, calendar entries, and contacts” with a data-file approach, not mailbox ingestion.

GCC customers historically receive features six to twelve months after the commercial cloud due to the extra compliance validation and the separate infrastructure in Microsoft’s sovereign clouds. The July 2026 date for GCC fits that pattern, assuming the commercial version rolls out by late 2025. The roadmap’s mention of “import…into a mailbox” rather than opening as a data file suggests GCC may get a more mature, cloud-native ingestion path from day one, bypassing the interim read-only step.

This cautious approach is understandable. PST import into Exchange Online must handle a minefield of data hygiene issues: corrupted records, duplicate items, legacy properties that don’t map cleanly to modern schema, and large files that could throttle server resources. For government tenants with stricter data sovereignty and auditing requirements, Microsoft needs to ensure every imported item is traceable, discoverable, and compliant with retention policies. Rushing that feature could mean data loss or security gaps.

What to do now (and what to watch)

For GCC administrators:

  1. Audit your PST inventory. Identify how many users still rely on PST files for calendar and contact data, and estimate the total data volume. This will help you plan for the ingestion process once it’s available.
  2. Catalog PST locations. Many PSTs live on local hard drives, network shares, or even removable media. Consolidate them into a secure, accessible location now so you’re not scrambling later.
  3. Review data governance policies. Determine whether imported calendar and contact items will automatically inherit mailbox retention labels or require manual tagging. Discuss with your compliance team how to handle items that may be older than your default retention period.
  4. Stay alert for preview announcements. Microsoft often opens features to targeted release or a private preview months before General Availability. Register your tenant for the GCC targeted release program if you haven’t already, and monitor the Microsoft 365 admin center message center for early access opportunities.
  5. Plan your training and communication. When the feature lands, users will need clear instructions on where to find the import option and what to expect. Prepare internal documentation templates now to adapt later.

For individual government users:

  • Do not attempt to force PST import through unofficial methods, as this can violate your agency’s data handling policies.
  • Continue using your existing workflow while keeping your PST files backed up. If you’re comfortable with the classic Outlook, you can keep it installed as a safety net until the feature arrives.
  • If you change roles or leave your agency, ensure your PST files are transferred to an official repository rather than lingering in personal storage.

The bigger picture: Microsoft’s steady march toward PST retirement

While Microsoft hasn’t openly declared a “PST end-of-life,” the writing is on the wall. The new Outlook is the future, and it intentionally omits PST creation and local archiving. Features like online archive, auto-expanding archive, and direct cloud-based ingestion are gradually making PST files less necessary. For government customers, Roadmap 486840 signals that Microsoft is finally bridging the gap—but it’s doing so selectively, starting with the non-email content that is most painful to migrate through existing bulk tools.

By 2026, the conversation may shift definitively: PST files will become read-only relics, and the recommended path for long-term data will be the cloud-based archive. Until then, patience and preparation are the watchwords for GCC tenants.

What to watch next

Keep an eye on the Microsoft 365 roadmap for a sibling entry targeting PST email import or broader PST management tools. A commercial cloud general availability announcement—likely by late 2025—will give you a concrete feature preview and may include PowerShell cmdlets or Graph API endpoints that GCC admins can eventually use. Also monitor the GCC high and DoD roadmaps; if the feature expands to those sovereign clouds, it signals that Microsoft has confidence in the import pipeline’s security posture. Finally, watch for any change in the July 2026 date, as roadmap timelines can shift based on testing feedback.