Merge pull request #109946 from asudbring/natpatch

Edited example

Author: PRMerger9

articles/virtual-network/nat-gateway-resource.md

@@ -63,19 +63,18 @@ The following example is a snippet from an Azure Resource Manager template.  Thi
 - **natgatewayname** -  Name of the NAT gateway.
 - **location** - Azure region where resource is located.
 - **publicipname** - Name of the outbound public IP associated with the NAT gateway.
-- **publicipprefixname** - Name of the outbound public IP prefix associated with the NAT gateway.
 - **vnetname** - Name of the virtual network.
 - **subnetname** - Name of the subnet associated with the NAT gateway.
 
 The total number of IP addresses provided by all IP address and prefix resources can't exceed 16 IP addresses total. Any number of IP addresses between 1 and 16 is allowed.
 
-:::code language="json" source="~/quickstart-templates/101-nat-gateway-1-vm/azuredeploy.json" range="256-281":::
+:::code language="json" source="~/quickstart-templates/101-nat-gateway-vnet/azuredeploy.json" range="81-96":::
 
 When the NAT gateway resource has been created, it can be used on one or more subnets of a virtual network. Specify which subnets use this NAT gateway resource. A NAT gateway isn't able to span more than one virtual network. It isn't required to assign the same NAT gateway to all subnets of a virtual network. Individual subnets can be configured with different NAT gateway resources.
 
 Scenarios that don't use availability zones will be regional (no zone specified). If you're using availability zones, you can specify a zone to isolate NAT to a specific zone. Zone-redundancy isn't supported. Review NAT [availability zones](#availability-zones).
 
-:::code language="json" source="~/quickstart-templates/101-nat-gateway-1-vm/azuredeploy.json" range="225-255" highlight="239-251":::
+:::code language="json" source="~/quickstart-templates/101-nat-gateway-vnet/azuredeploy.json" range="1-146" highlight="81-96":::
 
 NAT gateways are defined with a property on a subnet within a virtual network. Flows created by virtual machines on subnet **subnetname** of virtual network **vnetname** will use the NAT gateway. All outbound connectivity will use the IP addresses associated with **natgatewayname** as the source IP address.