Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.
Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version): Not sure what to put here
The operating system my web server runs on is (include version):
Windows Server 2022 Datacenter Azure Edition 21H2
My hosting provider, if applicable, is: Azure VPS
I can login to a root shell on my machine (yes or no, or I don't know): YES
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Not sure what to put here
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.24.0
Anyhow, it looks like your website doesn't answer on port 80. Because you're using --standalone (why?) we can be confident it's listening, so it must be some firewall: either your machine's or your provider's.
Before I try Certbot I was running my servers with NGINX on port 80 and it was working well.
Since Certbot asked me to put all down, I stopped NGINX and all my servers (just to be sure).
I mean, you use it on servers that don't have a webserver of their own, like smtp/imap ones, or you use it when you have a cluster and every node is reverse proxying the /.well-known/acme-challenge directory to the single server that runs certbot --standalone.
By putting that inside a server block that listen to all domains, I have set up my nginx to send all request for that path to another webroot which I then give to my acme client (all other paths get redirected to https)
At some point during your initial test port 80 was blocked, that's why standalone didn't work (I assume you are not doing any geographic or IP range filtering on connections in your firewall).
Check your website works normally over http (it currently does) [Edit: correction, your website does not currently connect on port 80, so you need to fix this first or at least ensure that port 80 is open at both the VM networking settings and your server firewall]
Stop nginx to ensure port 80 is freed up and nothing is listening. [Ensure there are no nginx processes running]
Run certbot standalone to get your certificate. This part should currently work OK if nothing else is using port 80.
Update your nginx configuration to point to the new certificate files for https.
Could you clarify something for me? Since NGINX is completly stopped when I ran Certbot, whit is it important excatly?
I mean, Certbot should be able to create the certificate with or without NGINX, with standalone or webroot, isn't it?