Merge pull request #211679 from lakmeedee/patch-586

Update co-location.md

Author: prmerger-automator[bot]

articles/virtual-machines/co-location.md

@@ -50,6 +50,9 @@ When specifying `intent`, you can also add the optional `zone` parameter to spec
 
 Proximity Placement Group creation or update will succeed only when at least one data center supports all the VM Sizes specified in the intent. Otherwise, the creation or update will fail with "OverconstrainedAllocationRequest", indicating that the combination of VM Sizes can't be supported within a proximity placement group. The **intent does not provide any capacity reservation or guarantee**. The VM Sizes and zone  given in `intent` are used to select an appropriate data center, reducing the chances of failure if the desired VM size isn't available in a data center. Allocation failures can still occur if there is no more capacity for a VM size at the time of deployment. 
 
+> [!NOTE]
+> To use intent for your proximity placement groups, ensure that the API version is 2021-11-01 or higher
+
 ### Best Practices while using intent
 
 - Provide an availability zone for your proximity placement group only when you provide an intent. Providing an availability zone without an intent will result in an error when creating the proximity placement group.