Fitbit's Web API is turned off 30 October; Microsoft retires Dev Box (2028) and Azure Deployment Environments (2027)

Three new dated items tonight. One is imminent — Fitbit’s legacy Web API is turned off this month — and two are longer-runway Microsoft developer-platform retirements off the Azure Updates feed. Each was verified against its primary source before publishing. The two re-verification flags due soon — EWS worldwide allow-list enforcement (10 October) and Azure Databricks Runtime 10.4 LTS (1 November) — were hand-checked against their primary sources and both dates hold.

New: Fitbit’s legacy Web API is turned off on 30 October 2026

Fitbit’s developer reference now carries a firm two-date shutdown. Support for the legacy Fitbit Web API ended on 30 September 2026 — the API kept running, but Google stopped fixing bugs and supporting it — and on 30 October 2026 the Web API is turned off entirely and “will no longer function or sync data to or from Fitbit users.” That second date is a hard cliff for the large base sitting on the api.fitbit.com/1/... endpoints: consumer fitness apps, research studies, corporate wellness platforms, Fitbit-metric dashboards. Google’s replacement is the Google Health API, and it is not a hostname swap — it uses Google OAuth 2.0 (a Cloud Console project) and requires mandatory user re-consent, so any user who hasn’t re-authorized by the cutoff loses data access. Work backwards from 30 October and drive existing users through re-consent early.

New: Microsoft Dev Box retires 18 September 2028 — and is in maintenance mode now

Microsoft has put Dev Box, its managed cloud developer-workstation service, into maintenance mode with no new feature development, and set a retirement date of 18 September 2028. The closing-down process starts 14 September 2026. Nothing breaks immediately — existing usage stays supported through the transition — but Microsoft is explicit that its investment in developer cloud environments is now on Windows 365, the named replacement for virtualized developer workstations. The long runway is the point: moving a developer-workstation estate (dev centers, projects, pools, custom images) onto a different platform, and validating identity, networking, image and licensing along the way, is exactly the kind of migration you start early rather than discover in 2028.

New: Azure Deployment Environments retires 22 February 2027 — no drop-in successor

Azure Deployment Environments (ADE) — catalogs of IaC templates plus governed, self-service, on-demand environments for developers — will be retired on 22 February 2027, closing down from 14 September 2026. The catch is that Microsoft names no one-to-one successor: the notice tells customers to “identify the replacement approach that best supports your requirements.” ADE’s real value was self-service with guardrails — a controlled catalog and access policy, not just a provisioning command — so the replacement has to reproduce that governance, not only the az call underneath. Most teams will rebuild on a direct Bicep/Terraform pipeline (Azure DevOps or GitHub Actions), optionally fronted by an internal developer portal such as Backstage to restore the self-service catalog.

The next three weeks on the board

Re-verified against their primary sources, dates unchanged: EWS worldwide allow-list enforcement (10 Oct — Microsoft turns on the cloud setting requiring an EWSAllowedAppIDs allow-list; full EWS disablement April 2027), Windows 11 24H2 end of servicing and Reddit RSS feeds ending (both 13 Oct), Microsoft Sentinel containerized SAP connector images removed (14 Oct), Cloudflare Workers KV legacy API (15 Oct), OpenSSL 3.4 end of life and Minimus shutdown (both 22 Oct), OpenAI GPT-4 / GPT-3.5 / o1 / o3 model removals (23 Oct), Kubernetes 1.34 end of life (27 Oct), and OpenAI’s hosted Evals platform going read-only (31 Oct, before its 30 Nov shutdown). Full board with live countdowns on the calendar.