If you add it as a Cloud Management target that will achieve what you're looking to do. VMTurbo won't automatically provision or suspend any Public Cloud VMs with default settings -- it's effectively read-only by default.

By adding it as a Cloud Management target, you may get some recommendations to move VMs from your private cloud out to the cloud or vice versa (depending on how highly utilized your on-premises infrastructure is) but these won't be executed automatically either.

If you don't want to mix Azure into your existing Operations Manager environment, you could always deploy a separate Operations Manager VM for this purpose.

If i donot want to mix Azure Into exisiting Operations Manager as a target can i Launch VMTurbo Operational Manager from Azure Market Place to Manage and monitor only my Azure machines running in that subsricption.

Ahh, yes, you can do that. In a similar way, people that deploy VMTurbo in a VMware or HyperV environment can discover and control the VMware and HyperV environments that the VMTurbo VM is running inside of. After the VMTurbo VM is launched from the Market Place you just have to configure it from Target Configuration. The in-product documentation (click the cog at the top right hand side and click "Use Guide, HTML") describes how to add your Azure public cloud as a target so that you can control your Azure instances.