Azure-docs: Collections supported?

[nprieto95]

I'd like to have my cors allowed origins defined in named values;
Since the cors policy does not allow comma-separated origins and instead requires one node per origin, I was wondering how I can manage dynamically setting origins?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 336f4e1b-62f2-fde1-d31f-a7cc30fc857c
• Version Independent ID: d5ccdd33-80d7-035f-1941-cc8a90c331ab
• Content: How to use named values in Azure API Management policies
• Content Source: articles/api-management/api-management-howto-properties.md
• Service: api-management
• GitHub Login: @vladvino
• Microsoft Alias: apimpm

[SadiqhAhmed-MSFT]

@nprieto95 Thanks for the comment. We are actively investigating and will get back to you soon.

[PramodValavala-MSFT]

@nprieto95 Apologies for getting back on this sooner. Unfortunately, the CORS policy does not support collections out of the box. Please feel free to raise a feature request to support them.

Since the CORS policy is to send the right headers, you could use policy expressions and the set-header policy to set the right headers manually instead. Note that you will have to handle the OPTIONS request manually as well by defining a separate API Operation and respond using the return-response policy.

Since there is no doc related changed required here, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.