Hi HooftG,
The CloudGaurd Controller has a sleep time of 30 between each cycle.
You can reduce the sleep time between each cycle, as it's a configurable parameter, but depending on the rest of your environment you run the risk of the cloud vendor throttling you if you exceed their API call limit.
I'm assuming that you don't mean that 30 seconds is too long and that for some reason changes take longer to propagate in your environment.
If you are seeing delays, it might be something worth looking into - for example it could be related to what I mentioned above and that your environment has multiple elements which are sending API calls causing Azure to throttle your connection and making many API calls fail,
I've seen a similar case where a customer had a malfunctioning 3rd party asset which was spamming Azure and causes severe delays in updates as a result.
Obviously the above is just one possible explanation and might not be relevant in your case.
It might be beneficial to run some empirical tests - import a tag into your policy, make a change in Azure and check how long it takes for the change to appear in your dashboard.
HTH
Yonatan