Indeed. And I'm tried to move to alternative script/github (fork: https://github.com/GiorgioBrux/azure-cloud-mining-script), but still workers on supportxmr are offline.

Others also experience issues? On supportxmr I don't see any workers anymore... But my pools in azure are still active?

Indeed. Terms are updated:


Source: https://azure.microsoft.com/en-us/offers/ms-azr-0029p/

So newer subscriptions will be disabled when performing crypto mining.

Since around two weeks the hashrate results (at supportxmr) are very unstable and have a much lower result overall (around 70% compared to before). Do others also experienced this? Is this due to something changed or wrong in the scripts? Or has Microsoft something changed on Azure (for Low Priority VM's)? Or maybe something is changed at SupportXMR?

Are others experiencing the same? Or someone have an explenation or fix?

supportXMR.com Login - password question.

I have some questions about this system, maybe some of you can help me with that: 

* can somebody else (who somehow knows my wallet and guesses that i mine at supportxmr.com) set a password and mess with my settings?

* how to change the password after multiple miners are running?

* can I hide the mining results info, or set it behind a password?

* What happens if i change the password through the gui at supportXMR.com? Will my miners be rejected if it is still using the old password?

Which VM type performs better?

• F2
  F2s
  F2s_V2

I have a lot of VisualStudio subscription to run Batch accounts.

But I'm unable to run Low-priority cores. Because for all new Azure Batch accounts; this is set to 0. For all regions/locations and for all VM types...

So only option is to use Dedicated Cores, which is 4 times more expensive... Hopefully they will remove the quota soon.

See https://docs.microsoft.com/nl-nl/azure/batch/batch-quota-limit for more information.

Quota is there also for paid subscriptions. Had already a support-case with Microsoft Support for expanding this quota, but this is not possible for Low-priority cores...

Earlier created batch accounts, don't have the limit set...