Microsoft Marketplace deployment
From the marketplace listing to your live integration workspace, follow these eleven steps to find, deploy, and open iQBus for the first time. The installation is automatic and takes less than 30 minutes end to end.
Get it on Microsoft Marketplace iQBus marketplace.microsoft.com/en-us/product/cerebrumcity.iqbus Open listingLog in to the Azure Portal at portal.azure.com. In the search bar at the top center of the screen, type Marketplace and select the Marketplace service from the results, it is represented by a cloud shopping bag icon.
Once inside the Marketplace, type iQBus in the search bar and select the iQBus listing from the results. Searching by name takes you straight to the product, and the card at the top of this page opens the same listing directly.
On the listing's Overview page, choose the Subscription you want to install into and select the appropriate Plan. Then click Create to open the deployment wizard.
The wizard opens on the Basics tab. There are five fields, in three groups. Everything on this tab is fixed once the deployment starts, so read it before you click through.
| Field | What to enter |
|---|---|
| Subscription | The Azure subscription that will own and be billed for the deployment. Only subscriptions you can deploy into are listed. |
| Resource group | The resource group that will hold the managed application object. Use Create new and give it a name you will recognise, this is the first place you will look for your installation later. |
| Deployment region | The Azure region the iQBus infrastructure is provisioned into. Pick the region closest to the systems iQBus will integrate with, or the one your data residency policy requires. |
| Application Name | The name of the managed application itself, and the name shown in the resource group. Lower case, no spaces. |
| Managed Resource Group | The second resource group, created by Azure to hold every resource that powers iQBus. It is pre-filled from the Application Name and you can edit it. This group is managed by the application, you have limited access to what is inside it. |
Once the five fields are filled, click Next to move on to the AI Settings tab.
The AI Settings tab asks two questions. The first decides where the AI Accelerator gets its model from. The second decides which Azure region that model is deployed into, which is a separate choice because not every Azure region offers every AI model deployment.
| Option | In one line |
|---|---|
| Private AI | The model is deployed into your own Azure subscription, so nothing leaves your network and the model capacity lands on your Azure bill. Needs Foundry quota in place beforehand. |
| Managed AI | No AI infrastructure is provisioned. iQBus calls the AI Accelerator hosted by Cerebrum City, capped per installation. For subscriptions that cannot provision model capacity of their own. |
| No AI | Nothing is provisioned and the AI Accelerator is unavailable in this installation. Suits production environments where no development work is done. |
The full comparison, including quotas, limits, billing and data boundaries, is in AI deployment options.
The AI services region is asked separately from the Deployment region on the Basics tab, and it does not have to match it. Not every Azure region hosts every AI model deployment, so if the region you deployed into cannot serve the model, you pick a region that can, and the rest of your infrastructure stays where you put it.
Click Next to continue to Networking.
On the Networking tab, select a VNet address range for the private virtual network iQBus uses internally. Choose a preset that does not overlap with any existing VNet you plan to peer with.
Once your selection is made, click Next. Azure validates the configuration before presenting the review screen.
The Review + create tab has two parts. At the top is the Co-Admin Access Permission agreement, which you must accept before the Create button becomes available. Below it is a read-only summary of everything you set on the first three tabs, together with the pricing for the plan you selected.
When everything reads correctly, tick the agreement and click Create. Azure begins deploying the iQBus infrastructure into your subscription.
After clicking Create, Azure immediately opens the Deployment overview screen. You will see the status Deployment is in progress while Azure provisions all the infrastructure components that power iQBus.
When the deployment finishes, the status changes to Your deployment is complete. At this point your iQBus infrastructure is live and ready.
Click Go to resource to navigate directly to your deployment, this takes you straight to the resource group where your managed application is listed. Alternatively, you can locate it at any time by navigating to the Resource group name you defined in Step 2.
Infrastructure is deployed. Continue with the steps below to locate your application URL and access your iQBus integration workspace for the first time.
Open the resource group you named in Step 2. Inside it you will find a single resource of type Managed application, this is the top-level object representing your iQBus installation.
Click on the Managed application resource. On its Overview page, look to the upper-right of the Essentials section for a field called Managed resource group. This is the second resource group, the one that holds all of the application's infrastructure. Click the link to open it.
Inside the managed resource group you will see all the Azure resources that power iQBus, including databases, a service bus namespace, storage, a function app, and more. Look for an App Service resource whose name contains the word front. This is the web application you will use to configure and manage your integrations day to day.
On the Web App's Overview page, look to the upper-right of the Essentials section for the field labelled Default domain. This is the permanent URL for your iQBus management console, the address you and your team will use every day to access your integration workspace.
You're all set
iQBus is deployed and ready for configuration. If you run into any issues our support team is happy to help.