No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

This page and none of it's links mention this UI being a front door feature from what i can tell

If you have it configured in the portal, could you export this resource as ARM template and see what’s there?

Either that, or you can also just perform that az command with --debug, that way you can see the actual JSON payload, and it’s basically the exact same property you would configure with azure-native.

Using `az` with `--debug` is a great way to also migrate your scripts to pulumi management with azure-native, without the extra overhead that an ARM templates provides, specially with arm template functions that don’t have an equal in pulumi.

```    "resources": [
        {
            "type": "Microsoft.Cdn/profiles/endpoints/customdomains",
            "apiVersion": "2020-09-01",
            "name": "[concat(parameters('profiles_test_profile_name'), '/test-endpoint/cdn-my-domain-com')]",
            "dependsOn": [
                "[resourceId('Microsoft.Cdn/profiles/endpoints', parameters('profiles_test_profile_name'), 'test-endpoint')]"
            ],
            "properties": {
                "hostName": "<http://cdn.my-domain.com|cdn.my-domain.com>"
            }
        },```

nothing about mintls or managed cert, same from json view in the UI

it's like the bottom half of the UI is being offloaded to front door or something and it's not documented at all

front doors is empty, but front doors standard/premium lists the profile/endpoint/custom domain, so there's maybe some weird overlap going on here?

We're going to just roll with Standard_AzureFrontDoor profile for now and use the AFDCustomDomain