Plugin isolation mode signifies the level of security restrictions imposed on the plugin execution pipeline. The isolation mode is specified on the assembly level and not on the individual plugin step.
When a plugin assembly is registered, it can either be registered in an isolated or sandbox mode or in a none mode. The sandbox is more secure and some actions are restricted.
When a plugin is registered in a sandbox mode, although a plugin can still access the Dynamics CRM organization service and execute requests in accordance with Dynamics SDK, some of the functionalities such as accessing database or file directory are restricted. However, the plugin will still be able to access Azure Cloud Services endpoint. When a plugin is registered in the none mode, the aforementioned restrictions on a plugin won't apply. Mentioned here are some of the key differences in the two modes of plugin isolation
|
Difference |
Sandbox |
None |
|
Restricted features |
A plugin registered in the sandbox mode will not be able to access the following features:
|
A plugin registered in the none mode can access the features that are restricted for the sandbox mode |
|
Dynamics CRM online support |
Dynamics CRM online supports the execution of plugins only registered in the sandbox mode. |
Dynamics CRM online does not support the execution of plugins registered in the none mode |
|
Dynamics CRM on premise support |
Dynamics CRM on-premise supports the registration of plugins in both the modes. |
Dynamics CRM on-premise supports the registration of plugins in both the modes |
|
Run time statistics and monitors |
Dynamics CRM collects runtime statistics and monitors plugins that execute in sandbox. If the process that hosts the plugin exceeds the CPU threshold, memory, or becomes unresponsive, the process will be killed by the platform. |
No statistics and monitors are collected by Dynamics CRM for plugins registered in none |