Answered

Power Pages Tenant Migration - Using Same URL

(0) Share

Report

Posted on by FluidPowerAutom

Hi everyone,

We're planning on moving DEV, TEST and PROD environments to a new tenant, each of which contains a Power Pages site. We're not too precious about the URLs for DEV and TEST, but we really need to keep the same URL for the PROD site as there are ~5000 users with it bookmarked!

It's a .powerappsportals.com URL. I've given it a dry run by trying to repoint the current DEV site to TEST (changing TEST's URL, then changing DEV to the old TEST URL). I'm getting a DNS cache validation issue (I think) but can't see any way of repointing. Does anyone have any ideas? Is this even possible?

Thanks for your time,

Josh

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Christian Leverenz 1,214 on at

Like (1)

Report
Copy link

Link copied!

Hi @FluidPowerAutom ,
The connection between the url and the website is created within the table website bindings. So, for a given url you can switch the website which is displayed for that url by changing the website.
Nevertheless, this is not quite your challenge. What should work is: delete the old portal (in make.powerapps.com for example). This frees up the url but leaves all data within the dataverse. Then register a new portal with this freed url on another tenant pointing to the website you transported before to the new tenant of course 🙂
(of course you should try this in a dev/testscenario b4 🙂 )

Just curious: when you change the tenant, you change the dataverse, right? How do you get all the userdata from one system to another? Do you transport it with datamigration or other fancy tools or do you make a redeploy of the dataverse?

Hope this answer helps a litle bit,

Was this reply helpful? Yes No
Verified answer

FluidPowerAutom 12 on at

Like (1)

Report
Copy link

Link copied!

Thanks for your response @chleverenz. I'd left it for a couple of hours and the DNS records must have expired (maybe after an hour looking at the CNAME record on https://dnschecker.org) because the old TEST URL now points to the DEV site! Deleting the old portal like you suggested might also work.

Regarding your question, yeah changing tenants means a completely blank Dataverse. The plan is to migrate the solution first to create the customisations, migrate the website records and then do a data migration on the other data tables to get them across. Once we do that for one environment, we'll probably copy it to make a DEV / TEST env.

Was this reply helpful? Yes No