3rd Party Services

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.

Title: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online User impact: Users may be unable to create SharePoint knowledge agents using Microsoft 365 Copilot in SharePoint Online. More info: When users attempt to create a SharePoint knowledge agent using Copilot in SharePoint Online, they may receive an error that states, “We couldn't verify your license.” Current status: We're continuing to monitor the rate of the deployment's progression through the impacted environment in an effort to establish a timeline for remediation. We'll aim to provide an update on this when possible. Scope of impact: Any user attempting to create SharePoint knowledge agents using Copilot in SharePoint Online may be affected. This information may be updated as our investigation continues. Root cause: A recent service change had a missing configuration that's preventing the licensing from being fetched and validated, causing impact. Next update by: Wednesday, October 28, 2026, at 7:00 PM UTC

We will be upgrading our ClickHouse clusters during this time period. Certain queries may fail or timeout as we roll nodes

The root cause has been identified as undersea cable issues affecting Azure infrastructure. The impact is highest for South Africa, which has the longest network path to Australia. Requests from South Africa to Azure DevOps organizations hosted in Australia are seeing an availability impact of around 6%. We expect improvement by October 26 and further recovery by November 4, though both dates are tentative due to technical complexity of the issue itself.

Salesforce is aware of a publicly reported compromise of intermediate certificates issued by a third-party certificate authority. Salesforce is continuing to monitor the situation and may undertake proactive maintenance. We will provide updates here as appropriate.

The SCM 26.10 release includes the following enhancements and fixes: - Support for GlobalSign for issuing public SSL certificates. (SCM-13814) - Support for EJBCA for issuing private certificates. (SCM-14520) - SCEP RA certificates can now be created by specifying a certificate profile to issue them from. When they approach expiry, SCM will automatically issue new certificates and replace them from the certificate profile. (SCM-13303) - New date formats are available in General Settings. (SCM-10682) - Improved filtering options on Admin REST API. (SCM-14184) - Support for configuring Sectigo Orchestration Gateway's endpoints using the credential store option. (SCM-15120) - Persistent Validation DCV validations will now automatically renew every 7 days. (SCM-15339) - New option to filter domains by DCV method. (SCM-15363) - Improved handling of MS Agent disconnected notifications if the agent fails to send heartbeats but is performing other actions. Only the first notification will be sent until a heartbeat is received. (SCM-15704) Resolved: - Moving a private key to another Network Agent instance might have failed if other key migrations were already in progress. (SCM-15561) - Enrollment using EST endpoint might have failed if the account URI contained uppercase characters. (SCM-15523) - Occasionally, when editing a certificate profile for an external CA such as MS CA, a warning about the template no longer being available might have appeared. (SCM-15435) - Mark certificates orders might have remained in the applied status even after issuance by the CA. (SCM-15403) - Assigning an SSL certificate to a department via API would have failed to validate the department that had delegated access to the certificate's domains. (SCM-15171) - If the requester for a code signing certificate had a name longer than 64 characters, the request was submitted to the CA but not recorded in SCM. (SCM-14069)

Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.