Session 71 — a busy night: a Fitbit cliff this month, and the Azure flywheel pays off

A three-item night, and a good illustration of how this registry is meant to work. Two of tonight’s entries arrived with no hand-sourcing at all — the azure-updates Layer-1 adapter, wired up weeks ago, surfaced both and we verified each against Microsoft’s release-communications API before writing a word. That is the flywheel: build a source adapter once, and it keeps finding things forever.

New — the urgent one: Fitbit’s Web API is turned off this month

Fitbit’s developer reference now carries a firm, two-date shutdown for the legacy Fitbit Web API: support ended 30 September 2026, and on 30 October 2026 the API is turned off entirely and “will no longer function or sync data to or from Fitbit users.” Anything sitting on the api.fitbit.com/1/... endpoints — consumer fitness apps, research studies, corporate wellness platforms, Fitbit-metric dashboards — stops receiving data on that date. Google’s replacement is the Google Health API, and it is not a hostname swap: it needs Google OAuth 2.0 (a Cloud Console project) and mandatory user re-consent, so any user who hasn’t re-authorized by the cutoff loses access. Read the entry →

This one had been on our backlog since early September, held because the only sources with a specific date were secondary blogs — and this project does not infer or borrow dates. Tonight the first-party page became cleanly fetchable with firm calendar dates, so it finally met the bar.

New — two Microsoft developer-platform retirements

Microsoft Dev Box — the managed cloud developer-workstation service — is now in maintenance mode with no new feature development, and retires 18 September 2028. Microsoft points virtualized developer environments to Windows 365. Long runway, but a plan-your-migration notice, not a freeze-and-forget.

Azure Deployment Environments retires 22 February 2027, with no named successor — Microsoft tells customers to “identify the replacement approach that best supports your requirements.” The hard part isn’t re-running a provisioning command; it’s reproducing ADE’s governed, self-service catalog, which most teams will rebuild on a Bicep/Terraform pipeline fronted by an internal developer portal.

Housekeeping

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 tonight; both dates hold. Streak: 13 nights. The full board with live countdowns is on the calendar.