| Sitecore via Azure Marketplace | Service is operating normally |
| Sitecore via AppSource | Service is operating normally |
| Device Detection | Service is operating normally |
| IP Geolocation | Service is operating normally |
Feb 16, 2021
IP Geolocation Service Scheduled Maintenance
As part of cloud infrastructure monitoring activities, Sitecore Cloud Operations team identified an event that we would like to bring to your attention. In case you have any follow up questions regarding the event, please do not hesitate to raise a support case on that matter from the home page of Sitecore Support & Self-Service Portal.
Planned maintenance is Scheduled for Sitecore IP Geolocation service. During the maintenance window, customers might get intermittent errors.
Completed Scheduled Maintenance: Sitecore Cloud Operations team has successfully finished the scheduled maintenance.
Feb 09, 2021
Azure portal issues accessing resource health feature
Starting at 06:21 UTC on 08 Feb 2021, some customers may experience issues accessing Resource Health feature through the Azure Portal.
Workaround: Customers should be able to use CLI or PowerShell as a workaround. More information can be found here: https://docs.microsoft.com/en-us/rest/api/resourcehealth/
Current Status: Microsoft engineers are continuing to investigate and are working on developing and verifying a fix. The next update will be provided in 3 hours or as events warrant.
MITIGATED: Preliminary Root Cause: MS Azure determined that a recent deployment task contained a configuration error, which resulted in issues when accessing Resource Health through the Azure Portal.
Mitigation: Following safe deployment procedure MS Azure expedited a hotfix deployment to address the configuration error, mitigating the issue.
Identified:
Feb 08, 2021
Azure Monitor in Canada Central may experience misses/delayed Log Search Alerts for resources in this region
Starting at 14:38 UTC on 8 Feb 2021 few customers using Azure Monitor in Canada Central who may experience misses/delayed Log Search Alerts for resources in this region. Microsoft Engineers have identified a preliminary root cause and are investigating mitigation options. The next update will be provided in 60 mins or as events warrant.
Feb 02, 2021
Azure SQL Database Connection Errors
Outage : Between 17:00 UTC on 01 Feb 2021 and 15:05 on 02 Feb 2021, Customer using Azure SQL Database may have experienced connection errors when accessing your database. Certain service management operations may also have failed.
Impacted region(s): Australia East; Australia Southeast; East US; East US 2
Preliminary Root Cause: Microsoft have identified that the issue was caused by a recent deployment which resulted in a configuration change. This introduced a breaking change that caused impact to service management operations and/or resulted in the service becoming unavailable.
Mitigation: Microsoft rolled back the deployment to revert the configuration change and returned to a previous version. Impacted SQL gateways were also restarted to mitigate the issue.
Next Steps: Microsoft sincerely apologize for the impact to affected customers. Microsoft will continue to investigate to establish the full root cause and prevent future occurrences.
Identified:
Dec 15, 2020
Phase 5: Azure SQL Database traffic migration to newer Gateways
During daily monitoring activities, Sitecore Cloud Operations engineers found a planned maintenance activity on Microsoft Azure due to which SQL database connectivity might be affected for the customer connecting to database.
Gateways built on new hardware are being added to SQL DB in various regions. This will allow logins to be serviced by more than one Gateway in these regions, leading to better response times and reduced latency. This will change the public IP address to which DNS will resolve for your SQL Database hosted on East Asia and Australia Central effective January 31, 2021.
Impact: Potential loss of connectivity for Customers using IP restriction rules on Azure SQL Databases. For the majority of customers, we expect this change will not impact connectivity to SQL Database. However, we recommend that you white list IP addresses for all Gateways East Asia and Australia Central, as outlined in the table here.
New SQL Gateways are being added to the following regions:
East Asia: 191.234.2.139, 52.175.33.150, 13.75.32.4
Australia Central: 20.36.105.0
These SQL Gateways shall start accepting customer traffic on January 31, 2021.
Scheduled: This migration has been scheduled on January 31, 2021.