How many app registration should I create for an app?

Question

I looking for best practices guidance, let's suppose an app with .net core frontend and backend and a Azure SQL and 3 environments (DEV, ACC, PROD).

is this recommended ?

• 1 subscription for DEV and ACC
• 1 subscription for PROD
• 1 App registrations record for frontend and per environment (total 3)
• 1 App registrations record for backend and per environment (total 3)
• 1 web app for frontend per environment (total 3)
• 1 web app for backend per environment (total 3)
• 3 different azure sql instance

My company policy is to have 2 subscriptions, 1 for PROD and 1 for Dev/Acc, I cannot change that, but the rest is free.

Answer 1

Hi @Ernesto ,

Thanks for reaching out.

It is always recommended for easier operations and deployment roll-out, create separate environments for development, testing, and production.

Having separate app registrations for the frontend and backend per environment is also a good practice as it allows for better control over access and permissions.

Also, having separate Azure SQL instances per environment is also a good practice as it allows for better control over data isolation and security.

Personally, I would recommend to go with above approach. This helps with resource and cost isolation, security, and easier management of the different environments.

Hope this will help.

Thanks,

Shweta

Please remember to "Accept Answer" if answer helped you.

Answer 2

Yes, it is recommended to have separate subscriptions for DEV/ACC and PROD environments, as it helps to maintain security, compliance and administrative boundaries.

Having separate app registration records and web apps per environment allows you to manage the different authorization and authentication requirements for each environment.

Having separate Azure SQL instances per environment is also a best practice, as it facilitates better data management, backup and recovery. Additionally, it ensures that any changes made in one environment do not affect the others.

In summary, having separate resources for different environments is a good practice for managing security, compliance and administrative requirements, as well as for data management and disaster recovery.