The service became read-only; users could no longer create new plans or codespaces.
Because environments were not automatically transferred, developers had to manually move their work:
Users can now launch environments directly from a GitHub repository's "Code" button instead of managing separate Azure plans and subscriptions. Visual Studio Codespaces is moving to GitHub
GitHub Codespaces initially defaults to the light GitHub theme, whereas the original service used the VS Code "Dark+" default.
While both services share the same underlying technology—VS Code running on Linux—the move to GitHub introduced several shifts: The service became read-only; users could no longer
The original Azure offering allowed for more granular manual control over instance sizes at creation, a feature that was later streamlined in the GitHub implementation . How to Migrate Code
The migration followed a phased decommissioning of the Azure-based service: Key Transition Timeline
Visual Studio Codespaces officially retired on , consolidating its features into GitHub Codespaces . Microsoft made this move to simplify the developer experience by providing a native, "one-click" workflow directly within the GitHub platform where most code already resides. Key Transition Timeline