Migrating to the Latest Version of CIPP
Last updated
Was this helpful?
In July of 2026, we were pleased to announce new infrastructure for CIPP. Migrating to the new infrastructure gains speed and controlled cost. Newly deployed CIPP instances are already on the new infrastructure.
Navigate to management.cipp.app.
If you haven't already completed the SSO set up steps you will be prompted to complete that setup when you first open CIPP again. See Setting Up SSO and Getting Access to CIPP
If you had a custom domain on your old version of CIPP, you'll need to migrate it too. To migrate a domain to the new generation of CIPP, point its existing CNAME record at CIPPXXXX.azurewebsites.net, then add the domain here. It will move over automatically. If a TXT record named asuid.<your domain> exists from your previous setup, remove it — domain-verification TXT records are no longer used, and a leftover one blocks validation. This step must be performed in the management portal.
Users who load your pre-existing custom domain prior to the certificate being provisioned will be redirected to the new Azure URL. After the certificate is provisioned they may still experience this behavior as their local DNS cache will remember the redirect. Please direct those users to clear their cache.
More information coming at a future date. We are only handling CyberDrain hosted migrations at this time.
Last updated
Was this helpful?
Was this helpful?

