Az.Functions cmdlets should support Manage Cross-Origin Resource Sharing (CORS).

[Francisco-Gamino]

To enable a similar functionality as the Az CLI, we need to have an equivalent to the following commands:

az functionapp cors add | Add allowed origins.
az functionapp cors remove | Remove allowed origins.
az functionapp cors show | Show allowed origins.

For more info, please see For more information, please see https://docs.microsoft.com/en-us/cli/azure/functionapp/cors?view=azure-cli-latest.

This will required adding 3 equivalent cmdlets.

[Francisco-Gamino]

cc: @AnatoliB @stefanushinardi

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably, @fabiocav.

Issue Details

---

To enable a similar functionality as the Az CLI, we need to have an equivalent to the following commands: ``` az functionapp cors add | Add allowed origins. az functionapp cors remove | Remove allowed origins. az functionapp cors show | Show allowed origins. ``` For more info, please see For more information, please see https://docs.microsoft.com/en-us/cli/azure/functionapp/cors?view=azure-cli-latest. This will required adding 3 equivalent cmdlets.

Author:	Francisco-Gamino
Assignees:	Francisco-Gamino
Labels:	`Functions`, `Service Attention`, `feature-request`
Milestone:	-

[AlexSchwerzmann]

Hi Is this foreseen and are there alternatives eg. with Graph API at the moment? Thanks

[Francisco-Gamino]

Hello @AlexSchwerzmann -- As a workaround for now, you can use the Az CLI. For more info, please see https://docs.microsoft.com/en-us/cli/azure/functionapp/cors?view=azure-cli-latest

[AlexSchwerzmann]

Hi @Francisco-Gamino Thanks for the answer - I'd like to adapt CORS of an Azure Function by applying PowerShell commands out of itself - not sure if that scenario would work with that client...?

[nicolashemery]

Hello, any news/timeline about porting this to powreshell functionality?