An Azure Event Hubs import topic lets you continuously ingest data
from [Azure Event Hubs](https://azure.microsoft.com/en-us/products/event-hubs) as an external source and into
Pub/Sub. Then you can stream the data into any of the destinations
that Pub/Sub supports.

> [!NOTE]
> **Note:** Only [*Standard* and *Premium* tier Azure Event Hubs](https://learn.microsoft.com/en-us/azure/event-hubs/compare-tiers#features) can be imported into Pub/Sub.

This document shows you how to create and manage Azure Event Hubs import
topics. To create a standard topic, see [Create a standard
topic](https://docs.cloud.google.com/pubsub/docs/create-topic).

For more information about import topics, see [About import topics](https://docs.cloud.google.com/pubsub/docs/publish-message-overview.md.txt#import-topic-overview).

## Before you begin

- Know more about the [Pub/Sub publish
  process](https://docs.cloud.google.com/pubsub/docs/publish-message-overview).

- Configure the [required roles and permissions to manage Azure Event Hubs
  import topics](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic#roles-permissions) including the following:

  - [Add the Pub/Sub publisher role to the
    Pub/Sub service account](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic#add-publisher-role)

  - [Add the Pub/Sub service agent role to the Pub/Sub service account](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#add-service-agent-role), if not already granted.

  - [Add the service account user role to the service account](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#add-service-account-role)

- Set up [workload identity federation](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#federated-identity) so that
  Google Cloud can access the external streaming service.

### Required roles and permissions


To get the permissions that
you need to create and manage Azure Event Hubs import topics,

ask your administrator to grant you the
[Pub/Sub Editor](https://docs.cloud.google.com/iam/docs/roles-permissions/pubsub.md.txt#pubsub.editor) (`roles/pubsub.editor`) IAM role on your topic or project.


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).


This predefined role contains

the permissions required to create and manage Azure Event Hubs import topics. To see the exact permissions that are
required, expand the **Required permissions** section:


#### Required permissions

The following permissions are required to create and manage Azure Event Hubs import topics:

- Create an import topic: pubsub.topics.create
- Delete an import topic: pubsub.topics.delete
- Get an import topic: pubsub.topics.get
- List an import topic: pubsub.topics.list
- Publish to an import topic: pubsub.topics.publish and pubsub.serviceAgent
- Update an import topic: pubsub.topics.update
- Get the IAM policy for an import topic: pubsub.topics.getIamPolicy
- Configure the [IAM policy](https://docs.cloud.google.com/iam/docs/reference/rest/v1/Policy.md.txt) for an import topic: `pubsub.topics.setIamPolicy`


You might also be able to get
these permissions
with [custom roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt) or
other [predefined roles](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#predefined).

You can configure access control at the project level and the
individual resource level.

## Set up federated identity to access Azure Event Hubs

Workload Identity Federation lets Google Cloud services access workloads
running outside of Google Cloud. With identity federation, you don't need
to maintain or pass credentials to Google Cloud to access your resources
in other clouds. Instead, you can use the identities of the workloads themselves
to authenticate to Google Cloud and access resources.

### Create a service account in Google Cloud

This is an optional step. If you already have a service account, you can use
it in this procedure instead of creating a new service account.
If you are using an existing service account, go to
[Record the service account unique ID](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#record-service-account) for the
next step.

For Azure Event Hubs import topics, Pub/Sub uses the
service account as the identity to access resources from Azure.

For more information about creating a service account, including prerequisites,
required roles and permissions, and naming guidelines, see
[Create service accounts](https://docs.cloud.google.com/iam/docs/service-accounts-create.md.txt). After you create
a service account, you might need to wait for 60 seconds or more before you
use the service account. This behavior occurs because read operations are
eventually consistent; it can take time for the new service account to
become visible.

### Record the service account unique ID

You need a service account unique ID to set up App registration in Azure.

1. In the Google Cloud console, go to the **Service account** details page.

   [Go to service account](https://console.cloud.google.com/iam-admin/serviceaccounts)
2. Click the service account that you just created or the one that you are
   planning to use.

3. From the **Service account details** page, record the Unique ID number.

   You need the ID as part of the workflow to set up [App registration in Azure](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#create_id).

### Add the service account token creator role to the Pub/Sub service account

> [!NOTE]
> **Note:** Pub/Sub creates and maintains a service account for each project. The service account has the following format: `service-{PROJECT_NUMBER}@gcp-sa-pubsub.iam.gserviceaccount.com`. Perform this procedure only if the Pub/Sub service account does not have the Pub/Sub Service Agent role (`roles/pubsub.serviceAgent`).

The **Service account token creator role** (`roles/iam.serviceAccountTokenCreator`)
lets principals [create short-lived credentials](https://docs.cloud.google.com/iam/docs/create-short-lived-credentials-direct.md.txt)
for a service account. These tokens or credentials are used to impersonate
the service account.

For more information about service account impersonation, see
[Service account impersonation](https://docs.cloud.google.com/iam/docs/service-account-impersonation.md.txt).

You can also add the **Pub/Sub publisher role** (`roles/pubsub.publisher`)
during this procedure. For more information about the role and why you are adding it,
see [Add the Pub/Sub publisher role to the Pub/Sub service account](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#add-publisher-role).

1. In the Google Cloud console, go to the **IAM** page.

   [Go to IAM](https://console.cloud.google.com/iam-admin/iam)
2. Click the **Include Google-provided role grants** checkbox.

3. Look for the service account that has the format `service-{PROJECT_NUMBER}@gcp-sa-pubsub.iam.gserviceaccount.com`.

4. For this service account, click the **Edit Principal** button.

5. If required, click **Add another role**.

6. Search and click the **Service account token creator role** (`roles/iam.serviceAccountTokenCreator`).

7. Click **Save**.

### Create an App registration with identity federation

To ingest data from Azure Event Hubs, register an application with the
Microsoft Identity platform and enable identity federation for
your service account. This allows your service account to authenticate to
Azure.

For more information on registering an application with the
Microsoft Identity platform, see the [Azure app
registration
quickstart](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate).

1. Sign in to the [Azure portal](https://portal.azure.com/) and open
   the **Microsoft Entra ID** page.

2. In the navigation pane, click **Manage** \> **App registrations**.

3. Click **New registration**.

4. Name the application and set **Supported account types** to
   anything other than **Personal Microsoft accounts only**.

5. To register the application, click **Register**.

6. Open the application and click **Manage** \> **Certificates \& Secrets**.

7. Click **Add credential**.

8. To configure a federated credential, click **Other issuer**.

9. For the **Issuer** field, enter `https://accounts.google.com`.

10. For the **Value** field, enter the unique ID of your Pub/Sub
    service account.

    You can find this ID in [Record the service account unique ID](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#record-service-account).
11. Name the federated identity and then click **Add**.

### Grant role assignments to the registered App

To enable Pub/Sub to read from your Azure event
hub, grant the necessary roles to your registered app.

1. Sign in to the [Azure portal](https://portal.azure.com/) and open your Event Hubs namespace.

   To open a namespace, enter **Event Hubs** in the search, and then click
   one of the namespaces.
2. In the sidebar, click **Access control (IAM)**.

3. Click **Add** \> **Add role assignment**.

4. Select the **Azure Event Hubs Data Receiver** role, then click **Next**.

   This grants the Pub/Sub service account read access to your
   Azure event hub.
5. Click **+Select members**, then search for your registered app.

6. Type the registered app name into the search field.

7. Click the name of your app and then click **Select**.

8. Click **Review + Assign**.

9. Repeat steps 3--6 and add the **Azure Event Hubs Data Sender** role.

   This role grants the Google Cloud Service Account permission to
   fetch metadata from your Azure event hub.

For more information on assigning Azure roles, visit the
[Assign Azure roles](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal) page.

## Add the Pub/Sub publisher role to the Pub/Sub principal

To enable publishing, you must assign a publisher role to the
Pub/Sub service account so that Pub/Sub is able to
publish to the Azure Event Hubs import topic.

## Add the Pub/Sub service agent role to the Pub/Sub service account

> [!NOTE]
> **Note:** The Pub/Sub service agent role is granted by default for all projects after April 9, 2021. If your project has been created after this date and the Pub/Sub service agent role has not been removed, your Pub/Sub service account will already have this role.

To allow Pub/Sub to use your import topic project's publish quota, the Pub/Sub service agent requires the [`serviceusage.services.use`](https://docs.cloud.google.com/iam/docs/roles-permissions/serviceusage.md.txt#serviceusage.services.use) permission on your import topic's project.

To provide this permission, we recommend you add the Pub/Sub service agent role to the Pub/Sub service account.

If the Pub/Sub service account does not have the Pub/Sub service agent role, it can be granted as follows:

1. In the Google Cloud console, go to the **IAM** page.

   [Go to IAM](https://console.cloud.google.com/iam-admin/iam)
2. Click the **Include Google-provided role grants** checkbox.

3. Look for the service account that has the format
   `service-{PROJECT_NUMBER}@gcp-sa-pubsub.iam.gserviceaccount.com`.

4. For this service account, click the **Edit principal** button.

5. If required, click **Add another role**.

6. Search and click the **Pub/Sub Service Agent role** (`roles/pubsub.serviceAgent`).

7. Click **Save**.

### Enable publishing from all topics

Use this method if you have not created any Azure Event Hubs import
topics.

1. In the Google Cloud console, go to the **IAM** page.

   [Go to IAM](https://console.cloud.google.com/iam-admin/iam)
2. Click the **Include Google-provided role grants** checkbox.

3. Look for the service account that has the format
   `service-{PROJECT_NUMBER}@gcp-sa-pubsub.iam.gserviceaccount.com`.

4. For this service account, click the **Edit principal** button.

5. If required, click **Add another role**.

6. Search and click the **Pub/Sub publisher role** (`roles/pubsub.publisher`).

7. Click **Save**.

### Enable publishing from a single topic

Use this method only if the Azure Event Hubs import topic already exists.

1.


   In the Google Cloud console, activate Cloud Shell.

   [Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)


   At the bottom of the Google Cloud console, a
   [Cloud Shell](https://docs.cloud.google.com/shell/docs/how-cloud-shell-works.md.txt)
   session starts and displays a command-line prompt. Cloud Shell is a shell environment
   with the Google Cloud CLI
   already installed and with values already set for
   your current project. It can take a few seconds for the session to initialize.

   <br />

2. Run the [`gcloud pubsub topics add-iam-policy-binding`](https://docs.cloud.google.com/sdk/gcloud/reference/pubsub/topics/add-iam-policy-binding) command:

   ```bash
   gcloud pubsub topics add-iam-policy-binding TOPIC_ID \
      --member="serviceAccount:service-PROJECT_NUMBER@gcp-sa-pubsub.iam.gserviceaccount.com" \
      --role="roles/pubsub.publisher"
   ```

   Replace the following:
   - <var translate="no">`TOPIC_ID`</var>: the topic ID of the Azure Event Hubs import topic.

   - <var translate="no">`PROJECT_NUMBER`</var>: the project number. To view the project
     number, see [Identifying projects](https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects.md.txt#identifying_projects).

## Add the service account user role to the service account

The **Service Account User role** (`roles/iam.serviceAccountUser`) includes the
permission `iam.serviceAccounts.actAs` that lets a principal attach a service
account to the Azure Event Hubs import topic's ingestion settings and
use that service account for federated identity.

1. In the Google Cloud console, go to the **IAM** page.

   [Go to IAM](https://console.cloud.google.com/iam-admin/iam)
2. For the principal that's issuing the create or update topic calls, click the
   **Edit principal** button.

3. If required, click **Add another role**.

4. Search and click the **Service account user role**
   (`roles/iam.serviceAccountUser`).

5. Click **Save**.

## Use Azure Event Hubs import topics

You can create a new import topic or edit an existing topic.

### Considerations

> [!CAUTION]
> **Caution:** If you already have data in Azure Event Hubs, first [create a
> standard topic and a default subscription](https://docs.cloud.google.com/pubsub/docs/create-topic#create_a_topic_2) without enabling the ingestion settings. Then, [convert the topic to an import topic](https://docs.cloud.google.com/pubsub/docs/change-topic-type.md.txt#convert-standard-to-import). This method ensures that all messages are received by the subscription.

- Creating the topic and subscription separately, even if done in rapid
  succession, can lead to data loss. There's a short window where the topic
  exists without a subscription. If any data is sent to the topic during this
  time, it is lost. By creating the topic first, creating the subscription,
  and then converting the topic to an import topic, you guarantee that no
  messages are missed during the import process.

- If you need to re-create the Azure event hub of an existing import topic with
  the same name, you can't *just* delete the Azure event hub and re-create it.
  This action can invalidate Pub/Sub's offset management, which can lead to
  data loss. To mitigate this, follow these steps:

  - Delete the Pub/Sub import topic
  - Delete the Azure event hub
  - Create the Azure event hub
  - Create the Pub/Sub import topic
- Data from an Azure event hub is always read from the [earliest
  offset](https://kafka.apache.org/documentation/#consumerconfigs_auto.offset.reset).

### Create Azure Event Hubs import topics

To know more about properties associated with a topic, see [Properties of a
topic](https://docs.cloud.google.com/pubsub/docs/create-topic#properties_of_a_topic).

Ensure that you have completed the following procedures:

- [Set up federated identity to access Azure Event Hubs](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#federated-identity)

- [Add the Pub/Sub publisher role to the Pub/Sub
  service account](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic#add-publisher-role)

- [Add the service account user role to the IAM principal](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#add-service-account-role)

To create an Azure Event Hubs import topic, follow these steps:

### Console

1. In the Google Cloud console, go to the **Topics** page.

   [Go to Topics](https://console.cloud.google.com/cloudpubsub/topic/list)
2. Click **Create topic**.

3. In the **Topic ID** field, enter an ID for your Azure Event Hubs
   import topic. For more information about naming topics, see the [naming
   guidelines](https://docs.cloud.google.com/pubsub/docs/pubsub-basics#resource_names).

4. Select **Add a default subscription**.

5. Select **Enable ingestion**.

6. For ingestion source, select **Azure Event Hubs**.

7. Enter the following details:

   - **Resource group**: the name of the Azure Resource Group that contains the Azure Event Hubs namespace that you are planning to ingest into Pub/Sub.
   - **Event Hub namespace**: the name of the Azure Event Hubs namespace that contains the Azure event hub that you are planning to ingest into Pub/Sub.
   - **Event Hub**: the name of the Azure event hub that you are planning to ingest into Pub/Sub.
   - **Client ID** : the application (client) ID of the registered App in Azure that contains the federated identity of the Google Cloud Service Account. This value should be a UUID. For more information, visit the [Azure App Registration page](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate).
   - **Tenant ID** : the directory (tenant) ID of the tenant that owns the Azure event hub that you are planning to ingest into Pub/Sub. This value should be a UUID. To find your tenant ID, visit the [Azure Get subscription and tenant IDs page](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - **Subscription ID** : the subscription ID of the subscription that owns the Azure Event Hubs resource group. This value should be a UUID. To find your subscription ID, visit the [Azure Get subscription and tenant IDs page](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - **Service account:** the service account that you created in [Create a service account in Google Cloud](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#create-service-account).
8. Leave the remaining fields with the default values.

9. Click **Create topic**.

### gcloud

1. In the Google Cloud console, activate Cloud Shell.

   [Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)


   At the bottom of the Google Cloud console, a
   [Cloud Shell](https://docs.cloud.google.com/shell/docs/how-cloud-shell-works.md.txt)
   session starts and displays a command-line prompt. Cloud Shell is a shell environment
   with the Google Cloud CLI
   already installed and with values already set for
   your current project. It can take a few seconds for the session to initialize.
2. Run the [`gcloud pubsub topics create`](https://docs.cloud.google.com/sdk/gcloud/reference/pubsub/topics/create) command:

   ```bash
     gcloud pubsub topics create TOPIC_ID \
         --azure-event-hubs-ingestion-resource-group RESOURCE_GROUP \
         --azure-event-hubs-ingestion-namespace NAMESPACE \
         --azure-event-hubs-ingestion-event-hub EVENT_HUB \
         --azure-event-hubs-ingestion-client-id CLIENT_ID \
         --azure-event-hubs-ingestion-tenant-id TENANT_ID \
         --azure-event-hubs-ingestion-subscription-id SUBSCRIPTION_ID \
         --azure-event-hubs-ingestion-service-account SERVICE_ACCOUNT
   ```

   Replace the following:
   - `TOPIC_ID`: the name or ID of your Pub/Sub topic.
   - `RESOURCE_GROUP`: the name of the Azure Event Hubs resource group that contains the Azure Event Hubs namespace that you are planning to ingest into Pub/Sub.
   - `NAMESPACE`: the name of the Azure Event Hubs namespace that contains the Azure event hub that you are planning to ingest into Pub/Sub.
   - `EVENT_HUB`: the name of the Azure event hub that you are planning to ingest into Pub/Sub.
   - `CLIENT_ID`: the application (client) ID of the registered App in Azure that contains the federated identity of the Google Cloud Service Account. This value should be a UUID. For more information, visit the [Azure App Registration page](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate).
   - `TENANT_ID`: the directory (tenant) ID of the tenant that owns the Azure event hub that you are planning to ingest into Pub/Sub. This value should be a UUID. To find your tenant ID, visit the [Azure Get subscription and tenant IDs page](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - `SUBSCRIPTION_ID`: the subscription ID of the subscription that owns the Azure event hub that you are planning to ingest into Pub/Sub. This value should be a UUID. To find your subscription ID, visit the [Azure Get subscription
     and tenant IDs page](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - `SERVICE_ACCOUNT`: the service account that you created in [Create a service account in Google Cloud](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#create-service-account)

### C++


Before trying this sample, follow the C++ setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub C++ API reference documentation](https://googleapis.dev/cpp/google-cloud-pubsub/latest/).

```c++
namespace pubsub = ::google::cloud::pubsub;
namespace pubsub_admin = ::google::cloud::pubsub_admin;
[](pubsub_admin::TopicAdminClient client, std::string project_id,
   std::string topic_id, std::string const& resource_group,
   std::string const& event_hubs_namespace, std::string const& event_hub,
   std::string const& client_id, std::string const& tenant_id,
   std::string const& subscription_id,
   std::string const& gcp_service_account) {
  google::pubsub::v1::Topic request;
  request.set_name(
      pubsub::Topic(std::move(project_id), std::move(topic_id)).FullName());
  auto* azure_event_hubs = request.mutable_ingestion_data_source_settings()
                               ->mutable_azure_event_hubs();
  azure_event_hubs->set_resource_group(resource_group);
  azure_event_hubs->set_namespace_(event_hubs_namespace);
  azure_event_hubs->set_event_hub(event_hub);
  azure_event_hubs->set_client_id(client_id);
  azure_event_hubs->set_tenant_id(tenant_id);
  azure_event_hubs->set_subscription_id(subscription_id);
  azure_event_hubs->set_gcp_service_account(gcp_service_account);

  auto topic = client.CreateTopic(request);
  // Note that kAlreadyExists is a possible error when the library retries.
  if (topic.status().code() == google::cloud::StatusCode::kAlreadyExists) {
    std::cout << "The topic already exists\n";
    return;
  }
  if (!topic) throw std::move(topic).status();

  std::cout << "The topic was successfully created: " << topic->DebugString()
            << "\n";
}
```

<br />

### Go


The following sample uses the major version of the Go Pub/Sub client library (v2). If you are still using the v1 library, see
[the migration guide to v2](https://github.com/googleapis/google-cloud-go/blob/main/pubsub/MIGRATING.md).
To see a list of v1 code samples, see [the deprecated code samples](https://docs.cloud.google.com/pubsub/docs/samples.md.txt?language=golang&text=deprecated).

Before trying this sample, follow the Go setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub Go API reference documentation](https://pkg.go.dev/cloud.google.com/go/pubsub/v2).

```go
import (
	"context"
	"fmt"
	"io"

	"cloud.google.com/go/pubsub/v2"
	"cloud.google.com/go/pubsub/v2/apiv1/pubsubpb"
)

func createTopicWithAzureEventHubsIngestion(w io.Writer, projectID, topicID, resourceGroup, namespace, eventHub, clientID, tenantID, subID, gcpSA string) error {
	// projectID := "my-project-id"
	// topicID := "my-topic"

	// // Azure Event Hubs ingestion settings.
	// resourceGroup := "resource-group"
	// namespace := "namespace"
	// eventHub := "event-hub"
	// clientID := "client-id"
	// tenantID := "tenant-id"
	// subID := "subscription-id"
	// gcpSA := "gcp-service-account"

	ctx := context.Background()
	client, err := pubsub.NewClient(ctx, projectID)
	if err != nil {
		return fmt.Errorf("pubsub.NewClient: %w", err)
	}
	defer client.Close()

	topicpb := &pubsubpb.Topic{
		Name: fmt.Sprintf("projects/%s/topics/%s", projectID, topicID),
		IngestionDataSourceSettings: &pubsubpb.IngestionDataSourceSettings{
			Source: &pubsubpb.IngestionDataSourceSettings_AzureEventHubs_{
				AzureEventHubs: &pubsubpb.IngestionDataSourceSettings_AzureEventHubs{
					ResourceGroup:     resourceGroup,
					Namespace:         namespace,
					EventHub:          eventHub,
					ClientId:          clientID,
					TenantId:          tenantID,
					SubscriptionId:    subID,
					GcpServiceAccount: gcpSA,
				},
			},
		},
	}
	topic, err := client.TopicAdminClient.CreateTopic(ctx, topicpb)
	if err != nil {
		return fmt.Errorf("CreateTopic: %w", err)
	}
	fmt.Fprintf(w, "Created topic with Azure Event Hubs ingestion: %v\n", topic)
	return nil
}
```

<br />

### Java


Before trying this sample, follow the Java setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub Java API reference documentation](https://cloud.google.com/java/docs/reference/google-cloud-pubsub/latest/overview).

```java

import com.google.cloud.pubsub.v1.TopicAdminClient;
import com.google.pubsub.v1.IngestionDataSourceSettings;
import com.google.pubsub.v1.Topic;
import com.google.pubsub.v1.TopicName;
import java.io.IOException;

public class CreateTopicWithAzureEventHubsIngestionExample {
  public static void main(String... args) throws Exception {
    // TODO(developer): Replace these variables before running the sample.
    String projectId = "your-project-id";
    String topicId = "your-topic-id";
    // Azure Event Hubs ingestion settings.
    String resourceGroup = "resource-group";
    String namespace = "namespace";
    String eventHub = "event-hub";
    String clientId = "client-id";
    String tenantId = "tenant-id";
    String subscriptionId = "subscription-id";
    String gcpServiceAccount = "gcp-service-account";

    createTopicWithAzureEventHubsIngestionExample(
        projectId,
        topicId,
        resourceGroup,
        namespace,
        eventHub,
        clientId,
        tenantId,
        subscriptionId,
        gcpServiceAccount);
  }

  public static void createTopicWithAzureEventHubsIngestionExample(
      String projectId,
      String topicId,
      String resourceGroup,
      String namespace,
      String eventHub,
      String clientId,
      String tenantId,
      String subscriptionId,
      String gcpServiceAccount)
      throws IOException {
    try (TopicAdminClient topicAdminClient = TopicAdminClient.create()) {
      TopicName topicName = TopicName.of(projectId, topicId);

      IngestionDataSourceSettings.AzureEventHubs azureEventHubs =
          IngestionDataSourceSettings.AzureEventHubs.newBuilder()
              .setResourceGroup(resourceGroup)
              .setNamespace(namespace)
              .setEventHub(eventHub)
              .setClientId(clientId)
              .setTenantId(tenantId)
              .setSubscriptionId(subscriptionId)
              .setGcpServiceAccount(gcpServiceAccount)
              .build();
      IngestionDataSourceSettings ingestionDataSourceSettings =
          IngestionDataSourceSettings.newBuilder().setAzureEventHubs(azureEventHubs).build();

      Topic topic =
          topicAdminClient.createTopic(
              Topic.newBuilder()
                  .setName(topicName.toString())
                  .setIngestionDataSourceSettings(ingestionDataSourceSettings)
                  .build());

      System.out.println(
          "Created topic with Azure Event Hubs ingestion settings: " + topic.getAllFields());
    }
  }
}
```

<br />

### Node.js


Before trying this sample, follow the Node.js setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub Node.js API reference documentation](https://googleapis.dev/nodejs/pubsub/latest).

    /**
     * TODO(developer): Uncomment these variables before running the sample.
     */
    // const topicNameOrId = 'YOUR_TOPIC_NAME_OR_ID';
    // const resourceGroup = 'YOUR_RESOURCE_GROUP';
    // const namespace = 'YOUR_NAMESPACE';
    // const eventHub = 'YOUR_EVENT_HUB';
    // const clientId = 'YOUR_CLIENT_ID';
    // const tenantId = 'YOUR_TENANT_ID';
    // const subscriptionId = 'YOUR_SUBSCRIPTION_ID';
    // const gcpServiceAccount = 'ingestion-account@...';

    // Imports the Google Cloud client library
    const {PubSub} = require('@google-cloud/pubsub');

    // Creates a client; cache this for further use
    const pubSubClient = new PubSub();

    async function createTopicWithAzureEventHubsIngestion(
      topicNameOrId,
      resourceGroup,
      namespace,
      eventHub,
      clientId,
      tenantId,
      subscriptionId,
      gcpServiceAccount,
    ) {
      // Creates a new topic with Azure Event Hubs ingestion.
      await pubSubClient.createTopic({
        name: topicNameOrId,
        ingestionDataSourceSettings: {
          azureEventHubs: {
            resourceGroup,
            namespace,
            eventHub,
            clientId,
            tenantId,
            subscriptionId,
            gcpServiceAccount,
          },
        },
      });
      console.log(
        `Topic ${topicNameOrId} created with Azure Event Hubs ingestion.`,
      );
    }

<br />

### Node.ts


Before trying this sample, follow the Node.js setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub Node.js API reference documentation](https://googleapis.dev/nodejs/pubsub/latest).

    /**
     * TODO(developer): Uncomment these variables before running the sample.
     */
    // const topicNameOrId = 'YOUR_TOPIC_NAME_OR_ID';
    // const resourceGroup = 'YOUR_RESOURCE_GROUP';
    // const namespace = 'YOUR_NAMESPACE';
    // const eventHub = 'YOUR_EVENT_HUB';
    // const clientId = 'YOUR_CLIENT_ID';
    // const tenantId = 'YOUR_TENANT_ID';
    // const subscriptionId = 'YOUR_SUBSCRIPTION_ID';
    // const gcpServiceAccount = 'ingestion-account@...';

    // Imports the Google Cloud client library
    import {PubSub} from '@google-cloud/pubsub';

    // Creates a client; cache this for further use
    const pubSubClient = new PubSub();

    async function createTopicWithAzureEventHubsIngestion(
      topicNameOrId: string,
      resourceGroup: string,
      namespace: string,
      eventHub: string,
      clientId: string,
      tenantId: string,
      subscriptionId: string,
      gcpServiceAccount: string,
    ) {
      // Creates a new topic with Azure Event Hubs ingestion.
      await pubSubClient.createTopic({
        name: topicNameOrId,
        ingestionDataSourceSettings: {
          azureEventHubs: {
            resourceGroup,
            namespace,
            eventHub,
            clientId,
            tenantId,
            subscriptionId,
            gcpServiceAccount,
          },
        },
      });
      console.log(
        `Topic ${topicNameOrId} created with Azure Event Hubs ingestion.`,
      );
    }

<br />

### Python


Before trying this sample, follow the Python setup instructions in
[Quickstart: Using Client Libraries](https://docs.cloud.google.com/pubsub/docs/create-topic-client-libraries).
For more information, see the [Pub/Sub Python API reference documentation](https://docs.cloud.google.com/python/docs/reference/pubsub/latest.md.txt).

```python
from google.cloud import pubsub_v1
from google.pubsub_v1.types import Topic
from google.pubsub_v1.types import IngestionDataSourceSettings

# TODO(developer)
# project_id = "your-project-id"
# topic_id = "your-topic-id"
# resource_group = "your-resource-group"
# namespace = "your-namespace"
# event_hub = "your-event-hub"
# client_id = "your-client-id"
# tenant_id = "your-tenant-id"
# subscription_id = "your-subscription-id"
# gcp_service_account = "your-gcp-service-account"

publisher = pubsub_v1.PublisherClient()
topic_path = publisher.topic_path(project_id, topic_id)

request = Topic(
    name=topic_path,
    ingestion_data_source_settings=IngestionDataSourceSettings(
        azure_event_hubs=IngestionDataSourceSettings.AzureEventHubs(
            resource_group=resource_group,
            namespace=namespace,
            event_hub=event_hub,
            client_id=client_id,
            tenant_id=tenant_id,
            subscription_id=subscription_id,
            gcp_service_account=gcp_service_account,
        )
    ),
)

topic = publisher.create_topic(request=request)

print(f"Created topic: {topic.name} with Azure Event Hubs Ingestion Settings")
```

<br />

If you run into issues, see [Troubleshooting an Azure Event Hubs
import topic](https://docs.cloud.google.com/pubsub/docs/azure-event-hub-import-topic-troubleshooting).

### Edit Azure Event Hubs import topics

To edit the ingestion data source settings of an Azure Event Hubs
import topic, follow these steps:

### Console

1. In the Google Cloud console, go to the **Topics** page.

   [Go to Topics](https://console.cloud.google.com/cloudpubsub/topic/list)
2. Click the Azure Event Hubs import topic.

3. In the topic details page, click **Edit**.

4. Update the fields that you want to change.

5. Click **Update**.

### gcloud

1. In the Google Cloud console, activate Cloud Shell.

   [Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)


   At the bottom of the Google Cloud console, a
   [Cloud Shell](https://docs.cloud.google.com/shell/docs/how-cloud-shell-works.md.txt)
   session starts and displays a command-line prompt. Cloud Shell is a shell environment
   with the Google Cloud CLI
   already installed and with values already set for
   your current project. It can take a few seconds for the session to initialize.
2. Run the [`gcloud pubsub topics update`](https://docs.cloud.google.com/sdk/gcloud/reference/pubsub/topics/update) command with all the
   flags mentioned in the following sample:

   ```bash
   gcloud pubsub topics update TOPIC_ID \
       --azure-event-hubs-ingestion-resource-group RESOURCE_GROUP \
       --azure-event-hubs-ingestion-namespace NAMESPACE \
       --azure-event-hubs-ingestion-event-hub EVENT_HUB \
       --azure-event-hubs-ingestion-client-id CLIENT_ID \
       --azure-event-hubs-ingestion-tenant-id TENANT_ID \
       --azure-event-hubs-ingestion-subscription-id SUBSCRIPTION_ID \
       --azure-event-hubs-ingestion-service-account SERVICE_ACCOUNT
   ```

   Replace the following:
   - `TOPIC_ID`: the name or ID of your Pub/Sub topic.
   - `RESOURCE_GROUP`: the name of the Azure Event Hubs resource group that contains the Azure Event Hubs namespace that you are ingesting into Pub/Sub.
   - `NAMESPACE`: the name of the Azure Event Hubs namespace that contains the Azure event hub that you are ingesting into Pub/Sub.
   - `EVENT_HUB`: the name of the Azure event hub that you are ingesting into Pub/Sub.
   - `CLIENT_ID`: the application (client) ID of the registered App in Azure that contains the federated identity of the Google Cloud Service Account. This value should be a UUID. For more information, see [the Azure App Registration page](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app?tabs=certificate).
   - `TENANT_ID`: the directory (tenant) ID of the tenant that owns the Azure Event Hubs that you are ingesting into Pub/Sub. This value should be a UUID. To find your tenant ID, see [visit the Azure Get subscription and tenant IDs page](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - `SUBSCRIPTION_ID`: the subscription ID of the subscription that owns the Azure event hub that you are ingesting into Pub/Sub. This value should be a UUID. To find your subscription ID, see [Azure Get subscription and tenant IDs](https://learn.microsoft.com/en-us/azure/azure-portal/get-subscription-tenant-id).
   - `SERVICE_ACCOUNT`: the service account that you created in [Create a service account in Google Cloud](https://docs.cloud.google.com/pubsub/docs/create-azure-event-hub-import-topic.md.txt#create-service-account)

## Quotas and limits

The publisher throughput for import topics is bound by the publish quota
of the topic. For more information, see
[Pub/Sub quotas and limits](https://docs.cloud.google.com/pubsub/quotas.md.txt).

## What's next

- [Monitor an import topic](https://docs.cloud.google.com/pubsub/docs/monitor-topic.md.txt#metrics-monitor-topic).

- Choose the [type of subscription](https://docs.cloud.google.com/pubsub/docs/subscriber.md.txt) for your topic.

- Learn how to [publish a message to a topic](https://docs.cloud.google.com/pubsub/docs/publisher.md.txt).

- Create or modify a topic with [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud/reference/pubsub/topics),
  [REST APIs](https://docs.cloud.google.com/pubsub/docs/reference/rest/v1/projects.topics.md.txt), or [Client libraries](https://docs.cloud.google.com/pubsub/docs/reference/libraries.md.txt).

- [Troubleshoot an Azure Event Hubs import topic](https://docs.cloud.google.com/pubsub/docs/azure-event-hub-import-topic-troubleshooting.md.txt).