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

The subnet resource has a `RouteTable` property: <https://www.pulumi.com/registry/packages/azure-native/api-docs/network/subnet/#routetable_csharp>

I also believe that the RouteTable resource’s `Routes` property Id subproperty  can be set with the subnet ID to create this association.
<https://www.pulumi.com/registry/packages/azure-native/api-docs/network/routetable/#routes_csharp>

That's right, but I need to connect an existing Subnet and an existing RouteTable.

```            var subnetArgs = new SubnetArgs
            {
                Name = subnet.GetProperty("name").ToString(),
                AddressPrefix = subnet.GetProperty("addressPrefix").ToString(),
                RouteTable = new RouteTableArgs {
                    Id = "RouteTable.Id here"
                }
            };```

Are either of these  resources managed by pulumi?

So, you should be able to update the pulumi code for one to reference the other.  Or, am I missing some nuance here?

It seems like the RouteTable Id can only be set on

What about adding the subnet Id to the routetable  routes declaration?

<https://www.pulumi.com/registry/packages/azure-native/api-docs/network/routetable/#inputs>

I don't see how a Subnet can be assigned to a RouteTable.

From googling around how to do this with ARM templates (the Azure-Native provider is based on the ARM API), I believe that assigning the subnet ID in the `routes` property (<https://www.pulumi.com/registry/packages/azure-native/api-docs/network/routetable/#route>) will associate it.

That associates a Route (NextHop, addressPrefix ...) not a subnet

<https://learn.microsoft.com/en-us/powershell/module/az.network/set-azvirtualnetworksubnetconfig?view=azps-9.3.0>
With PowerShell RouteTable(s) can be assigned to Subnets

You can use the classic azure provider alongside the azure-native provider and should be able to use <https://www.pulumi.com/registry/packages/azure/api-docs/network/subnetroutetableassociation/> to create the association.

I was thinking that when I started this thread.  I was hoping to do it with Azure-Native.   Thank you Mitch.

I get that and was of the same mind. But since Azure ARM doesn’t appear to allow modifying the subnet resource after creation, it looks like the classic provider resource needs to be used.
That said, I would suggest opening an issue against azure-native requesting an analogous association resource. 

Open a request with Microsoft or Pulumi ?