Microsoft is shutting down two of its AI app-building services, and it wants developers and IT admins to know before the clock runs out. According to a report from Neowin, the company is retiring these tools as part of a broader effort to fold its AI capabilities into the Copilot brand, and there’s a hard deadline developers must meet to avoid losing access to the apps they’ve already built.
The announcement is a reminder of how quickly Microsoft’s low-code and AI development landscape has been shifting over the past couple of years. If you’ve built anything on these services, you’ll want to understand what’s changing and what you need to do before your access disappears.
Which AI app-building services are being retired?
At the center of the news is the retirement of two AI app-building services. Microsoft is winding these down in favor of its Copilot products, which means the tools you may have relied on for creating and managing AI-powered apps will no longer be available as they exist today.
The initial report doesn’t spell out every detail, but the direction is clear: the company is consolidating app-building capabilities under the Copilot umbrella rather than keeping them spread across separate services. This aligns with a strategy Microsoft has been pursuing since it launched the Copilot brand in early 2023, when it began rebranding and folding numerous standalone products into a unified AI experience.
The deadline you can’t miss
The most urgent part of the announcement is the deadline. Microsoft is giving developers and IT admins a window to act before existing apps become inaccessible, which puts the onus on you to figure out your migration path before time runs out.
For IT admins managing a fleet of business apps, this isn’t just about your own development work — it’s about the internal tools your colleagues depend on. If an app was built on one of the retiring services and there’s no migration plan in place, it could simply stop working once the service is retired.
The practical takeaway is straightforward: don’t wait. If you have anything built on these services, start mapping out what needs to move and where it needs to land before the deadline.
Why Microsoft is consolidating under Copilot
This retirement fits into a much larger pattern. Over the past few years, Microsoft has steadily consolidated its AI and low-code offerings. Power Virtual Agents, for example, was rebranded as Microsoft Copilot Studio, folding chatbot and conversational AI development into the Copilot family.
Based on that trajectory, the current move appears to be Microsoft pushing remaining app-building tools further toward a single, Copilot-native experience. The idea is to give developers one place to build, manage, and deploy AI-powered applications rather than juggling multiple platforms.
It’s worth noting that this kind of consolidation has been a recurring theme in Microsoft’s strategy — products get absorbed, rebranded, or retired as the company funnels features into Copilot. Not every change has gone smoothly, and developers have occasionally pushed back on losing familiar interfaces, so it’s reasonable to approach this announcement with a healthy dose of caution.
What this means for you
For everyday Windows users, this likely won’t change anything you do day to day — you’re not going to see a new Copilot feature appear on your desktop because of this. But if you’re a developer, citizen developer, or IT admin who has built apps on these services, this is something you need to take seriously.
The risk is real: apps built on a retiring service don’t just quietly become outdated. When the underlying service is shut down, the apps can stop functioning entirely, and if you haven’t migrated them, you could lose access to work you’ve already done.
What you should do before the deadline
First, inventory what you have. Take stock of any apps, flows, or integrations built on the services being retired. Then, figure out where they need to go — whether that’s a Copilot-native alternative or another supported platform.
Reach out to Microsoft for the official deprecation timeline and any migration documentation. The company typically publishes detailed notices with exact dates and guidance, so check the official channels rather than relying on secondary reports. If you’re managing apps for an organization, coordinate with your team so nothing gets left behind.
How to stay informed
Because the initial report is brief, the specifics — exactly which two services, the precise deadline, and the recommended migration path — are the details to watch for. Microsoft usually follows up with formal deprecation notices that spell out the timeline, so keep an eye on official announcements for the full picture.
In the meantime, treat this as a signal to review your AI app portfolio. The trend toward a unified Copilot experience shows no signs of slowing, and planning ahead now will save you a scramble later.
Source: Neowin
Over to you: Have you already built apps on the services being retired, and do you have a migration plan in place before the deadline?
