Flex Consumption in a Managed Application

Question

Flex Consumption in a Managed Application

Alexander Clouter 21

I have a Marketplace (and Service Catalog) Managed Application solution that uses Flex Consumption.

I migrated from Consumption (Y1) recently to help my consumers avoid running into Azure's regional capacity problems.

The problem is Flex Consumption is only available in a limited number of locations, a list of which you can get from:

az functionapp list-flexconsumption-locations

Managed Applications allow you to filter locations that the solution can be deployed and at the moment I use Microsoft.Web/serverfarm but this is a superset of the regions (meaning it contains more) than where Flex Consumption will work.

What should I use instead? I do not want to manually track, populate and publish a custom 'location' restriction list by way of 'location -> allowedValues'.

Currently I have something like this below and what do I need to do to amend this to automatically restrict the valid location lists the consumer can choose from where Flex Consumption is available?

{
  "$schema": "https://schema.management.azure.com/schemas/0.1.2-preview/CreateUIDefinition.MultiVm.json#",
  "handler": "Microsoft.Azure.CreateUIDef",
  "version": "0.1.2-preview",
  "parameters": {
    "config": {
      "isWizard": true,
      "basics": {
        ...
        "location": {
          "label": "Region",
          "toolTip": "Select the closest region to your location",
          "resourceTypes": [
            ...
            "Microsoft.Web/serverfarms",
            ...
          ]
      }
    },
    "resourceTypes": [
      ...
      "Microsoft.Web/serverfarms"
      ...
    ]
  }
}

Suchitra Suregaunkar 11,470 Reputation points Microsoft External Staff Moderator

2026-01-19T01:52:05.3166667+00:00

Hello Alexander Clouter

Thank you for posting your query on Microsoft Q&A platform.

Currently we are looking into your issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 11,470 Reputation points Microsoft External Staff Moderator

2026-01-19T16:30:11.75+00:00

Hello Alexander Clouter

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

Answer accepted by question author

1 additional answer

Your answer

Suchitra Suregaunkar 11,470 Reputation points Microsoft External Staff Moderator

2026-01-19T01:52:05.3166667+00:00

Hello Alexander Clouter

Thank you for posting your query on Microsoft Q&A platform.

Currently we are looking into your issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 11,470 Reputation points Microsoft External Staff Moderator

2026-01-19T16:30:11.75+00:00

Hello Alexander Clouter

Please let us know if the suggested resolution helped/ addressed your concern. If it did, we’d appreciate your feedback on the proposed resolution as it helps others with similar issues.

If the resolution did not help, feel free to share more details about the challenge you’re still facing. Any additional information such as your current issue or specific errors will help us perform a deeper analysis and provide more targeted guidance.

We’re happy to continue assisting and work with you toward the right solution.

Thanks,

Suchitra.

Answer 1

You can’t get this “for free” via resourceTypes.

In createUiDefinition, the location picker can only be constrained by:

resourceTypes (regions that support a resource type), and/or

allowedValues (a hard list you provide).

Flex Consumption availability is a plan/SKU capability, not a distinct resource type that the location control can target, so Microsoft.Web/serverfarms will always be a superset.

What people do in practice:

Maintain allowedValues (yes, manual), or

Build a dynamic dropdown backed by Microsoft.Solutions.ArmApiControl (or your own endpoint) that returns the “Flex supported locations” list, and bind that to a Microsoft.Common.DropDown. ArmApiControl is specifically meant to populate dynamic values from an API response.

If you want “no manual tracking”, option #2 is the closest: host a tiny service that returns the output of az functionapp list-flexconsumption-locations (or equivalent), and have the UI read that list at deploy time.You can’t get this “for free” via resourceTypes.

In createUiDefinition, the location picker can only be constrained by:

resourceTypes (regions that support a resource type), and/or

allowedValues (a hard list you provide).

Flex Consumption availability is a plan/SKU capability, not a distinct resource type that the location control can target, so Microsoft.Web/serverfarms will always be a superset.

What people do in practice:

Maintain allowedValues (yes, manual), or

Build a dynamic dropdown backed by Microsoft.Solutions.ArmApiControl (or your own endpoint) that returns the “Flex supported locations” list, and bind that to a Microsoft.Common.DropDown. ArmApiControl is specifically meant to populate dynamic values from an API response.

If you want “no manual tracking”, option #2 is the closest: host a tiny service that returns the output of az functionapp list-flexconsumption-locations (or equivalent), and have the UI read that list at deploy time.

Alexander Clouter 21 Reputation points

2026-01-16T09:11:04.1266667+00:00

Thank you your answer, I suspected this would be as much the case.

I likely will choose to use Microsoft.Solutions.ArmApiControl but to toggle the visibility on an Microsoft.Common.InfoBox which is something I already do as I still need to retain filtering of all the other resource types my solution requires.

On a related note, I was under the impression ArmApiControl only allows you to query the ARM API (ie. Azure's management.azure.com endpoint) and not a custom endpoint? You probably could have worked around this with a Custom Resource Provider but this is now unfortunately deprecated with no other usable alternative; especially for the use case of viewDefinition.json.

Answer 2

Hello Alexander Clouter

You are correct in your understanding shared below.

CreateUiDefinition does not provide a way to automatically restrict the built‑in Region picker to only locations where Azure Functions Flex Consumption is available. The Location control can only be constrained by:

resourceTypes – which filters regions based on resource provider presence, and
allowedValues – which is a static list you must maintain.

Flex Consumption availability is a plan / SKU‑level capability, not a distinct ARM resource type. Because of that, using Microsoft.Web/serverfarms will always return a superset of regions, including ones where Flex Consumption is not supported.

There is currently no finer‑grained resource type that maps specifically to Flex Consumption, so this behavior is expected.

About Microsoft.Solutions.ArmApiControl your follow‑up understanding is also correct.

Microsoft.Solutions.ArmApiControl can only call Azure Resource Manager (ARM) endpoints under management.azure.com. It cannot:

Call Azure CLI commands
Call arbitrary HTTPS or custom REST endpoints
Invoke Azure Functions, Logic Apps, or external services

Historically, some solutions exposed custom data to the UI through Custom Resource Providers, but these are now deprecated and are no longer a viable option for Managed Application UI scenarios such as viewDefinition.json.

As a result, unless Flex Consumption availability is exposed directly through an ARM‑accessible API, there is no supported way to dynamically retrieve a live list of Flex‑supported regions at UI render time.

Given the current platform capabilities, the practical patterns are:

Keep the built‑in Location picker scoped broadly (for all required resource types)
Use informational messaging (for example, an InfoBox) to clearly state that Flex Consumption is only available in selected regions
Enforce Flex Consumption region correctness at deployment time in the ARM/Bicep template (fail fast with a clear validation error if an unsupported region is selected)

This approach aligns with supported CreateUiDefinition behavior and avoids reliance on deprecated or unsupported extensibility mechanisms.

Hope it helps your concern. If you have any other queries, please let me know.

Thanks,

Suchitra.

Share via

Flex Consumption in a Managed Application

1 additional answer

Your answer