If you are trying to license a SQL Server in Azure, your best bet is to follow the Azure Specific guidance. If you want to continue down the dual core road, you can try the HB-Series VMs.
In Azure, when you use marketplace images you are charged for the licensing costs of SQL & Microsoft automatically. If you have any specific questions on this, please let me know.
@StaffanWilln-5044 Can you view the resource group 'sekia' in the portal, and view other resources in that resource group?
If so, this is an issue with your subscription / portal and your next steps will be to follow up with support. If you do not have a support plan, please let me know.
@AndreiKazakou-6380 Yes, that should work without issue. You can add any tags, as long as the name & region exist, it will use that resource group.
Thanks for the clarification! I see what you are referring to with the listed CPU type & listed maximum throughput. I will need to deploy a few VMs and see if this behavior is similar across different VM sizes, or if this is something isolated to this particular size, or possibly an issue with your individual VM.
Your size is dependent upon the hardware that you are allocated to when you create the VM. You do not have any control on which one, Azure chooses that for you when you allocate. You can try to get a different host by stopping & starting the VM, or resizing the VM to a different size and then sizing it back.
This is possible using Application Gateways, but not Azure Load Balancer
Azure Application Gateways can use internal IPs that are connected via a VPN or ExpressRoute.
I would do some testing to verify the functionality of how LUNs get mapped to your VM vs your VM object in Azure. It typically isn't a best practice to spam attach / de attach operations, it might be better to have a few VMs with larger attached storage and direct requests that need more storage to those VMs.