Add support for --public-network-access for az functionapp config namespace

[HenryLGatesFoundation]

There seems to be no way of setting the publicNetworkAccess attribute value (Enabled or Disabled) of the functionapp namespace, neither during creation, nor update (with az functionapp config create|update).

This means that, although we can automate the creation of Function App Inbound Private Endpoints and Function App VNet Integrations, we must go to each Function App and manually disable Public Access to our Function Apps.

Describe the solution you'd like
I'd simply like/expect to be able to run any of the following commands:

• az functionapp config --name myFA --resource-group myRG --public-network-access enabled

• az functionapp config --name myFA --resource-group myRG --public-network-access disabled

• OR -

• az functionapp config --ids myFAID --resource-group myRG --public-network-access enabled

• az functionapp config --ids myFAID --resource-group myRG --public-network-access disabled

Describe alternatives you've considered
It doesn't exist under "az webapp config set" either.

Additional context
Without this, everyone who wishes to create or manage secure Function Applications must go directly to each resource and toggle this attribute, manually, while the rest of the same page can be updated via the Azure CLI:

[yonzhan]

route to CXP team

[navba-MSFT]

@HenryLGatesFoundation Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.

[navba-MSFT]

@HenryLGatesFoundation Could you please try the below command ?

az resource update -g myRG -n myFA --resource-type Microsoft.Web/sites --set properties.publicNetworkAccess=Enabled

Awaiting your reply.

[HenryLGatesFoundation]

Yes, the use of the generic "resource" does work.

[navba-MSFT]

@HenryLGatesFoundation Thanks for getting back. Does the above command suffice your requirement or do you still need the CLI command?

[HenryLGatesFoundation]

I believe everyone who might run across this post would/should be able to use it. But if you, or the team, could be so kind as to place it in a more intuitive "or correct" namespace for customers, that would be very much appreciated. Is that possible?