Introduction
This document describes the Coins recommended deployment process for Microsoft Azure SQL Server for use with Coins Analytics on Azure. It has been updated to reflect current Azure portal navigation and Microsoft's recommended vCore-based purchasing model.
Prerequisites
Coins ERP+ server hosted in Coins Construction Cloud or on premise (including customers own cloud tenancy)
Customers own Microsoft Azure Tenant
Access rights to create new resources in an Azure Subscription
Coins JSON template for Coins Analytics on Azure.
Database Scaling
Coins suggests using the Azure SQL Database: size S3 or General-Purpose tier vCore for typical testing and reporting development, smaller or larger scale databases may be suitable depending on the customers expected load.
Note: The vCore model is Microsoft’s current recommended approach, offering greater flexibility and transparency over the older DTU-based tiers.
Microsoft is deprecating the older DTU-based Basic, Standard (S0–S12), and Premium tiers in favour of the vCore model. Existing DTU-based databases continue to work as Microsoft haven’t published an end date yet.
Recommended Starting Sizes (vCore)
Scenario | Recommended Tier |
Development/Testing | General Purpose, 2 vCores |
Standard Production | General Purpose, 4 vCores |
High-Load Production | General Purpose, 8+ vCores or Business Critical |
See the Microsoft pricing calculator for current costs:
Creating the Azure SQL Database
Create SQL Database
Log in to the Azure portal using an account with Owner rights to the applicable Azure Subscription.
Select Create a Resource, search for Template deployment (deploy using custom templates), and select it.
Click Create, then select Build your own template in the editor.
Click Load File and select the JSON template supplied by Coins. Click Save.
Complete the required parameters before clicking Review + Create. After validation, click Create.
Required Parameters
Parameter | Value/Guidance |
SQL Administrator Login | Coins standard is ‘sysadmin’. Use a strong password. Avoid characters: [] {}() , ; ? * ! @ |
Collation | SQL_Latin1_General_CP1_CI_AS (required for Coins compatibility) |
Server & Database Name | Must be unique and meet Azure naming conventions. Database name should reference the Coins environment. |
Compute Tier | See Database Scaling |
Max Size Bytes | 268435456000 |
Location | Must match the Azure location of the Coins Data Gateway for best performance. Your Coins project manager will confirm this. |
Note: Customers may prefer to provide an alternative account with reduced privileges for Coins access. This SQL user will need CONTROL permission granted.
Configure SQL Database Access (Firewall)
After creating the database, configure the SQL Server firewall to permit access from TRUSTED networks and Azure services only.
Portal Navigation (updated for 2025/2026):
Navigate to your logical SQL Server (not the database) in the Azure portal.
Under Security in the left menu, select Networking.
Set Public network access to Selected networks.
Enable the Allow Azure services and resources to access this server toggle — this is essential for Coins Analytics.
Add firewall rules for your trusted networks and the Access Group support ranges below.
Note: The older ‘Set server firewall’ toolbar button on the database Overview blade still works but Microsoft’s current documented path is Server > Security > Networking.
Access Group Support IP Ranges
Please add the following firewall rules so that Access Group staff can provide configuration and reporting support:
Region | IP Range |
Access Group UK | 212.54.135.128 – 212.54.135.159 |
Access Group US | 40.87.12.20 |
Access Group AUS | 103.84.112.192 – 103.84.112.223 |
Warning: Please confirm these IP ranges are current with your Coins project manager at time of deployment. Static IP documentation can become outdated.
Record SQL Database Connection String
Open the SQL Database blade and select the new database
Select Overview and then click Show database connection strings
Capture the “ADO.NET (SQL authentication)” connection string.
Typical SQL Database connection string:
Server=tcp:coins-live.database.windows.net,1433;
Initial Catalog=coins-live;
Persist Security Info=False;
User ID={your_username};
Password={your_password};
MultipleActiveResultSets=False;
Encrypt=True;
TrustServerCertificate=False;
Connection Timeout=30;
Note: TLS 1.2 or higher is required. TLS 1.0 and 1.1 were retired by Microsoft on 31 August 2025. Ensure your client drivers support TLS 1.2+. The Encrypt=True and TrustServerCertificate=False settings in the connection string above are correct and enforce this.
Creating Additional Databases
After the initial SQL Server and database has been created, repeat the Create SQL Database, Configure SQL Database Access (Firewall), and Record SQL Database Connection String steps, but use the Additional DB JSON template provided by Coins to add an additional database to your existing Azure SQL Server.
Follow the same database configuration process but specify a new database name and select the SQL Server previously created.
Create Storage for Bulk Import
Create Bulk Storage
Open the Storage Account blade and select Create.
Location should match the Data Gateway Web App for best performance.
Accept all default settings for Advanced, Networking, Data Protection, and Encryption sections.
Proceed to Review + Create.
After creating the Storage Account:
Select the new Storage Account.
On the Overview screen, click Blob Service (or navigate to Containers under Data storage).
Add a new container named bulk. Set Public Access Level to Private (no anonymous access). Accept all other defaults.
Create Shared Access Signature Token (SAS)
Open the storage account and select Shared Access Signature from the left menu.
Set the end date to 10 years ahead.
Click Generate SAS and connection string.
Record both the Connection String and the SAS Token that are generated.
Warning: Store the SAS token and connection string securely. These credentials grant access to your bulk storage container.
Send Setup Information to Coins
Provide your Coins project manager with the following information once all steps above are complete. Coins recommend using a secure method such as encrypted email when sharing credentials.
Item | Details |
SQL Database Connection String | |
SQL Database Name | As configured in Create SQL Database |
SQL Administrator Login | Account with CONTROL permission |
SQL Administrator Password | As set in Create SQL Database |
Azure Blob Storage Connection String | |
Azure Blob Storage SAS Token |
Note: The SQL account provided must have privileges to create/drop tables, and create, update and delete data in the Coins Analytics on Azure databases.