We need to be able to host CRM Portals ourselves. There are many technical reasons why this is needed, a few which I can think of:
- Ability to have full control over the hosting infrastructure
- Ability to have full control over where their data resides
- Ability to have more access to the running state of the application than what's available in SaaS (e.g. application exception information)
- Ability to control when an application is upgraded (or never upgrade if that is the best business decision)
Here are some other non-technical (business?) things to consider:
- What is the opportunity cost of ignoring on-premise customers?
- Dynamics CRM has been marketed for years as being hosted on-premise and online, via the 'power of choice'. Are we now losing choice?
- On-premise hosting is one of the biggest differentiators of the Dynamics CRM platform to the competitors
JoeF-MSFT
on:
Receipt Processing cannot read the majority of rec...
on:
Automatic HyperLink conversion in the Power Apps r...
on:
Consistent order of object design properties
on:
Security in Dataverse for Teams
on:
Option to view all the formulas used in an App at ...
Thank you for your feedback. This would be important for many of our enterprise customers that wish to deploy portals in their own Azure subscription to manage it alongside all of their other web properties.