Topic: Azure Free Credits for Mining Monero or CN-Heavy:Super Easy and Super Profitable - page 3. (Read 24184 times)

You'll get an email saying that they made the change (internally this is handled as a support-request). From the replies i got i have to say that azure takes the support-requests quite seriously and they are dedicated to resolve them in a timely manner.

Do they send any email to confirm or you just request and the "system" automatic increase ^^?

FYI: I requested an increase of the quota for low-priority cores (20)  for one of my batch-accounts. It took some days, but then the quota was increased without any problem.
Requesting the quota-increase is very easy. If you go to your batch-account, there's the item "quotas" on the left pane. After clicking it it will show you your current quota-settings, and there is also a button "Request quota increase". You can just click it and fill the following form to get the increased quota (processing the request will likely take some time, though). For most cases 20 low-priority cores should be enough. I haven't tried it, but i guess if you are asking for a much higher quota azure might actually ask what you are planning to do...

It's probably too early to say, but it seems the profit has increased a bit - according to cryptunit 8kH/s will net you ca. 1$ per day in XMR.

Yes, you right.
I do some mistake by del all the resources group. If you just del the pool then create a new one then you should be ok.
For now all new active Azure account can not create batch job anymore, seem they found this ^^
 

In my account all newly created batch-accounts/Pools now have a quota of 0 - probably that's why you got the message about the CPU core limit.

My existing batch-accounts/pools still have their original quotas - If you have a working batch-account it's probably a good idea to keep re-using that account for now.

I will contact the azure-support and check if they increase the quota on request.

Seem we can not create a new pool any more. Always get the error say reach CPU core limit even on new account.

What's the profit like?

The monero-RandomX-fork has gone live... everything went smoothly as far as i can tell.
Still, it's probably a good idea to check the output of your azure-pools - please write here or pm me if you are having any problems.

Hi everybody,

i have activated the changes. If you experience any problems please contact me (post here or send me a pm).

Hi everybody,

I have almost completed the preparation for the Monero RandomX-fork. The good news: you probably won't have to do anything (if you mine something else than monero your action may be required - see the technical details below).

Technical details:
* I am still running some tests, but i will activate my changes 1-2 days after this post (i will make another post here then).
* I have changed the scripts to use xmrig instead of xmr-stak. xmrig makes a smooth change to randomX much easier and i hardly found any difference in the hashrate.
* Unfortunately, however, xmrig manages the different cryptonight-variants differently than xmr-stak. The script will try to adapt the settings to make things work, though. If you are mining something else than Monero: please check your hashrate and tell me if there is any problem after the change in the scripts (like i said i will post here again in 1-2 days when i make the change).
* In my tests i have found that the F2-type of VMs are the most  cost-effective for running randomX. This means that there will be no need to change the pool-settings for the fork (currently F2 is also the most cost-effective for mining monero). You can expect a hashrate of ca. 400H/s per used core. If you have a MSDN-Enterprise subscription this should net you 7-8KH/s (whether this is a lot or not we'll only know after the fork).

You can have a look here:
https://bitcointalksearch.org/topic/m.47841140
However, as MATHReX already said: if you are using trial-accounts you will get banned with google and AWS, too.

Even in AWS or Google Cloud, you'll face issues like suspended account due to violation of terms.
I did try it on AWS for a week with some free credit during promotion a while back and the account was suspended just after a few hours and requiring a mail to re-activate the account but I was sure they won't reactivate it.
Moreover, migration to RandomX algorithm will bring a wave of CPU miners to XMR network and we will see many users trying to use on-demand computing platforms for it and their accounts getting suspended in no time.

Azure has blocked this feature....

Is there anyway to make it work on AWS or google cloud?

You're welcome 

I don't recommend mining with free credits from trial-accounts.
With that being said: If you enter your credit-card details and deactivate the spending-limit your VMs won't get shut down. You just have to remember to switch off everything before your free credits run out (your free credits will still work after deactivating the spending-limit).

Thank you for this, I just stumbled my way thru it a few hours ago. So far so good, I decided on 16 instances - averaging 108h.

I was able to start running mine with no issues. But my buddy got shut down in 4 hrs into it and be basically followed the same steps I did.

Is there any other ways to prevent MS from seeing these batches as violations?

Profitability right now is generally bad... if the past is any indication for the future then things will change with the next altcoin-season after the upcoming bitcoin-halving.
Otherwise my favorite profit-calculator is https://www.cryptunit.com/, you can have a look at the numbers there.

Is monero the most profitable thing to mine with azure right now or are there more profitable alternatives?