This article outlines the service provided by Sitecore for the removal of an Application Gateway (AGW) with Web Application Firewall (WAF) functionality.
It details the situations in which you should create this service request (SR), the prerequisites, considerations, and service level agreement (SLA) associated with the service.
You should create this service request when you want to delete an existing AGW including the WAF policy from a PaaS 1.0 environment. This is typically required when consolidating resources, updating your network infrastructure, or changing your content delivery strategy.
*If the target AGW (+WAF) was created on your own (not created by Sitecore), it will be treated as your custom resource and the deletion is out of our service scope. In this situation, you should do the deletion on your own.
Before creating the SR to remove the AGW, ensure the following steps are completed:
The removal process for the AGW (including WAF policy) will be completed within 3 business days from the creation of the service request.
The Sitecore Managed Cloud team provides Limited Support for Managed Cloud Standard customers using the Azure AG + WAF enabled product with their Sitecore implementation. This Limited Support scope includes the Azure WAF component with Azure Application Gateway.
The following tables indicate the roles and responsibilities associated with key considerations when planning the removal of Application GW (WAF).
Task |
Sitecore |
Customer |
Add all custom domain names to the Content Delivery (CD) endpoint |
C, I |
R, A |
Upload all custom domain certificates to the CD endpoint |
C, I |
R, A |
Remove IP restrictions on the CD endpoint |
C, I |
R, A |
Update custom domain DNS records from AGW public IP to CD endpoint |
C, I |
R, A |
Conduct testing to ensure all custom domains are functioning correctly |
C, I |
R, A |
Create a Service Request (SR) to remove the AGW, including the WAF policy |
C, I |
R, A |
Update the CD ping test URL to point to the CD |
R, A |
C, I |
Modify the TM endpoint list, DR script, and DR ping test |
R, A |
C, I |
Remove the four AGW-related resources:
|
R, A |
C, I |
Legend:
Impact on Services: Be aware that removing the AGW might temporarily affect traffic management and load balancing. Plan accordingly to minimize disruptions.
Backup and Recovery: Ensure all relevant data and configurations are backed up before initiating the removal process. In case of any issues, having a backup will facilitate quicker recovery.