Changes to Fastly Application Multi-Account Management

Informational
29 January 2025, 22:00 UTC

Changes to Fastly Application Multi-Account Management

Status: closed
Date: 29 January 2025, 16:00 UTC
End: 29 January 2025, 22:00 UTC
Duration: 6 hours
Affected Components:
Fastly Fastly Application API & Configuration Management Notification Center API Services Configuration Management Services
Affected Groups:
All Public Users
Update

29 January 2025, 16:00 UTC

29 January 2025, 16:00 UTC

On the 29th of January 2025 we will be launching a new account-switching experience that is part of our continuous efforts to strengthen our security processes. 

Customers who have our multi-account user access feature enabled are anticipated to be impacted by our implementation and the below message describes how this change applies to your services.

What’s Changing?

We are deploying a re-authentication step to our account services that will trigger when users switch between Fastly accounts within the Fastly Application. This change applies to all user accounts and access levels.

To learn more about this change please read our Managing multiple accounts documentation. 

Why does it matter?

The best part? You don't have to do a thing! This change is all about enhancing security practices and ensuring that all shared information is protected under our non-disclosure agreements. Users will need to re-authenticate when switching between their different accounts within the Fastly Application.

This effort will help to better secure your accounts in the interim as we continue to develop a smoother and more seamless long term account-switching experience.

Your account will continue to operate as expected and all other products and services remain unaffected by this change.

Contact Information

Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.

Resolved

29 January 2025, 22:00 UTC

29 January 2025, 22:00 UTC

This informational post has been closed.

It will remain accessible within our Incident History https://www.fastlystatus.com/incidents.