In NDFC, VRF and Network attachments can happen independently, i.e. create VRFs and attach them to leaf switches then create Networks and attach them to leaf switches. The workflow can also be combined as you are doing in this lab where the VRF is created, then the Networks associated to the VRF, and finally the Networks are deployed, inturn, deploying the VRF. All of this adhering to Cisco best practices.
You have staged your overlay tenant VRF and staged two host Networks associated to your overlay tenant VRF in the previous sections. It is now time to attach these constructs to the leaf switches that require it. This requirement in reality would come based on a design of how hosts, such as ESXi are connected to your leaf switches. There are two standalone Linux instances connected to your Site1-L1 and Site1-L2 switches on Ethernet1/5. This is the interface you used policy to configure as an access interface leaving the access VLAN undefined. An additional part of the attachment workflow is selecting an interface(s) for the networks to be deployed, whether that is an access or trunk interface. For this lab, you will select your Ethernet1/5 interface between your two leaf switches for each Network you previously created.
In the Edit Network Attachment - Site1 wizard:
Confirm both BlueNet1 and BlueNet2 networks display as deployed:
Revisit the main Overview dashboard to see the VRF and Network definition health displayed:
Continue to the next section to verify your Site1 Greenfield "Data Center VXLAN EVPN" fabric.