BestPaid guides · Mobile apps · Visual Studio App Center

Visual Studio App Center: Analytics and Diagnostics end in March 2027. What to remove and what replaces it

Visual Studio App Center was retired on March 31, 2025, except for Analytics and Diagnostics (crash reports), which now run until the end of March 2027 after two extensions. Any app still shipping the App Center SDK (Xamarin, .NET MAUI, React Native, native iOS or Android) needs a new home for crashes and events before then: support and telemetry ingestion end on March 31, 2027, so ship a release that replaces the SDK in time.

Sources: Microsoft's App Center retirement page, Azure Monitor migration guide (Preview) and Application Insights IP handling page (the tables native OTLP data is stored in); App Center SDK docs (overview; getting started for MAUI/Xamarin, React Native, Android, iOS; Distribute for Android, iOS, MAUI/Xamarin; Export; diagnostics export); Microsoft's code-push-server and react-native-code-push READMEs, the client's setup docs for iOS and Android, and the Xamarin support policy; the OpenTelemetry Collector's Azure Monitor exporter README; React Native's 0.82 release post; Apple's Upcoming Requirements; Google Play's target API level requirement. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What ends when

DateWhat Microsoft says
March 20, 2025First extension: Analytics and Diagnostics supported until June 30, 2026.
March 31, 2025App Center retired: Build, Test, Distribution and CodePush ended; only Analytics and Diagnostics kept running.
April 15, 2026Azure Monitor mobile analytics entered public preview as the migration path, and Analytics and Diagnostics were extended to the end of March 2027, unchanged until then. General availability was expected later in 2026.
March 31, 2027End of support for Analytics and Diagnostics, including telemetry ingestion (Azure Monitor migration guide).

Older App Center SDK pages still carry a June 30, 2026 banner, which the April 2026 update supersedes. The Azure Monitor guide was still marked Preview on November 21, 2026.

Which apps are affected

Any app that ships the App Center SDK:

Xamarin apps have a second problem: support ended on May 1, 2024, and Microsoft names Android API 34 and Xcode 15 as the last SDKs Xamarin targets, below the current Google Play and App Store minimums for phone and tablet apps (step 5 below). Plan the App Center removal as part of the move to .NET: Microsoft says Xamarin.Forms projects should be migrated to .NET MAUI, and Xamarin.Android, Xamarin.iOS and Xamarin.Mac projects upgraded to .NET for Android, .NET for iOS and .NET for Mac. See our Xamarin.Forms to .NET MAUI 11 checklist.

What Microsoft recommends instead

FeatureStatusMicrosoft's recommendation
BuildEnded March 31, 2025Azure Pipelines.
TestEnded March 31, 2025BrowserStack App Automate.
DistributionEnded March 31, 2025App Store and TestFlight; Google Play and Play Console test releases; Azure Pipelines tasks publish to both. Microsoft Store apps: Package Flights in Partner Center.
CodePushEnded March 31, 2025A standalone CodePush server you host yourself.
Analytics and DiagnosticsUntil March 31, 2027Azure Monitor (Application Insights and Log Analytics via OpenTelemetry, in preview) or the Azure Native ISV services Datadog, Dynatrace or New Relic. Microsoft Store apps: the Partner Center dashboard; UWP apps can log custom events with the Microsoft Store Services SDK.

The standalone CodePush server needs Azure Blob Storage and is designed for Azure App Service. Microsoft has archived it and the react-native-code-push client: the server comes as is, without Microsoft support, and the client won't support the New Architecture. Its README says to opt out of the New Architecture on React Native 0.76 or later, but React Native 0.82 and later ignore the opt-out, so the client needs React Native 0.81 or earlier. To keep CodePush, point the client at your server:

<!-- Android, strings.xml -->
<string moduleConfig="true" name="CodePushServerUrl">server-url</string>

<!-- iOS, Info.plist -->
<key>CodePushServerURL</key>
<string>server-url</string>

The Azure Monitor route

Microsoft's guide, in order:

  1. Prepare a workspace-based Application Insights resource and its linked Log Analytics workspace.
  2. Deploy a gateway you run: an OpenTelemetry Collector for high-volume apps or an Azure API Management proxy for small ones. Apps send OTLP to it; it holds the credentials.
  3. Configure the gateway to export to Azure Monitor.
  4. Remove the App Center SDK.
  5. Instrument the apps with a community OpenTelemetry SDK; .NET MAUI and React Native have no cross-platform one, so use a native bridge: for MAUI, native library interop or custom code based on the opentelemetry-dotnet examples; for React Native, Native Modules.
  6. Point the apps' OTLP export at the gateway.
  7. Validate ingestion and find the tables your telemetry lands in: with Azure Monitor's native OTLP ingestion, OpenTelemetry tables such as OTelSpans, OTelLogs and OTelEvents; with the Collector's Azure Monitor exporter and a connection string, Application Insights tables such as traces, exceptions and customMetrics. Then rebuild queries, workbooks and alerts on them.

Microsoft supports Azure Monitor once telemetry reaches it; the community OpenTelemetry SDKs, an OpenTelemetry Collector gateway and App Center SDK removal are outside its support. Crash handling also differs: App Center grouped mobile crashes and resolved symbols, while Azure Monitor stores exceptions and stack traces with a different workflow.

What to remove from the app

Microsoft's list: packages, initialization code and service calls, configuration values, symbol or mapping uploads in CI; then confirm nothing goes to App Center. Where they live:

If a Google Play build still has the full Distribute module, remove it first: Microsoft warns that Google Play treats in-app update code as malicious even when unused, which can get the app removed. To find leftovers in each repository, pipelines included:

git grep -niE "appcenter|code-?push"

Order of work

  1. Inventory each app and build flavor: App Center modules, CodePush, app secrets, and the dashboards and alerts people use.
  2. Pick and build the destination per app (for Azure Monitor, the resources and the gateway), and check that it handles your symbols and crash grouping.
  3. Export the history you want. Analytics export backfills only 28 days (Blob Storage) or two days (Application Insights), so start it early; crashes export to Blob Storage through the API.
  4. Swap the SDKs in one release per app and move symbol uploads in CI. Microsoft's docs say an iOS app can't have more than one active crash reporting SDK, so don't plan an overlap.
  5. Ship under today's store rules: since August 31, 2026, Google Play app updates must target API level 36 (lower for Wear OS, Automotive OS, TV and XR), and from February 1, 2027, Google Play won't let you release an update that doesn't support 16 KB memory pages (see our 16 KB page size by framework guide); since April 28, 2026, iOS, iPadOS, tvOS, visionOS and watchOS apps uploaded to App Store Connect must be built with Xcode 26 or later, and since September 9, 2026, iOS and iPadOS apps must target iOS 13 or later. On Xamarin, that means moving to .NET first: .NET MAUI for Xamarin.Forms, and .NET for Android and .NET for iOS for Xamarin.Android and Xamarin.iOS apps.
  6. Validate and clean up: confirm data arrives, rebuild dashboards and alerts, remove App Center tokens and secrets. After March 31, 2027, builds with only the App Center SDK have no supported crash destination, so move users to the new version before then.
Still shipping App Center in an app that hasn't been updated in a while? We update native, Unity, Flutter, React Native and Xamarin apps to the current App Store and Google Play rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer