Windows Azure Pack / SMA: How to fix when some VM Clouds Automation Triggers does not work

In WAP VM Clouds provider, we are able to set trigger on different actions.



Yesterday, in a new test environment, I had a problem that some of them would not trigger.

When I tested Subscription trigger, it worked fine, but none of the others worked.


Luckily I asked my MVP network for help, and fellow CDM MVP Stan showed me the path to the fix! (Check his blog here:

He said some actions are handled directly by WAP, and some are handled by SPF.


The SMA Web service has to use a valid certificate that is trusted by the SPF server!


It is described here


“For VM Clouds to trigger runbooks in Service Management Automation, the Service Management Automation web service certificate must be trusted on the computer running Service Provider Foundation. “

Leave a Reply