Microsoft has begun rolling out a ‘Manage memory’ toggle inside Copilot and revealed early preparations for a Google Drive connector, according to testers and UI references first reported by Windows Latest. The changes push Copilot toward the same persistent, cross-document capabilities that have made ChatGPT a personal research tool—but with Microsoft’s own enterprise governance layer built in.
What’s Actually Showing Up in Copilot
For weeks, users have sporadically noticed a new Manage memory switch tucked into the profile menu of the consumer Copilot web app and Windows 11 integration. Where exactly it appears depends on the A/B test bucket Microsoft has assigned you—sometimes at the top‑right profile icon, sometimes in the bottom‑left corner. Flipping the switch doesn’t yet open a full memory editor, but it primes the assistant to obey explicit “remember this” instructions. According to the observed behavior, when you tell Copilot something like “Remember that I prefer Python for data‑analysis examples,” the assistant stores that preference and uses it in later chats.
Microsoft’s documentation describes the memory as intent‑driven: casual conversation or one‑off prompts won’t be saved; only statements that clearly express a desire to be remembered trigger storage. That design mirrors ChatGPT’s memory model, but the user‑facing controls are still rough. While the toggle exists, there is currently no in‑app page to review or edit individual saved memories. Windows Latest’s testing found that you can delete all stored memories by going to the broader Privacy section of your Microsoft account, but a granular memory manager—where you could add, delete, or edit each entry—is referenced in code and expected later.
Alongside memory, the Connected apps (or Connectors) section of the same profile menu is expanding. Many Copilot users now see OneDrive as a connectable source, and the interface clearly lists Google Drive as an upcoming option. When enabled, connectors let Copilot read the contents of specific cloud folders and use that material in its responses. This isn’t local file search; it’s a direct pipeline from cloud storage into the assistant’s reasoning engine, particularly useful for Deep Research, where Copilot can synthesize information from multiple documents in one go.
Both memory and the Google Drive connector are appearing in staged rollouts. Not every account will have them yet—the presence of the features can vary by region, account type, and Microsoft’s testing schedules. Microsoft has not published a definitive timeline for full availability.
What This Means for You—Based on How You Use Copilot
If You’re a Casual Copilot User
Personalization may sound convenient, but the immediate practical concern is data visibility. Because the memory editor isn’t live for everyone, you might not know what Copilot has retained. Microsoft says it will notify you when memories are created or updated, but until that’s consistent, the safest play is to locate the Manage memory toggle in your profile and turn it off if you’re uncomfortable. You can always enable it later when the management UI is complete.
For connectors: if you don’t want Copilot accessing any cloud files, just avoid linking accounts. The feature is opt‑in—you’ll need to grant OAuth permissions for OneDrive or (eventually) Google Drive before Copilot can read anything.
If You Regularly Store Sensitive Files in Google Drive
Once the Google Drive connector pushes to your account, be cautious with OAuth scopes. Copilot will request permission to read files; ideally, the consent screen will let you limit access to specific folders, but early implementations often default to broad access. Check the permissions carefully and, if possible, restrict Copilot to a dedicated “AI‑readable” folder rather than granting blanket access to your entire Drive.
If You’re a Power User Relying on Deep Research
Connectors with Deep Research can dramatically cut down manual work. Imagine asking Copilot to “summarize all client proposals in the ‘Q3 Submissions’ folder on Google Drive and compare them to the budget spreadsheet from OneDrive”—the assistant could pull in both sources and produce a structured report. But test this with dummy data first. Because the feature is still rolling out, behavior might shift between builds, and you don’t want it misreading or misassociating real documents.
Keep in mind that Copilot currently offers five free Deep Research queries per month (the exact count may change; Microsoft hasn’t published a permanent limit). If you plan to use connectors heavily, budget for potential subscription tiers if additional queries become paid.
If You’re an IT Administrator or Manage a Tenant
Memory and connectors are not just consumer features—they have immediate enterprise implications. Microsoft has built compliance hooks into the architecture:
- Purview/eDiscovery: Copilot memories and interaction logs are discoverable and can be placed on legal hold.
- Separate retention policies: Earlier in 2025, Microsoft introduced dedicated retention controls for Copilot interactions, allowing you to delete them faster than standard mailbox or file data.
- Tenant‑level toggles: Admins can disable memory organization‑wide or for specific user groups.
However, the staged rollout means some users will get these features before your tenant policies are fully tested. Proactively check your admin centre for any “Manage Copilot” or “AI settings” section. If Google Drive connector shows up for your employees, you’ll want to control whether it’s allowed—especially if your organization already restricts third‑party cloud storage. Consider piloting the connector in a sandbox first, and update your internal guidelines to teach employees how to revoke linked services.
How We Got Here: From Simple Q&A to Persistent Assistant
Copilot started as a family of AI helpers scattered across Windows, Edge, Microsoft 365, and a standalone chat. The early versions were essentially session‑based: ask a question, get an answer, close the tab, repeat. That model is fine for quick facts but falls apart when you need the assistant to carry context across days or projects.
Microsoft began laying the groundwork for persistence in late 2024 and early 2025. References to “Copilot Memory” appeared in roadmap documents, and Microsoft publicly committed to an intent‑driven memory model that would be enterprise‑compliant from day one. At the same time, the company’s existing Graph Connectors—which already index third‑party data sources like Google Drive, Salesforce, and ServiceNow into the Microsoft Graph—started being positioned as a backbone for Copilot’s enterprise data access.
On the consumer side, the more direct inspiration is clear: OpenAI’s ChatGPT launched a full Connectors ecosystem, letting users link Google Drive, Gmail, GitHub, and other services directly into the chat. Microsoft, as OpenAI’s primary infrastructure partner, has been able to adopt similar patterns while layering its own compliance and admin controls on top. The Copilot Connectors you see now are essentially a consumer‑friendly wrapper around the same Graph Connector technology, with OneDrive as the first proof point.
Thus, when Windows Latest spotted the Manage memory toggle and the Google Drive listing in the profile menu, it wasn’t a surprise—it was the visible arrival of features whose technical scaffolding had been under construction for months.
What to Do Now: A Practical Checklist
Whether you’re an individual user or an IT pro, there are concrete steps you can take today.
For individual users:
- Open Copilot (web or Windows integrated), click your profile icon, and look for “Manage memory” or a “Memory” toggle. Turn it off if you want to wait for better controls.
- Check “Connected apps” or “Connectors” in the same menu. If OneDrive is already linked and you don’t want it, disconnect it immediately.
- When Google Drive appears, before granting access, review the permission scopes and, if the UX supports it, limit access to a single folder.
- Remember that even with memory off, your conversation history might still be logged separately; delete old chats from the Privacy section if needed.
For IT administrators:
- Locate your tenant’s Copilot admin controls (typically under the Microsoft 365 admin centre or dedicated Purview portals). Verify whether memory is enabled by default and decide if you need to disable it.
- Update retention policies to include Copilot interactions and memories. Microsoft provides separate policy containers for AI‑generated content—use them.
- If your organization uses Google Drive, consider whether you want to allow the connector at all. If yes, pilot it with a test group and monitor Purview for the resulting data.
- Educate users: send a brief advisory that tells them how to find the memory toggle and what company policy is regarding connector usage.
What to Watch Next
Microsoft’s connector ecosystem will likely expand quickly. The same profile menu that lists OneDrive and (future) Google Drive is expected to eventually show Dropbox, Box, and enterprise platforms like Salesforce. However, pricing remains an open question. The Windows Latest report notes that while current connectors appear free, some may eventually be gated behind the $20/month Copilot Pro subscription. Microsoft has not published a consumer‑facing list of which integrations will remain free, so treat any assumption of universal free access as tentative.
Another uncertainty is cross‑product memory synchronization. If you save a memory in the web Copilot, will it automatically appear in Copilot in Windows or the Microsoft 365 Copilot pane? Microsoft hasn’t detailed whether memories roam across all Copilot endpoints, and early behavior suggests they might be siloed. Until documentation clarifies this, expect gaps.
Finally, the full memory management interface—where you can see, edit, and delete individual stored facts—is still in the pipeline. When it lands, it will be the true test of Microsoft’s privacy promise. Right now, the building blocks are in place, but the glue holding them together for a seamless, trustworthy experience is still being applied.