You’re offline. This is a read only version of the page.
We have a single installation of CRM, but multiple tenants - each tenant is configured to allow our "Tenant / Customers" to do their own development in their own tenant.
Any best practices or advice out there for code promotion / deployments / roll-up / roll-back approach and any best practices that we should implement.
Our goal is to allow the tenants maximum deployment rights while protecting the overall CRM installation, and the integrity and performance optimization of the other tenants and their productivity.
This in a enterprise level / complex environment and has a tightly controlled and managed infrastructure architecture, complex CRM security models using teams, roles, and secure data models (shared, encrypted and non-encrypted). We have over 10 tenants and 00+ users total - each tenant is configured differently, and each uses integrations, web services and other configurations to support the business units processes...
Thanks, Nancy
*This post is locked for comments
I have the same question (0)
Nancy, these best practices are normally part of the knowledge transfer activity from your implementation partner to your operations team. There are some blog articles (e.g. ayazahmad.wordpress.com/.../solutions-release-management-crm-2011) discussing the approaches available, but none of them will be tailored to the situation found in your organization.
Speak to your Microsoft partner and ask them to help you devices a set of practices suitable for your situation.
Share
Report
All responses (
Answers (
7,369
