Things to note when registering a Plugin/custom workflows in Sandbox mode

Sandbox mode can also be referred isolation environment. Lets us see some Pros and Cons when registering the plugins/custom workflow activities in Sandbox mode.

Advantages:

  • Can make use of the full power of the Microsoft Dynamics CRM SDK
  • Have access to external endpoints like Azure Cloud Services.
  • CRM collects run-time statistics and monitors plug-ins and custom workflow activities that execute in the sandbox.
  • If code exceeds CPU Memory or is otherwise unresponsive, it would be killed by the platform
  • More secure, collects run time statistics and reporting
  • Platform collects runtime statistics and were populated after 30 mins to 1 hr
  • Can access the network through HTTP, HTTPS protocols
  • Anonymous authenication is allowed for plugins

Disadvantages:

  • Access to localhost (loopback) is not permitted.
  • IP addresses cannot be used, web address requires DNS name resolution

Discover more from ECELLORS CRM Blog

Subscribe to get the latest posts sent to your email.

Unknown's avatar

Author: Pavan Mani Deep Y

Passionate for Power Platform. A technology geek who loves sharing the leanings, quick tips and new features on Dynamics 365 & related tools, technologies. An Azure IOT and Quantum Computing enthusiast...

2 thoughts on “Things to note when registering a Plugin/custom workflows in Sandbox mode”

  1. Heya i am for the primary time here. I found this board and I to find It truly helpful & it helped me out a lot. I am hoping to offer something again and help others like you helped me.

    Like

Leave a reply to Jessie Fickes Cancel reply

Discover more from ECELLORS CRM Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading