Microsoft has announced that it will retire the Podcasts feature in the consumer Copilot app on August 18, 2026. After this date, users will no longer be able to create new AI-generated podcasts or access any podcasts they created previously.
The change applies to all Copilot users, including both free and paid subscribers. Since Microsoft does not provide an option to export or download these podcasts, all existing podcast content and shared links will be permanently removed after the feature is discontinued.
Microsoft Ends the Copilot Podcasts Feature
Copilot Podcasts allowed users to turn prompts and documents into AI-generated podcast-style audio. However, the podcasts were stored only inside the Copilot app and could not be downloaded or moved to another platform.
Microsoft confirmed that once the feature is retired, previously created podcasts and any shared links pointing to them will stop working. The company thanked users for their feedback but did not explain why the feature is being removed.
This retirement only affects the consumer Copilot app and does not impact Microsoft 365 subscriptions or other Copilot features included with eligible plans.
What Users and Organizations Should Do
Users and organizations that have shared Copilot podcast links in documents, training materials, websites, or internal communications should review them before August 18, 2026. After the retirement date, those links will no longer be accessible.
Although the original AI-generated audio cannot be exported, users may be able to recreate important podcasts if they still have the original prompts, documents, notes, or transcripts used to generate them.
This announcement also highlights an important lesson for organizations using AI services. Business-critical AI-generated content should not rely solely on cloud-hosted features that do not support data export. Keeping local copies or storing important AI-generated content in approved repositories can help avoid data loss if a service or feature is removed in the future.
Microsoft confirmed that this change only affects the Podcasts feature. Other Copilot capabilities and Microsoft 365 subscription benefits will continue to be available as usual. Users who need additional information can contact Microsoft Support through the official support channels.
The agent_submit architecture with its 24-step budget and six terminal states is a pragmatic approach to balancing automation efficiency with cost control. At APIVALE, we’ve implemented similar LLM-driven form automation for API testing, and we found that the fill_many optimization you mentioned significantly reduced step count and solver costs. Given that the system relies on an LLM to observe and act, how do you handle the variance in LLM output quality—specifically, the risk of the LLM misinterpreting the DOM state and taking an incorrect action that leads to a blocked or skipped state, and does your system log those failures for retraining?