Two things come to mind:
The quickest way is probably to Copy the entire IAM and just rename the application and database name, but this is tricky on a production environment.
You could also use the build in tasks to copy a user/usergroup. from one db to another. By copying and amending the stored procedure and add dbname.dbo.dtable] to the insert statements and run it from SSMS. You must also add the server to do this, or put a temporary copy of the IAM database on production to avoid having to copy between two servers.
Hi Alex,
Did Erwin's reply help you out? Feel free to create an idea for the migration of different data between IAM's.
Yes, this will work I guess. In a way. Problem is that moving data between a VM db and an Azure Db is not super easy click-and-go.
And ‘Export’ function, and ‘Import’ would be a nice-to-have, all in a wizard-like system.
But we will create a small script for this so we can do this like described.
Thnx!