BSS and Storefront Application Service Interruption During Planned Version Upgrade

Τhe BSS and Storefront applications experienced a planned service interruption during the deployment of a new application version.

Unlike the previous incidents involving Azure Load Balancer functionality and backend server performance, this incident was not related to the load balancer or underlying infrastructure. The service interruption was a direct result of the application upgrade process.

Version upgrades are normally scheduled during weekend maintenance windows to minimize customer impact. However, due to release challenges encountered with this specific version, deployment could not be completed during the planned maintenance period. As a result, the upgrade was performed during early business hours, resulting in a brief service interruption.

Business Impact

• The BSS and Storefront applications were unavailable for approximately five minutes during the deployment.
• Users were temporarily unable to access application services.
• No data loss or integrity issues were identified.
• Service was fully restored following successful completion of the upgrade.

Root Cause

The service interruption resulted from the deployment of a planned application version that required a brief outage during installation.

This deployment was executed outside the standard weekend maintenance window because the release encountered challenges that prevented it from being delivered during the planned maintenance schedule. Completing the deployment was necessary to deliver the required application updates.

The incident was not related to the previously reported Azure Load Balancer routing issue or the backend server performance incident.

Corrective Actions

Completed

• Successfully deployed the new application version.
• Validated BSS and Storefront functionality following deployment.
• Confirmed normal service operation through monitoring.

Future Improvements

• Continue scheduling application upgrades during planned weekend maintenance windows whenever possible.
• Enhance release planning to reduce the likelihood of deployments outside approved maintenance windows.
• Review deployment procedures to identify opportunities for reducing or eliminating service interruption during future upgrades.
• Improve customer communication by providing advance notification whenever an application upgrade must be performed outside the normal maintenance window, including the expected impact and duration.
• Continue improving release readiness and testing to minimize delays that could affect planned deployment schedules.

Relationship to Previous Incidents

This incident is independent of the previously reported incidents involving:

• Azure Load Balancer traffic routing failure.
• Backend server performance degradation.

No evidence indicates that the service interruption was related to infrastructure, networking, or load balancing. The interruption was solely attributable to the planned application deployment activities.