Get Started with Confluent Cloud on the Azure Marketplace with Commitments¶
This topic shows you how to get up and running using Confluent Cloud on the Azure Marketplace with a usage-based billing commitment. With a commitment, you sign up for a minimum spend amount and get a discount on your committed usage of Confluent Cloud.
To pay for Confluent Cloud, Confluent Consumption Units (CCUs) are enabled in the cloud Marketplace. Pricing in Marketplace is the same as direct purchase pricing. For more information, see Confluent Cloud Consumption Metrics for Marketplace Deployments.
An Azure Marketplace account. You can use Confluent Cloud and get billed directly through Azure.
You cannot sign up for Confluent Cloud through a Microsoft Solutions Provider.
Confluent Cloud currently requires your email address to be unique across all organizations. If your Azure AD email address has already been used for signup on Confluent Cloud, you must first remove yourself as a user from the Confluent Cloud org where you signed up previously, so your Azure AD email can be used for single sign on (SSO). One option is to invite an alternate email that you own as a user to the old organization, and then delete your “Azure AD related email user” from the old organization. This way, you can sign up using SSO. Alternatively, another user in the old organization can delete your Azure AD user id. To find the email address associated with your your Azure AD account, follow these steps:
- Go to the Azure Active Directory portal.
- Click the More Info link in the Tenant Information section.
- Click Profile under Manage in the left navigation menu. Your Azure AD email address appears in the Identity section under User Principle Name.
To purchase, you must be logged in to the Azure Marketplace and you must be the owner of the subscription you are using to sign up (the one linked to the billing account).
Your Azure policy should allow you to provision resources in the region where you choose to set up the Confluent resource.
Click the Apache Kafka® on Confluent Cloud™ for Azure tile.
Select the “Commit” plan and click Set up + subscribe. You might have multiple plans available.
Choose the correct subscription and Create new for Resource group.
In the Instance details section, enter your desired Region for the resource, and choose the commit private Plan created for your tenant.
The specified region is used to store metadata for this resource group, and does not need to be the same region where your Confluent Cloud clusters are located. You are not charged for this usage.
In the Confluent organization details section, you can either create a new Confluent organization (account) or link an existing Confluent organization.
To link an existing Confluent organization:
Click Link to an existing organization. A dialog appears that asks you to confirm the updated billing details. Once confirmed, the linked organization name will appear in Azure next to the Confluent Organization Name field.
When you link to an existing organization, the existing organization should not be associated with an active entitlement. If an active entitlement exists at the time of linking, then the exisiting entitlement will be automatically be cancelled.
(Optional) Click the Tags tab to create tags for your project.
Click Review and create.
After validation occurs, you are ready to create the resource. Review the terms of your plan and click Create. Your deployment will start. This could take up to a minute.
After your resources are deployed, you will receive a confirmation message. Click Go to resource to view the deployed resource on the Azure portal.
Click the Confluent SSO URL Manage on Confluent Cloud to sign on to Confluent Cloud using your Azure AD account. You may be asked to choose an account for SSO. Grant permission to the Confluent app on the Consent screen by clicking Accept. You will be signed in. From here, you can manage your resources on Confluent Cloud.
You can invite additional users to your Confluent Cloud organization by clicking the Administration menu (☰) at the top right corner of the Confluent Cloud Console and selecting Users from the menu that appears. After you reach the Users main page, click + Add user and provide an the email address for the user you want to invite. This can be an Azure AD user, or a non-SSO user with an email id and password.
Azure AD is the only supported SSO identity provider when you are subscribed to Confluent Cloud through the Azure Marketplace.
Cannot view private offer¶
- You access the marketplace via portal.azure.com, but cannot view the private offer after clicking View Private Offers.
- Confirm with your Confluent Account Executive (AE) that a private offer has been created for your organization. Also, confirm that you shared the correct tenant ID with your Confluent AE. If you still can not view the private offer, please reach out to your Confluent AE.
Email already exists¶
- When you try to sign up on Confluent Cloud, you receive a conflict error.
- When you click the Click here for details link within the warning message, “Email already exists” is shown as the reason for signup failure.
- See the Prerequisites section. If your Azure AD email is already in use for another organization on Confluent Cloud, you need to remove yourself as a user from that organization before you can register for Confluent Cloud through the Azure marketplace.
SSO Login Failure - Invalid Username¶
- The user is authenticated successfully and is registered with Confluent Cloud but does not belong to the Azure AD Tenant that was used during Confluent Cloud Signup.
- Ask your Confluent Cloud administrator to invite you to the Confluent Cloud organization.
SSO Login Failure - Tenant Mismatch¶
- SSO Login to Confluent Cloud shows an error after login.
- Ask your Confluent Cloud administrator to add your user to the Azure AD tenant that was used during Confluent Cloud organization signup.
Not able to launch Azure resource in a region¶
- You see a message on the Azure portal UI stating that you can not launch resources in a certain Azure region.
- Verify that your policies are set to allow you to provision resources in your chosen region on the Azure portal.
Deployment failed - could not create Marketplace resource¶
- You see a message on the Azure portal UI stating that the deployment operation failed.
Make sure your subscription has Marketplace purchase permission, meaning your account has subscription owner or contributor permissions. In addition, verify you have an Azure Standard or above support plan associated with your subscription. A Developer support subscription is not sufficient.