Skip to main content

Coins Analytics on Azure - Licensed Components and Provisioning

J
Written by Jen Johnson
Updated over 2 weeks ago

Introduction

This topic describes the licensed components and provisioning requirements for Coins Analytics on Azure.

The detail in subsequent sections, outlines what Microsoft and Coins components are required to provision for the data replication using Power BI and/or another tool for reporting data.

The ‘Coins Analytics on Azure SQL Server Deployment Guide’, describes what is recommended for clients to provision on Azure for data replication.

Fundamentally, the following is required:

  1. BLOB Storage service

  2. Virtual SQL Server(s) - shared virtual SQL server or separate server

  3. SQL Database(s) – the number dependent on client environments as each Coins environment requires a SQL DB.

  4. Power BI Pro license or alternative tool for reporting data.

  5. Licenses to Initialize Data Extracts and Analytics

PowerBI Embedded Capacity

Clients requiring PowerBI embedding would need additional PowerBI Pro licenses and the Azure AD Application.

  • At least 3 Power BI Pro licenses

  • Provision Azure AD Embedding Application

The following details on how they will be utilized:

  • 1 to an Admin user

  • 1 to an API service user (for embedding)

  • 1 for a user to be able to author and publish reports and dashboards.  

Additional Pro licenses can be purchased if more users (developer/publisher) require publishing reports.

The client will need to provision PowerBI embedded capacity, as is outlined on ‘Coins PowerBI Embedded Deployment Guide’.

Additionally, the client will need to provision an Application in their Azure Active Directory - this has no cost.  The Application enables Coins OA to authorize PowerBI visualizations to be embedded.

Once the above is established, we provision and configure the Coins Data Gateway. This resides in the Access Coins tenant and forms part of our delivery to clients, together with configuring the connections from the OA environment to the Coins Data Gateway, SQL DB and BLOB Storage.  

Note: No application data is replicated to Azure SQL at this stage.

Components

Summary list of components required for standard data replication/embedded PowerBI.

Components - Provisioning List

Component Premise

Name

Description / Purpose

Quantity

Source

Comments

Data Replication

BLOB Storage Service

File storage for bulk inserts of data into SQL

1

Microsoft

Azure Blob Storage service for storing sizeable amounts of data

Data Replication

Virtual SQL Server

SQL Server on Azure to contain the SQL databases

1

Microsoft

Data Replication

SQL Database

To replicate the data from Coins

1 per Coins environment to be replicated

Microsoft

Can be on a shared or separate virtual SQL servers

Data Replication

Coins Data Gateway

Data gateway web application and key vault

1

Coins

Provides communication and gateway from Coins OA to Azure SQL

Embedded Power BI

Power BI Pro licenses

Pro User licenses to administer and publish reporting contents via Power BI

1 for an Admin user

1 to an API Service user

1 for each Publishing user

Microsoft

More can be purchased if more report/developer users are required.

Embedded Power BI

Power BI Embedded Capacity

Power BI Embedded is a capacity which is used to embed Power BI Reports to Coins or any Application(s)

1

Microsoft

Embedded Power BI

Provision App in Azure AD

Provides authorisation for Coins OA to embed PowerBI content

1

Microsoft

Data Extraction licenses

X-EXINITROWS

X-EXINITSIZE

X-EXDATAROWS

X-EXDATASIZE

Licenses for Data Extracts and Analytics, allows for the initialization of the amount of data

4

Coins

The licenses have default values as standard.

The two primary elements of the licenses:

INIT is for initialization based on the size of the Database.

DATA is for monthly updates.

Note: The license come with default values (as blank), however the values can be updated and set as required (when there are more tables have been configured or the scale of records has increased.

Did this answer your question?