Installation guidedeployment ama marketplace azure
- Find CluedIn
- Complete the Basics tab
- Complete the Initial Setup tab
- Review the AKS Setup tab
- Review the Service Setup tab
- Review the Advanced Configuration tab
- Complete the Review + Create tab
- Next steps
In this article, you will learn how to install CluedIn from the Azure Marketplace.
Important! Make sure that you have completed all of the actions described in Pre-installation checklist.
Start the installation process by finding CluedIn in the Azure Marketplace.
To find CluedIn
- In the Azure Marketplace, search for CluedIn.
- From the results, select CluedIn Master Data Management.
- On the CluedIn Master Data Management page, select Get It Now.
- In the dialog box that appears, in Software plan, select CluedIn Platform.
- Review your contact information, and then select Continue.
On the Basics tab, you can select the Azure resource group where CluedIn will be installed and provide license details.
To complete the Basics tab
- Fill in the Project details section:
- In Subscription, select your Azure subscription where you want to install CluedIn.
- In Resource group, create a new resource group. You can select the existing resource group, but it must be empty. If the resource group that you select contains other Azure resources, you will get an error.
- Fill in the Instance details section:
- In Region, specify the Azure region where different resources will be created. The region will probably match your resource group location.
- Depending on whether you have the license key, do one of the following:
- If you have the license key, in CluedIn License Version, select Existing License Key. Then, in CluedIn License Key, paste the license key.
- If you don’t have the license key, in CluedIn License Version, select a plan that was chosen by your company (Essential, Professional, or Elite).
- Make sure that the Installation Name field is filled out correctly. This field is usually filled out by default, but you can make changes if needed.
- Make sure that the Managed Application Details section is filled out correctly. This section is usually filled out by default, but you can make changes if needed.
On the CluedIn - Initial Setup tab, you can create the organization and the administrator account for your CluedIn instance, specify SMTP details, and enable SSO.
To complete the Initial Setup tab
- Specify organization details:
- Specify Organization Name. The organization name will be used as part of the URL. Ideally, it should be one word with no dashes or hyphens.
- Specify Administrator Email Address.
- Specify CluedIn Administrator Password, and then Confirm password. The password must be more than 12 characters long.
- Specify SMTP details:
- Specify SMTP - Server.
- In SMTP - Port, specify SSL port.
- Add details about the email that will be used for sending invitations to other users to join CluedIn. Important! You can change SMTP details after installation by submitting a ticket to CluedIn support.
- If needed, enable SSO access for CluedIn, and then specify SSO details. Important! You can enable SSO access for CluedIn after installation. This is often the preferable option because some mapping of Azure AD groups to product groups is required. For more information, see Configure SSO.
On the CluedIn - AKS Setup tab, you can customize the number of nodes that you want to use in your CluedIn instance, and you can also define autoscaling parameters.
Important! In most cases, you do not need to adjust anything on this tab unless advised to do so by CluedIn support.
The AKS Setup tab contains the following settings:
- General node pool that runs the main application services. General Node Pool VM Count contains a minimum number of VMs to ensure that all resources can be scheduled. If you need to increase the VM count, consult with CluedIn support.
- Data node pool that runs any database and data collection services. Data Node Pool VM Count contains a minimum number of VMs to ensure that all resources can be scheduled. If you need to increase the VM count, consult with CluedIn support.
- Processing node pool that runs any CluedIn processing services. Processing Node Size depends on the license type you have selected on the Basics tab. If you have entered a license key on the Basics tab, then the machine type will be hidden because it is encoded into the license.
You can enable auto-scaling for the processing node pool. It means that when CPU pressure (high workload) builds up in this node pool, AKS can start up new nodes to compensate for the increase in load. When the load returns to normal, the extra nodes will be shut down. However, be aware that there are additional infrastructure and licensing costs associated with scaling up. For more information about auto-scaling, contact CluedIn support.
Important! You can enable auto-scaling after installation.
On the CluedIn - Service Setup tab, you can review major services that make up CluedIn’s data layer. By default, CluedIn uses the resources provisioned inside the cluster and the Azure managed (encrypted) disks to store any data created.
Important! The default configuration is sufficient, so you don’t need to adjust anything on this tab. You can change service details after installation by submitting a ticket to CluedIn support.
The installer can use the existing services or provision new services as part of the setup. However, the provisioning of new services may incur additional infrastructure charges from Azure.
By default, CluedIn creates an instance of SQL Server inside the cluster, backed with 1TB disks.
The installer can provision an Azure SQL instance (Elastic Pool) to install all the databases. The Azure SQL resource will be created inside the managed resource group.
By default, CluedIn creates a scalable instance of Redis inside the cluster.
CluedIn can be configured to use the existing Redis instance if provided with connection details. The installer can also provide a new Azure Redis instance that will be created inside the managed resource group.
By default, CluedIn creates a scalable instance of ElasticSearch inside the cluster, backed with 1TB disks.
CluedIn can be configured to use the existing ElasticSearch instance if provided with connection details.
By default, CluedIn doesn’t create an Event Hub instance.
The installer can provide a new Azure Event Hub instance that will be created inside the managed resource group.
On the CluedIn - Advanced Configuration tab, you can find technical and debugging switches that are used by CluedIn support. Most of the options on this tab should not be adjusted. Any misconfiguration or changes to these options can cause the installation to fail.
Important! You can make changes on this tab only with the advice of CluedIn support.
You may be required to change the address CIDR ranges of the vNet that is created. For example, you can do it if you are connecting to a vNet that has similar internal IP addresses and you want to avoid a clash.
You can enable the Advanced Networking section to make changes to the vNet defaults.
Important! The installer cannot verify these IP ranges and their validity before the installation starts, so double-check all settings before proceeding.
On the Review + Create tab, review and accept the terms and conditions. To start the deployment process in your own cloud environment, select Create.
You have CluedIn running in your own cloud environment.
Customize CluedIn to meet your organization’s needs as described in our Post-installation guide.