This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 21%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES7%3C/text%3E%3C/svg%3E)
Have a batch account with 'public network access' disabled
Followed instructions from https://video2.skills-academy.com/en-us/azure/batch/private-connectivity
by creating a private endpoint connection etc and I can see a private IP/FQDN as mentioned in that article. The IP is part of my subnet which is part of VNet as expected.
Now, how can I create a batch pool? Tried from portal.azure.com and it says "This batch account has public network access disabled and may be accessed via a private end point" ..
"code: AuthorizationFailure"
Is there not a way to click on 'Pools' in the batch account blade on portal.azure.com? It says I can access the batch account from one of the VMs on the subnet. What URL (Is it the private end point connection's FQDN?) do I use to create a batch pool through UI?
@SR-7559 You can try doing this from one of the VMs in the Virtual Network, but it is a prerequisite that you create the pools without private endpoints enabled.
Your best bet will be to remove / disable the private endpoint, create your pools, and then re-enable the endpoint.
@TravisCragg-MSFT - As you know, disabling the private endpoint to create a pool is not an option. When the batch account is created (without public IP option) for the first time, Azure portal will not allow to perform anything when "Pools" setting is clicked. It gives the same error "code:AuthrorizationFailure"
What am I missing here...
Too, has anyone tried to create a pool from portal (UI) for a batch account with public IP disabled? (either from VM on VNet or otherwise)?
My apologies, you do not need to disable the endpoints, just the Network Policies as discussed in the doc I linked above.
@TravisCragg-MSFT - Both of those policies are showing as "Disabled" on my subnet. How do I get to the next step (create a pool w/o public IPs from UI/portal) -- https://video2.skills-academy.com/en-us/azure/batch/batch-pool-no-public-ip-address#create-a-pool-without-public-ip-addresses-in-the-azure-portal
Still get "code:AuthrorizationFailure" when I click on "Pools" -- Should I be accessing portal.azure.com from a VM inside the subnet? That does not make much sense to me. How did the screenshot in the tutorial work? which PC did the user click 'pools' option from in the tutorial?
My apologies, your are doing this with a Private Endpoint and no public IP.
You will need to perform these operations from a VM in the Virtual Network. For best results, use CLI or PowerShell from within the Virtual Network.
These screenshots were likely done in a deployment that did not use Private Endpoints.
@TravisCragg-MSFT - Alright. So a batch pool can only be created through API (CLI/PS/.Net) from a VM in the VNet. Got it.
If I am using, say .Net API to create batch pool (using this example - https://video2.skills-academy.com/en-us/azure/batch/quick-run-dotnet ), would I be using the private IP of batch account since the following format will not work? Or, will the following format work?
https://mybatchaccount.mybatchregion.batch.azure.com
Is there an example like the dotnet quick start for batch account with no public IP (and pools inside it with no public IP)?
If you integrated your private endpoint with a private DNS zone, and added the DNS entry (if needed) then you will be able to resolve the FQDN to the proper IP. You can use NSLOOKUP or another DNS lookup from the VNET to see if this is working properly.
The IP is the safest and easiest option.