capabilities.work

Lock Down a Namespace Network

A 2-step recipe with Azure Event Hubs. We can help you get access.

Recipe · 2 steps

Lock Down a Namespace Network

with Azure Event Hubs · IT Infrastructure Management

Apply a default-deny network rule set to a namespace and verify it.

  1. Apply a network rule set with a Deny default action that allows only the supplied trusted IP mask.
  2. Read the network rule set back and assert the default action is Deny so the lockdown is verified.
What you'll need to have ready
  • subscriptionId: Azure subscription identifier that scopes the resource.
  • resourceGroupName: Name of the resource group that contains the namespace.
  • namespaceName: The existing Event Hubs namespace name.
  • allowedIpMask: The IP mask (CIDR) permitted to reach the namespace (e.g. 203.0.113.0/24).
  • trustedServiceAccessEnabled: Whether trusted Azure services may bypass the deny rule.
  • apiVersion: Client API version for the management plane.
For your developer

Arazzo workflow microsoft-azure-event-hubs:lock-down-namespace-network, 2 operations: Namespaces_CreateOrUpdateNetworkRuleSet → Namespaces_GetNetworkRuleSet. Specs on APIs.io.

More recipes with Azure Event Hubs

Microsoft Azure Event Hubs Configure Geo-Disaster Recovery PairingMicrosoft Azure Event Hubs Configure Event Hub Capture to Blob StorageMicrosoft Azure Event Hubs Create an Event Hub with a Consumer GroupMicrosoft Azure Event Hubs Provision an Authorization Rule and Retrieve KeysMicrosoft Azure Event Hubs Provision a Namespace with an Event HubMicrosoft Azure Event Hubs Register a Schema Registry GroupMicrosoft Azure Event Hubs Rotate Namespace Keys