Plugin Registration Tool Isolation Mode

In Dynamics 365, when registering plugins, you must choose an isolation mode, either Sandbox or None. Here's what these modes mean and how they differ:

1. Sandbox Isolation Mode

• Runs in an isolated environment: The code runs within a restricted, isolated environment, ensuring that it has limited access to system resources.
• Restricted permissions: The plugin can only access web resources through HTTP and HTTPS but cannot directly access local files, registry, or network resources.
• Memory & execution time limitations: Plugins in sandbox mode are limited to 2 minutes of execution time and can use only a certain amount of memory.
• Security: Thís mode ensures that plugins cannot harm the Dynamics instance or external systems. It is recommended for production environments and mandatory when using Dynamics 365 Online.
• Performance impact: Sandbox-mode plugins may be slightly slower than those running outside due to the isolation overhead.

Use case:

• Required for Dynamics 365 Online (cloud).
• Recommended for plugins from external developers or if you want to ensure that your code is sandboxed for extra security.

2. None (Full-Trust) Isolation Mode

• Direct access to resources: The code runs without restrictions, meaning it has full access to all system resources (e.g., file system, registry, network, etc.).
• Faster execution: Since the plugin runs directly without the overhead of isolation, it performs faster than sandbox plugins.
• No restrictions on execution time or memory usage: There are no limits on the execution time or memory used by the plugin.
• Security risks: If the code is not properly written or validated, it could compromise the system or access unintended resources. Only available for on-premises deployments of Dynamics 365.

Use case:

• Use this mode only in on-premises environments where you need direct access to system resources and performance is critical.

Which Mode Should You Use?

• Sandbox: If you're developing for Dynamics 365 Online or want an extra layer of security, even in on-premises deployments.
• None: If you're using on-premises Dynamics and need faster performance with unrestricted access to system resources.

In general, for most online environments, Sandbox is required. Use None only when you absolutely need more access and control in on-premises setups.