Merge pull request #299666 from hrazi/patch-7

Update network-security-perimeter.md

Author: prmerger-automator[bot]

articles/communication-services/quickstarts/network-security-perimeter.md

@@ -65,7 +65,7 @@ Provide the same network security perimeter name used in **Step 3**.
 
 `az network perimeter profile create --name <network-perimeter-profile-name> --resource-group <resource-group-name> --perimeter-name <network-security-perimeter-name>`
 
-### Step 5: Create an inbound access rule with a public IP address [YC2.1] [YC2.2] prefix for the profile created with the following command
+### Step 5: Create an inbound access rule with a public IP address prefix for the profile created with the following command
 
 `az network perimeter profile access-rule create --name <access-rule-name> --profile-name <network-perimeter-profile-name> --perimeter-name <network-security-perimeter-name> --resource-group <resource-group-name> --address-prefixes "[192.0.2.0/24]"`
 
@@ -90,7 +90,7 @@ Provide the same network security perimeter name used in **Step 3**.
    `az network perimeter association create --name <network-perimeter-association-name>  --perimeter-name <network-security-perimeter-name> --resource-group <network-perimeter-resource-group>  --access-mode Enforced --private-link-resource "{id:<ACSArmId>}" --profile "{id:<networkSecurityPerimeterProfileId>}"`
 
 
-### Step 7: Verify the allowlisted IP addresses can send email with NSP enabled [YC3.1] [YC3.2] [NM3.3]
+### Step 7: Verify the allowlisted IP addresses can send email with NSP enabled 
 
 Make sure that the Azure Communication Services resource is connected to a verified email domain. For more information, see [Connect a verified email domain](./email/connect-email-communication-resource.md).