Event Grid Private Link GA

Author: spelluru

articles/event-grid/configure-firewall.md

@@ -254,7 +254,7 @@ Invoke-RestMethod -Method 'Get' `
     -Headers $Headers `
     | ConvertTo-Json -Depth 5
 
-# prepare the body for REST PUT method. Notice that it includes inbound IP rules now. This feature available in both basic and premium tiers.
+# prepare the body for REST PUT method. Notice that it includes inbound IP rules now. This feature is available in both basic and premium tiers.
 $body = @{"location"="<LOCATION>"; "sku"= @{"name"="basic"}; "properties"=@{"publicNetworkAccess"="enabled"; "inboundIpRules"=@(@{"ipmask"="<IP ADDR or CIDR MASK>";"action"="allow"}, @{"ipmask"="<IP ADDR or CIDR MASK>";"action"="allow"})}} | ConvertTo-Json -Depth 5
 
 # update the topic with inbound IP rules

articles/event-grid/configure-private-endpoints.md

@@ -15,9 +15,6 @@ You can use [private endpoints](../private-link/private-endpoint-overview.md) to
 
 This article describes how to configure private endpoints for topics or domains.
 
-> [!IMPORTANT]
-> Private endpoints feature is available for topics and domains only in premium tier. To upgrade from basic tier to premium tier, see the [Update pricing tier](update-tier.md) article. 
-
 ## Use Azure portal 
 This section shows you how to use the Azure portal to create a private endpoint for a topic or a domain.
 
@@ -201,7 +198,7 @@ Here's a sample script that creates the following Azure resources:
 - Resource group
 - Virtual network
 - Subnet in the virtual network
-- Azure Event Grid topic (premium tier)
+- Azure Event Grid topic
 - Private endpoint for the topic
 
 > [!NOTE]
@@ -250,8 +247,7 @@ az network vnet subnet update \
 az eventgrid topic create \
     --resource-group $resourceGroupName \
     --name $topicName \
-    --location $location \
-    --sku "Premium" 
+    --location $location
 
 # verify that the topic was created.
 az eventgrid topic show \
@@ -365,7 +361,7 @@ $virtualNetwork | Set-AzVirtualNetwork
 
 
 ```azurepowershell-interactive
-$body = @{"location"="<LOCATION>"; "sku"= @{"name"="premium"}; "properties"=@{"publicNetworkAccess"="disabled"}} | ConvertTo-Json
+$body = @{"location"="<LOCATION>"; "properties"=@{"publicNetworkAccess"="disabled"}} | ConvertTo-Json
 
 # create topic
 Invoke-RestMethod -Method 'Put'  `

articles/event-grid/network-security.md

@@ -88,11 +88,10 @@ The following table describes the various states of the private endpoint connect
 For publishing to be successful, the private endpoint connection state should be **approved**. If a connection is rejected, it can't be approved using the Azure portal. The only possibility is to delete the connection and create a new one instead.
 
 ## Pricing and quotas
-**Private endpoints** are only available with premium tier topics and domains. Event Grid allows up to 64 private endpoint connections to be created per topic or domain. To upgrade from basic tier to premium tier, see the [Update pricing tier](update-tier.md) article.
+**Private endpoints** is available in both basic and premium tiers of Event Grid. Event Grid allows up to 64 private endpoint connections to be created per topic or domain. 
 
 **IP Firewall** feature is available in both basic and premium tiers of Event Grid. We allow up to 16 IP Firewall rules to be created per topic or domain.
 
-
 ## Next steps
 You can configure IP firewall for your Event Grid resource to restrict access over the public internet from only a select set of IP Addresses or IP Address ranges. For step-by-step instructions, see [Configure IP firewall](configure-firewall.md).