Microsoft.EventHub namespaces 2014-09-01
Bicep resource definition
The namespaces resource type can be deployed with operations that target:
- Resource groups - See resource group deployment commands
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.EventHub/namespaces resource, add the following Bicep to your template.
resource symbolicname 'Microsoft.EventHub/namespaces@2014-09-01' = {
location: 'string'
name: 'string'
properties: {
createdAt: 'string'
enabled: bool
provisioningState: 'string'
serviceBusEndpoint: 'string'
status: 'string'
updatedAt: 'string'
}
sku: {
capacity: int
name: 'string'
tier: 'string'
}
tags: {
{customized property}: 'string'
}
}
Property values
Microsoft.EventHub/namespaces
| Name | Description | Value |
|---|---|---|
| location | Namespace location. | string (required) |
| name | The resource name | string Constraints: Min length = 6 Max length = 6 (required) |
| properties | Properties of the Namespace supplied for create or update Namespace operation | NamespaceProperties |
| sku | SKU parameters supplied to the create Namespace operation | Sku |
| tags | Resource tags | Dictionary of tag names and values. See Tags in templates |
NamespaceCreateOrUpdateParametersTags
| Name | Description | Value |
|---|
NamespaceProperties
| Name | Description | Value |
|---|---|---|
| createdAt | The time the Namespace was created. | string |
| enabled | Specifies whether this instance is enabled. | bool |
| provisioningState | Provisioning state of the Namespace. | string |
| serviceBusEndpoint | Endpoint you can use to perform Service Bus operations. | string |
| status | State of the Namespace. | 'Activating' 'Active' 'Created' 'Creating' 'Disabled' 'Disabling' 'Enabling' 'Failed' 'Removed' 'Removing' 'SoftDeleted' 'SoftDeleting' 'Unknown' |
| updatedAt | The time the Namespace was updated. | string |
Sku
| Name | Description | Value |
|---|---|---|
| capacity | The Event Hubs throughput units. | int |
| name | Name of this SKU. | 'Basic' 'Standard' |
| tier | The billing tier of this particular SKU. | 'Basic' 'Premium' 'Standard' (required) |
Quickstart samples
The following quickstart samples deploy this resource type.
| Bicep File | Description |
|---|---|
| Azure Digital Twins with Time Data History Connection | This template creates an Azure Digital Twins instance configured with a time series data history connection. In order to create a connection, other resources must be created such as an Event Hubs namespace, an event hub, Azure Data Explorer cluster, and a database. Data is sent to an event hub which eventually forwards the data to the Azure Data Explorer cluster. Data is stored in a database table in the cluster |
| Azure Function App with Event Hub and Managed Identity | his template provisions an Azure Function app on a Linux Consumption plan, along with an Event Hub, Azure Storage, and Application Insights. The function app is able to use managed identity to connect to the Event Hub and Storage account |
| Create an event hub | This template enables you to deploy a EventHubs namespace with an event hub. |
| Create an EventHubs namespace, Event Hub, & consumer group | This template enables you to deploy an Event Hubs Standard namespace, an Event Hub, and a consumer group. |
| Creates Event Hub cluster & namesapce in cluster | This template enables you to create EventHubs Cluster and a namespace in cluster |
| Creates Eventhub cluster, namesapce & eventhub | This template enables you to create EventHubs Cluster, namespace and eventhub in cluster |
| Deploy Azure Data Explorer db with Event Grid connection | Deploy Azure Data Explorer db with Event Grid connection. |
| Deploy Azure Data Explorer db with Event Hub connection | Deploy Azure Data Explorer db with Event Hub connection. |
| Deploy the MedTech service | The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. |
| Deploy the MedTech service including an Azure IoT Hub | The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. |
| Deploy the Sports Analytics on Azure Architecture | Creates an Azure storage account with ADLS Gen 2 enabled, an Azure Data Factory instance with linked services for the storage account (an the Azure SQL Database if deployed), and an Azure Databricks instance. The AAD identity for the user deploying the template and the managed identity for the ADF instance will be granted the Storage Blob Data Contributor role on the storage account. There are also options to deploy an Azure Key Vault instance, an Azure SQL Database, and an Azure Event Hub (for streaming use cases). When an Azure Key Vault is deployed, the data factory managed identity and the AAD identity for the user deploying the template will be granted the Key Vault Secrets User role. |
| FrontDoor CDN with WAF, Domains and Logs to EventHub | This template creates a new Azure FrontDoor cdn profile. Create WAF with custom and managed rules, cdn routes, origin and groups with their association with WAF and routes, configures custom domains, create event hub and diagnostic settings for sending CDN access logs using event hub. |
| Moesif API Analytics and Monetization | The template will log API calls from Azure API Management to Moesif API analytics and monetization platform |
ARM template resource definition
The namespaces resource type can be deployed with operations that target:
- Resource groups - See resource group deployment commands
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.EventHub/namespaces resource, add the following JSON to your template.
{
"type": "Microsoft.EventHub/namespaces",
"apiVersion": "2014-09-01",
"name": "string",
"location": "string",
"properties": {
"createdAt": "string",
"enabled": "bool",
"provisioningState": "string",
"serviceBusEndpoint": "string",
"status": "string",
"updatedAt": "string"
},
"sku": {
"capacity": "int",
"name": "string",
"tier": "string"
},
"tags": {
"{customized property}": "string"
}
}
Property values
Microsoft.EventHub/namespaces
| Name | Description | Value |
|---|---|---|
| apiVersion | The api version | '2014-09-01' |
| location | Namespace location. | string (required) |
| name | The resource name | string Constraints: Min length = 6 Max length = 6 (required) |
| properties | Properties of the Namespace supplied for create or update Namespace operation | NamespaceProperties |
| sku | SKU parameters supplied to the create Namespace operation | Sku |
| tags | Resource tags | Dictionary of tag names and values. See Tags in templates |
| type | The resource type | 'Microsoft.EventHub/namespaces' |
NamespaceCreateOrUpdateParametersTags
| Name | Description | Value |
|---|
NamespaceProperties
| Name | Description | Value |
|---|---|---|
| createdAt | The time the Namespace was created. | string |
| enabled | Specifies whether this instance is enabled. | bool |
| provisioningState | Provisioning state of the Namespace. | string |
| serviceBusEndpoint | Endpoint you can use to perform Service Bus operations. | string |
| status | State of the Namespace. | 'Activating' 'Active' 'Created' 'Creating' 'Disabled' 'Disabling' 'Enabling' 'Failed' 'Removed' 'Removing' 'SoftDeleted' 'SoftDeleting' 'Unknown' |
| updatedAt | The time the Namespace was updated. | string |
Sku
| Name | Description | Value |
|---|---|---|
| capacity | The Event Hubs throughput units. | int |
| name | Name of this SKU. | 'Basic' 'Standard' |
| tier | The billing tier of this particular SKU. | 'Basic' 'Premium' 'Standard' (required) |
Quickstart templates
The following quickstart templates deploy this resource type.
| Template | Description |
|---|---|
Azure Digital Twins with Time Data History Connection |
This template creates an Azure Digital Twins instance configured with a time series data history connection. In order to create a connection, other resources must be created such as an Event Hubs namespace, an event hub, Azure Data Explorer cluster, and a database. Data is sent to an event hub which eventually forwards the data to the Azure Data Explorer cluster. Data is stored in a database table in the cluster |
| Azure Function App with Event Hub and Managed Identity |
his template provisions an Azure Function app on a Linux Consumption plan, along with an Event Hub, Azure Storage, and Application Insights. The function app is able to use managed identity to connect to the Event Hub and Storage account |
| Azure SQL Server with Auditing written to Event Hub |
This template allows you to deploy an Azure SQL server with Auditing enabled to write audit logs to Event Hub |
| Connect to a Event Hubs namespace via private endpoint |
This sample shows how to use configure a virtual network and private DNS zone to access a Event Hubs namespace via a private endpoint. |
| Create a Event Hubs namespace Virtual Network rule |
This template enables you to deploy a Event Hubs Standard namespace with Virtual Network rule |
| Create a Eventhub namespace and geo-recovery configuration |
This template enables you to deploy a Service Bus namespace with a Basic/Standard SKU. |
| Create a Eventhub namespace IP Filter rule |
This template enables you to deploy a Service Bus Premium namespace with IP Filter rule |
| Create an Environment with an Event Hub Event Source |
This template enables you to deploy a Time Series Insights environment that is configured to consume events from an Event Hub. |
| Create an event hub |
This template enables you to deploy a EventHubs namespace with an event hub. |
| Create an EventHubs namespace and enable auto-inflate |
This template enables you to deploy an Event Hubs Standard namespace, an Event Hub, and a consumer group.This template also turns on the auto-inflate feature on your namespace. |
| Create an EventHubs namespace, Event Hub, & consumer group |
This template enables you to deploy an Event Hubs Standard namespace, an Event Hub, and a consumer group. |
| Create Event Grid custom topic and event hub handler |
Creates an Azure Event Grid custom topic and event hub to handle the events. |
| Create EventHubs authorizationRules |
This template enables you to deploy a EventHubs Standard namespace, an Event Hub, a consumer group and authorizationRules |
| Create EventHubs with Capture enabled |
This template enables you to deploy a EventHubs namespace with an event hub and enabling Capture on it |
| Create EventHubs with Capture enabled (ADLS) |
This template enables you to deploy a EventHubs namespace with an event hub and enabling Capture on it |
| Create SQL MI with configured sending of logs and metrics |
This template allows you to deploy SQL MI and additional resources used for storing logs and metrics (diagnostic workspace, storage account, event hub). |
| Creates Event Hub cluster & namesapce in cluster |
This template enables you to create EventHubs Cluster and a namespace in cluster |
| Creates Eventhub cluster, namesapce & eventhub |
This template enables you to create EventHubs Cluster, namespace and eventhub in cluster |
| Deploy Azure Data Explorer db with Event Grid connection |
Deploy Azure Data Explorer db with Event Grid connection. |
| Deploy Azure Data Explorer db with Event Hub connection |
Deploy Azure Data Explorer db with Event Hub connection. |
| Deploy the MedTech service |
The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. |
| Deploy the MedTech service including an Azure IoT Hub |
The MedTech service is one of the Azure Health Data Services designed to ingest device data from multiple devices, transform the device data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service. |
| Deploy the Sports Analytics on Azure Architecture |
Creates an Azure storage account with ADLS Gen 2 enabled, an Azure Data Factory instance with linked services for the storage account (an the Azure SQL Database if deployed), and an Azure Databricks instance. The AAD identity for the user deploying the template and the managed identity for the ADF instance will be granted the Storage Blob Data Contributor role on the storage account. There are also options to deploy an Azure Key Vault instance, an Azure SQL Database, and an Azure Event Hub (for streaming use cases). When an Azure Key Vault is deployed, the data factory managed identity and the AAD identity for the user deploying the template will be granted the Key Vault Secrets User role. |
| FrontDoor CDN with WAF, Domains and Logs to EventHub |
This template creates a new Azure FrontDoor cdn profile. Create WAF with custom and managed rules, cdn routes, origin and groups with their association with WAF and routes, configures custom domains, create event hub and diagnostic settings for sending CDN access logs using event hub. |
| Moesif API Analytics and Monetization |
The template will log API calls from Azure API Management to Moesif API analytics and monetization platform |
| PubNub Realtime Gateway for Azure Event Hubs |
The PubNub Realtime Gateway for Azure provides a realtime data stream bridge between the PubNub Data Stream Network and Azure Event Hubs. -- consider it a bi-directional bridge between PubNub and Azure! |
Terraform (AzAPI provider) resource definition
The namespaces resource type can be deployed with operations that target:
- Resource groups
For a list of changed properties in each API version, see change log.
Resource format
To create a Microsoft.EventHub/namespaces resource, add the following Terraform to your template.
resource "azapi_resource" "symbolicname" {
type = "Microsoft.EventHub/namespaces@2014-09-01"
name = "string"
location = "string"
sku = {
capacity = int
name = "string"
tier = "string"
}
tags = {
{customized property} = "string"
}
body = jsonencode({
properties = {
createdAt = "string"
enabled = bool
provisioningState = "string"
serviceBusEndpoint = "string"
status = "string"
updatedAt = "string"
}
})
}
Property values
Microsoft.EventHub/namespaces
| Name | Description | Value |
|---|---|---|
| location | Namespace location. | string (required) |
| name | The resource name | string Constraints: Min length = 6 Max length = 6 (required) |
| properties | Properties of the Namespace supplied for create or update Namespace operation | NamespaceProperties |
| sku | SKU parameters supplied to the create Namespace operation | Sku |
| tags | Resource tags | Dictionary of tag names and values. |
| type | The resource type | "Microsoft.EventHub/namespaces@2014-09-01" |
NamespaceCreateOrUpdateParametersTags
| Name | Description | Value |
|---|
NamespaceProperties
| Name | Description | Value |
|---|---|---|
| createdAt | The time the Namespace was created. | string |
| enabled | Specifies whether this instance is enabled. | bool |
| provisioningState | Provisioning state of the Namespace. | string |
| serviceBusEndpoint | Endpoint you can use to perform Service Bus operations. | string |
| status | State of the Namespace. | 'Activating' 'Active' 'Created' 'Creating' 'Disabled' 'Disabling' 'Enabling' 'Failed' 'Removed' 'Removing' 'SoftDeleted' 'SoftDeleting' 'Unknown' |
| updatedAt | The time the Namespace was updated. | string |
Sku
| Name | Description | Value |
|---|---|---|
| capacity | The Event Hubs throughput units. | int |
| name | Name of this SKU. | 'Basic' 'Standard' |
| tier | The billing tier of this particular SKU. | 'Basic' 'Premium' 'Standard' (required) |