Azure Disk created with Public Endpoint, no option to make it private

This issue was originally opened by @NickLarsenNZ as hashicorp/packer#10535. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.

---

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Using the azure-arm builder, a Disk is created with "Public Endpoint" enabled, even when building on a private network.

It would be great to have a config option to make it private (and make that the default).

Use Case(s)

Organisations with controls to prevent public disks being created.

Potential configuration

Either add an option to allow the disk to be public, but default to private:

   "builders": [
        {
            "type": "azure-arm",
            ...
            "pubic_disk_access": true
        }
   ]

Or, hard code it to private (I can't think of a case where it would need to be public).

Maybe even the "Deny All" option would work, I'm not quite sure if private access is even required for mounting the disk to a VM.

Potential References

• https://docs.microsoft.com/en-us/azure/virtual-machines/disks-enable-private-links-for-import-export-portal