Hello @adedapo,
Before answering your last question: there is a PowerShell command to reset sandbox environments.
However, if you want to keep your users and permissions, I would suggest another approach, because any business units, teams etc. you set up will be removed when you reset the environment.
Instead, I would suggest to:
- Create a new environment (e.g. adedapoDev) and configure security as required
- Next, you would have 2 options:
- Use adedapoDev as a template environment that you use to create new environments
- Use adedapoDev as your dev environment that you reset every week
In the case of option 1, you would:
- Create a manual backup of adedapoDev every time you want to create a new dev environment
- Use this backup to restore adedapoDev to a new environment, e.g. adedapoDev2
- If you want, you can then delete adedapoDev2 after one week and repeat the process to create adedapoDev3
In the case of option 2, you would:
- Create a manual backup of your environment at the beginning (or end) of each week. This backup will be retained for up to 7 days.
- Develop and test in adedapoDev
- Briefly before your backup is deleted, restore the backup into the same environment (adedapoDev), thereby resetting it to the state when the backup was created.
I think these two approaches would be better than actually resetting the environment. If you want to automate and schedule this process, you could use either PowerShell or DevOps.
