Roadmap questions: APIM self-hosted gateway on Workspaces, self-hosted gateway on V2 SKUs, and DRS 2.2/OWASP support for AGC WAF

Question

Roadmap questions: APIM self-hosted gateway on Workspaces, self-hosted gateway on V2 SKUs, and DRS 2.2/OWASP support for AGC WAF

Mouad MIKOU 25

Hi Team,

I'd like to ask about the roadmap for a few gaps I've run into across API Management and Application Gateway for Containers. Posting all three together since they're related to gateway/networking capability parity across tiers.

1. Self-hosted gateway support for Workspaces Current docs state that a workspace can't be associated with a self-hosted gateway — only the default managed gateway or a dedicated workspace gateway (Premium tier). Is there a roadmap item to let workspaces route through a self-hosted gateway, for hybrid/on-prem scenarios where teams want workspace-level delegation and an on-prem data plane?

2. Self-hosted gateway on V2 SKUs Per the V2 tiers documentation and confirmed in other Q&A threads, self-hosted gateways are currently only available on Developer and Premium (classic) tiers — not on Basic v2/Standard v2/Premium v2. Is there a plan to bring self-hosted gateway support to the V2 SKUs? This would help customers who want V2's simplified networking/scaling but still need a hybrid/on-prem gateway option.

3. DDoS Protection and DRS 2.2/OWASP support on Application Gateway for Containers WAF AGC's WAF currently only supports DRS 2.1 (not the newer DRS 2.2, which is already GA on Application Gateway and Front Door), and the HTTP DDoS ruleset is explicitly listed as not currently supported on AGC. Are there plans to bring AGC WAF up to parity with DRS 2.2 and add DDoS protection support?

Any insight into timelines, preview status, or whether these are tracked feature requests would be appreciated. Happy to file these individually as separate threads if that's preferred.

Thanks!

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-11T06:55:33.03+00:00

Hi @Mouad MIKOU ,

Thanks for reaching out to Microsoft Q&A.

We don't have roadmap/timeline information in the provided documentation. What we can confirm from the APIM gateway feature comparison is that Workspaces are treated as a separate gateway category from self-hosted gateways, and the current feature matrix does not describe Workspace being routed through a self-hosted gateway.

For self-hosted support across V2 tiers and for AGC WAF rules parity (DRS 2.2/OWASP/DDoS), the provided materials don’t include a support matrix or roadmap details, so we can’t confirm plans or ETA from this data.

If you share your exact SKUs/regions and what behavior you’re seeing, we can help validate the current support boundaries and, if applicable, help you file/troubleshoot feature requests.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mouad MIKOU 25 Reputation points

2026-07-11T08:53:57.1066667+00:00

Thanks for the details, we are trying to setup a shared APIM to be used for AKS APIs. And we are trying to cover both cases when APIs are used only internaly on private network, and when used on public. Since its AKS, we are trying to get use of AGC as ingress to expose the public APIs. But this looks impossible with managed gateways.

Answer accepted by question author

Alex Burlachenko 25,285 MVP Volunteer Moderator

hi Mouad MIKOU & thx for sharing urs issue here at Q&A portal,

those are all reasonable requests, but I don't think anyone outside the product teams can give a reliable roadmap or ETA.

As of today, the documentation still reflects the current limitations

Workspaces support the managed gateway or a workspace gateway, but not a self-hosted gateway.

Self-hosted gateways are supported on the classic Developer and Premium tiers, not the v2 SKUs.

Application Gateway for Containers WAF doesn't yet have feature parity with Application Gateway WAF in areas such as DRS 2.2 and the HTTP DDoS ruleset.

I really haven't seen any public announcements or preview programs that change those statements, so I wouldn't plan around those capabilities being available until Microsoft announces them. I'd recommend splitting these into separate feature requests if you're looking for product team feedback, as they're owned by different engineering teams (APIM vs. Application Gateway for Containers). That also makes it easier for Microsoft to track customer demand for each feature individually. Hopefully someone from the APIM and AGC product teams can comment if any of these are actively on the roadmap but Microsoft generally doesn't publish timelines for unreleased features.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

Mouad MIKOU 25 Reputation points

2026-07-13T10:43:13.6533333+00:00

Thans for your answer, clear enough.
Alex Burlachenko 25,285 Reputation points MVP Volunteer Moderator

2026-07-13T11:00:54.2166667+00:00

Mouad MIKOU u are welcome!

rgds,

Alex

1 additional answer

Your answer

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-07-11T06:55:33.03+00:00

Hi @Mouad MIKOU ,

Thanks for reaching out to Microsoft Q&A.

We don't have roadmap/timeline information in the provided documentation. What we can confirm from the APIM gateway feature comparison is that Workspaces are treated as a separate gateway category from self-hosted gateways, and the current feature matrix does not describe Workspace being routed through a self-hosted gateway.

For self-hosted support across V2 tiers and for AGC WAF rules parity (DRS 2.2/OWASP/DDoS), the provided materials don’t include a support matrix or roadmap details, so we can’t confirm plans or ETA from this data.

If you share your exact SKUs/regions and what behavior you’re seeing, we can help validate the current support boundaries and, if applicable, help you file/troubleshoot feature requests.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Mouad MIKOU 25 Reputation points

2026-07-11T08:53:57.1066667+00:00

Thanks for the details, we are trying to setup a shared APIM to be used for AKS APIs. And we are trying to cover both cases when APIs are used only internaly on private network, and when used on public. Since its AKS, we are trying to get use of AGC as ingress to expose the public APIs. But this looks impossible with managed gateways.
Mouad MIKOU 25 Reputation points

2026-07-13T10:43:13.6533333+00:00

Thans for your answer, clear enough.
Alex Burlachenko 25,285 Reputation points MVP Volunteer Moderator

2026-07-13T11:00:54.2166667+00:00

Mouad MIKOU u are welcome!

rgds,

Alex

Answer 1

Christos Panagiotidis 3,551

Hi! Based on the currently documented capabilities, workspaces cannot use the APIM self-hosted gateway, and the v2 SKUs do not provide self-hosted gateway parity with the classic Developer/Premium tiers. AGC WAF capability also remains dependent on its documented supported rulesets. Microsoft generally does not confirm roadmap dates through Q&A. I would submit these as three separate feedback requests and design against currently available features until a public preview is announced.

0 comments