TiCON Cloud (TICON System Limited) designs, migrates and operates Microsoft Azure for companies in Bangladesh. The work is architecture and operations: a landing zone you can hand to an auditor, AKS or App Service for the apps, Entra ID tied to the Active Directory you already run, and Microsoft 365 as operations — not a licence marketplace. This is not an AWS reseller page with the logo swapped. Azure usage is billed on whatever paper the Microsoft agreement produces. A badge on this site is not a Solutions Partner designation or a CSP number — Microsoft’s partner directory is the record.
Last updated 21 September 2026
TiCON architects, migrates and runs Microsoft Azure in Bangladesh. That sentence is the whole commercial claim this page is allowed to make. It does not include a taka reseller invoice for Azure usage, a Microsoft 365 seat price list, or a Solutions Partner designation copied from a brochure.
On AWS, TiCON is an Advanced Tier Partner you can check on AWS Partner Solutions Finder, and it resells usage on a taka invoice. Those two facts are sourced. They do not transfer to Azure because the logo is in the same mega-menu. On Azure, the engagement is design, migration and operations. The Microsoft bill stays a Microsoft bill unless a separate Microsoft or partner programme — written in a contract, not invented here — changes the paper.
That split is useful. A Bangladeshi estate that already lives in Entra ID, Microsoft 365, Windows and SQL Server should not be talked into AWS for those workloads just because TiCON can invoice AWS in taka. The other way around is also allowed: keep the product on AWS (and pay that usage in taka) and land only identity and collaboration on Azure. Multi-cloud is allowed when there is a reason. Two identity systems and two bills without a reason is how estates get expensive and unauditable.
Staff certification lists are not published here. Numeric SLA minutes live in the managed-services contract, not on this page. Azure Reservations and savings plans exist as Microsoft pricing mechanisms; this page does not quote a percentage saving on Azure to match the AWS 15–35% / CloudFront-up-to-40% ranges, because those ranges are AWS reseller facts, not Microsoft list-price facts.
Microsoft Azure does not operate a region in Bangladesh. Traffic from Dhaka lands in India or Singapore. This page does not publish ping times; those need a dated measurement from a Bangladeshi ISP.
Azure’s India geography, checked on Microsoft’s public geographies page on 21 September 2026, lists Central India (Pune), South India (Chennai) and West India (Mumbai), plus Southeast Asia (Singapore) further east. Microsoft has announced a further India South Central region; announced is not the same as live, so the table below uses the regions Microsoft already lists as available.
For a regulator who asks where the bits sit, the honest answer is India or Singapore, then a document that names the region, the services in scope, and who can reach them. This page does not restate Bangladesh Bank circular numbers. AWS or Azure are the usual shortlists for regulated estates we see; that is a pattern, not a circular.
| Topic | On this page | Not on this page |
|---|---|---|
| Region in Bangladesh | No | A local-region promise, or a ping-time winner |
| Nearest published regions | Central India Pune; South India Chennai; West India Mumbai; Southeast Asia Singapore | Millisecond figures from Dhaka, or treating an announced region as live |
| TiCON’s commercial path | Architecture, migration and operations, quoted in taka for that work | An Azure-in-taka reseller or CSP invoice, or bKash as a Microsoft payment rail |
| Partner record | Microsoft’s Find a partner / Marketplace partner directory. This page does not invent a Solutions Partner designation or CSP number for TiCON | A screenshot of a badge, or a competitor’s designation copied from a brochure |
| Pricing | Quote after discovery. Azure Reservations exist; they are not restated as a TiCON percentage here | A public SKU table, or the AWS 15–35% range applied to Azure |
Region names are from Microsoft’s Azure geographies page, accessed 21 Sep 2026. Ping times and a taka-per-month winner are omitted.
Source: Azure geographies (opens in a new tab) Checked
Start from the estate you already run. Azure is the usual pick when Microsoft 365, Windows, SQL Server and on-prem Active Directory are already in the building. Hybrid with Entra ID is the reason, not a cheaper VM.
A governed multi-subscription foundation: management groups, policy, hub-and-spoke networking, identity, and logging. Microsoft publishes this pattern as the Cloud Adoption Framework landing zone. Aligning to that pattern is architecture work, not a Microsoft designation on this page.
Managed Kubernetes and PaaS for the apps that belong on Azure — including .NET estates that should not be talked onto a different runtime for fashion. AKS and App Service are Microsoft products; they are not a reason to invent a hybrid-mesh product name here.
Entra ID (the directory formerly labelled Azure AD), SSO, and conditional access, tied to the on-prem Active Directory you already operate. Identity is usually why Azure wins in a Microsoft shop. It is not a licence table.
Deploying and administering Microsoft 365 (Exchange, Teams, SharePoint) for a team in Bangladesh is operations work, including migration from on-prem Exchange or Google Workspace. It is not a CSP seat price list, and it is not a substitute for the Azure landing zone.
A badge on a company website is self-published. Microsoft keeps public partner directories. Use those. This page does not publish a TiCON Solutions Partner designation, CSP number, or specialisation from them.
Check a Microsoft partner in Microsoft’s directories
About 5 minutes
Use Microsoft’s directories, not a screenshot on this site, as the source for partner status.
Open Find a Microsoft partner
Go to partner.microsoft.com’s Find a partner page (the URL is in the sources below). Microsoft also points buyers at the Marketplace partner directory for solution providers.
Search the legal name, not only the trading name
Search TICON System Limited as well as TiCON Cloud. A trading-name miss is not evidence the company is unlisted, and a homepage badge is not evidence that it is listed.
Read designations from the listing, if there is one
If a listing exists, the directory is the record for Solutions Partner designations, specialisations and any CSP status Microsoft currently shows. If no listing exists, this page still does not invent one.
Match the legal entity to the contract
The company that will design or operate your project should be the company on the listing and on the statement of work. Ask for that match in writing. A CSP relationship, if you need one, is a Microsoft admin-centre relationship — not a sentence on this page.
Re-check before you renew
Partner programmes are reviewed and have been renamed. Repeat the check when the contract renews, not only at first signature.
Moving an estate onto Azure is still a migration: inventory, a TCO model, a wave plan, a rollback. The 6 R’s still apply. Azure Migrate is Microsoft’s tooling for assessment and replication; naming the tool is not a claim that every cutover is automatic. MAP co-funding is an AWS programme; this page does not invent a Microsoft equivalent amount.
Typical sources are on-prem Windows/SQL, VMware or Hyper-V, or an AWS estate that belongs next to Entra ID. A typical split we will actually recommend is Azure for identity and Microsoft workloads, AWS for the product that can be invoiced in taka. The other way around is allowed when the product is already on Azure. What we will refuse is a fashion multi-cloud.
After cutover, operations are the same job as on AWS — monitoring, IAM hygiene, backups, a named person who answers — with the Microsoft bill remaining a Microsoft bill. FinOps on Azure is reservation advice and idle-resource removal, quoted as work, not as a public saving percentage.
This page does not publish a Solutions Partner designation or a CSP number. Microsoft’s partner directories are the record. TiCON designs, migrates and operates Azure in Bangladesh. If a sales deck names a designation, believe the directory.
Yes: architecture, migration and operations on landing zones, AKS, App Service, Entra ID and Microsoft 365, with local support from Dhaka. That is not the same as reselling Azure usage on a taka invoice.
TiCON’s taka reseller invoice is for AWS usage. Azure work is quoted in taka for architecture and operations; the Azure usage bill follows the Microsoft agreement. This page is not an Azure-in-BDT product.
There is no region in Bangladesh. Nearby published regions are Central India (Pune), South India (Chennai), West India (Mumbai) and Southeast Asia (Singapore). Ping times are not published on this page. Announced regions are not treated as live.
None of the hyperscalers has a region in Bangladesh. Azure is a usual shortlist when Microsoft is already in the building. Residency and the auditor decide, not a slogan. Circular numbers are not restated here.
No CSP number or Azure reseller invoice in taka is published here. TiCON can deploy and operate Azure and Microsoft 365. Buying the usage and the seats still follows Microsoft’s own commercial path unless a written contract says otherwise.
Yes, when the workload belongs there — typically identity, Windows/SQL, or an estate already tied to Microsoft 365. We can also keep the product on AWS and land only identity on Azure. MAP funding amounts are not quoted; MAP is an AWS programme.
Yes: monitoring, IAM, backups and a named owner for in-scope Azure subscriptions, quoted in taka for that work. Numeric response times stay in the contract. Azure usage itself is not a TiCON reseller line.
