Skip to main content

Azure Spring Apps Retirement Announcement – Self Analysis

Last updated: July 15, 2025 | Author: Andrew Orcilla

This notification went through an editorial process by me as one of a request I completed for my Technical Writing role at Insight Global. This request informed customers about the upcoming retirement of Azure Spring Apps.

After the communication was sent to subscription owners by email and the Azure portal, it was then sent to the Azure Updates team to copy onto their live page.

There are slight modifications the Azure updates team made to conform to their policies for posting on their Azure Update page mainly to their date formatting.

info

Live Communication Link: View on Azure Updates

Summary​

Microsoft Azure, in partnership with VMware, will retire Azure Spring Apps (Basic, Standard, and Enterprise SKUs) on March 31, 2028. This retirement notice guides developers and administrators to evaluate migration paths, like the mentioned Azure Container Apps, to ensuring a smooth transition before the retirement date.

Goals & Outcomes​

I aligned my messaging with the Microsoft Style guidelines, stayed in compliance with our roles policies, and provided an excellent customer experience. I had the following goals and outcomes planned to acheive this:

  • Notify users 3+ years ahead to support migration planning.
  • Make sure there are clear migration alternatives stated, such as Azure Container Apps.
  • Reduce post-retirement disruption and support ticket volume.

My Role & Responsibilities​

As I took the lead for this retirement request, I performed the following:

  1. Collaborated with engineering and product teams to verify the timeline and SKU scope.
  2. Drafted stakeholder provided content using Microsoft’s retirement templates and style guidelines.
  3. Coordinated technical review and sign-offs on messaging accuracy and migration clarity.
  4. Organized subscription impact analysis to customize communication targeting.
  5. Coordinated publication via Azure’s internal content management pipelines.

Analysis​

When performing the editorial and having it approved I had the following self analysis for the impact of this communication:

  • Early-stage guidance helped reduce migration issues.
  • Reinforced trust through transparency and strategic planning.

Key Skills Demonstrated​

  • Technical writing aligned to corprate setting in this case Microsoft editorial standards.
  • Cross-functional collaboration with engineering, product, and PMM teams.
  • Strategic communication planning for long-term retirements.

Conclusion​

I wrote this documentation page as a self analysis for my previous technical writing work. This explains my thought process and goals when performing editorial work for communications within this nature.

This also demonstrates my understanding with creating content with CDMs such as Docusaurus and deploying it as a GitHub page for public viewing.

This sample is part of my technical writing portfolio.