Restore database from STR (Short Term Retention) backup on Azure SQL Managed Instance

In Azure SQL Managed Instance automated database backups help protect your databases from user and application errors, accidental database deletion, and prolonged outages. This built-in capability is available for all service tiers and compute sizes. This video describes how to restore a database from short term retention backup to Azure SQL Managed Instance. When the restore is complete, it creates a new database on the target instance.
Chapters:
00:08 Introduction
00:27 Set backup retention policies
01:00 Restore a database from short term retention
02:18 View the restored database
Recommended content:
Azure SQL Managed Instance Stop/Start how-to: learn.microsof...
Optimize cost of SQL Managed Instances with new stop-start capability: techcommunity....
What is Azure SQL Managed Instance?: learn.microsof...
What's new in Azure SQL Managed Instance?: learn.microsof...
How to do more with less in Azure SQL Managed Instance?: techcommunity....
2022 - a year of unparalleled innovation in Azure SQL Managed Instance: techcommunity....

[@gcere]

Simple video to restore a database. It's nice but what I would like to see is what would be the best approach for restoring a production database after a disaster. Example: my application uses the database named "Orders_DB". Following a problem in production at yyyy-mm-dd hh:mm:ss, I have to restore the database 5 minutes before the incident on the same database because I don't want to redeploy the application and change connection strings. Should I rename the database before doing a restore or after? What are the best practices for this kind of situation?

[@azuresqlmanagedinstance]

Short answer - you should rename problematic database and invoke PITR (point in time restore), to re-create database at desired moment T when everything was still fine. With PITR you can choose database name, so you can set it do be "Orders_DB".