I doubt. Not without a terrible SDK or Custom Activity Activity , which even then may not work. Unless you have a truly gigantic amount of workflows that need to be changed, a manual approach may be the best.
It can be a terrible hack, but you can replace the GUID instances of the development environment support account with your production copy directly in SQL Server. Not in the SystemUserBase table, but in any workflow activities, mention the support account as the CC field in the email. But this is scary.
You can also take a look at your process again; a significant part of Dynamics CRM is designed to solve support problems and includes fairly reliable tracking and storage of email; there probably should not be a need for CC this support mailbox that you are accessing.
In short . All of these options are terrible. Find a way to avoid them. :-P
source share