Power BI in Dubai — what it does, what it costs and how we deliver it
This page is for someone deciding whether Power BI is the right move for a Dubai business and what it actually takes: which licence, how it connects to Tally, Zoho, Odoo, SAP or Dynamics, what Arabic support really means, what drives the price and how long a build runs. Oakwood Group builds Power BI reporting for organisations across Dubai and the UAE, quoted as a fixed price before work starts. Delivered in partnership with Roar Data, an Australian Power BI consultancy.
What Power BI is good at, and what it is not
Power BI is a reporting and analysis layer that sits on top of the systems a business already runs. It reads from the ERP, the payroll file, the CRM, the warehouse system and the spreadsheets, joins them in one governed data model, and refreshes on a schedule so the numbers leadership sees on Monday are the same numbers finance closed on Friday. That is what it is for, and at that job it is very good: one definition of revenue, margin, DSO or occupancy across every report, row-level security so a branch manager sees one branch, and a model that a second person can open and understand.
It is not a replacement for the ERP: transactions still get recorded in Tally, Zoho, Odoo, SAP or Dynamics, and Power BI reports what those systems hold. It is not a data-entry tool, so budgets and forecasts live in a spreadsheet or a planning tool and are read from there. And it is not a full right-to-left publishing tool: Arabic text renders, but the canvas does not mirror, as the Arabic section below explains.
Power BI services we deliver in Dubai
Six services, each with its own page, each quoted as a fixed price. Most engagements use one or two of them together.
Power BI consulting services Dubai
The full engagement: review, scope, data model, dashboards, handover and training, quoted as one fixed price.
Learn morePower BI dashboard development Dubai
Executive, finance and operations dashboards built on a governed model, with KPI definitions written down.
Learn moreCorporate Power BI training Dubai
Workshops for finance and operations teams, run on your own reports rather than sample data.
Learn morePower BI managed services UAE
Refresh monitoring, small changes, gateway upkeep and a named contact after the build is handed over.
Learn moreExcel reporting automation Dubai
Keep Excel where the business wants it and remove the manual copying, pasting and reconciling underneath.
Learn morePower BI performance optimisation
Slow refreshes, visuals that take twenty seconds to load, numbers two reports disagree on: diagnosed and fixed.
Learn moreExcel to Power BI migration Dubai
For the business whose reporting is a set of spreadsheets that one person understands. The logic is documented, rebuilt in a model, and reconciled to the old workbook before anyone switches.
Read the migration pagePower BI developer Dubai
For the business that already knows what it wants built and needs someone to build it: DAX, Power Query, data modelling and report design as a scoped block of work.
Read the developer pageWhich Power BI licence do you need?
Three licence shapes cover almost every Dubai business. The right one depends on how many people view reports, how big the data is, and whether Fabric is on the roadmap.
| Licence | Who it suits | What it adds | Watch-outs |
|---|---|---|---|
| Power BI Pro (per user) | Most Dubai businesses with up to a few hundred report users, already on Microsoft 365 Business or Enterprise plans. Some E5 plans include it. | Publishing to shared workspaces, apps, scheduled refresh (up to eight a day), row-level security, and sharing with anyone else who also holds Pro. | Every viewer needs a Pro licence, not only the authors. Model size is capped at 1 GB per dataset and the shared capacity throttles heavy refreshes. |
| Premium Per User (PPU) | Small teams that need Premium features (large models, paginated reports, deployment pipelines) without buying a capacity. | Model size up to 100 GB, 48 refreshes a day, XMLA read/write for tooling, paginated reports, deployment pipelines, datamarts. | Anyone who opens a PPU workspace also needs PPU, so the cost scales with viewers, not authors. Content cannot be shared back to Pro-only users. |
| Fabric capacity (F-SKU) | Groups with many viewers, heavy refresh schedules, or a plan to use Fabric workloads (lakehouse, pipelines, warehouse) as well as Power BI. | Capacity you pay for rather than per-viewer licences. From F64 upwards, users with a free licence can view content in the capacity. Pay-as-you-go can be paused; reserved pricing is cheaper for steady use. | Below F64 viewers still need Pro. Capacities can be throttled when overloaded, so someone has to watch the metrics app. Sizing is a decision, not a default. |
Two things worth knowing before you buy. First, the older Premium per-capacity P-SKUs are being retired: Microsoft has stopped selling them to new customers and is moving existing agreements onto Fabric F-SKUs at renewal, so a capacity bought today is an F-SKU. Second, Microsoft changes its prices and its bundling from time to time, so this page deliberately carries no figures; the current list prices are on Microsoft’s Power BI pricing page, and licences are bought from Microsoft or your reseller, not from us.
On where the data sits: Microsoft operates Azure regions in UAE North (Dubai) and UAE Central (Abu Dhabi), and a Power BI tenant stores its data in the home region chosen when the Microsoft 365 tenant was created. That region is set at tenant level, not per report (the Power BI admin portal shows it under “About Power BI”). If an older tenant has a European or US home region, a Fabric capacity can be placed in a UAE region and workspaces assigned to it, which keeps the Power BI data for those workspaces in the Emirates. Whether that matters depends on your own obligations under the UAE PDPL, DIFC or ADGM rules and your customer contracts; we set it up the way your policy requires, we do not interpret the policy for you.
Connecting Power BI to the systems Dubai businesses run
The question buyers usually have is not “can Power BI connect to our system” but “what does it take”. This table is the honest answer for the twelve sources most common in Dubai and the UAE.
Three things decide how hard a connection is: whether there is a native connector or you go through ODBC, an API or an export; whether the source is on-premises (a data gateway on a machine that stays on) or in the cloud (no gateway, but rate limits); and what the source does that is not obvious until the first refresh fails. The last column is the one that matters.
| System | Connection method | Refresh pattern | The common catch |
|---|---|---|---|
| Tally / TallyPrime | No native connector. ODBC from the machine running Tally, or scheduled XML export to a folder. | On-premises data gateway on the Tally machine or a server that can reach it. Scheduled refresh runs while Tally is open with the company loaded. | One company per ODBC session, so a group of Tally companies means one extract each and a consolidation layer in the model. Ledger data is not tabular until it is shaped. |
| Zoho Books | REST API through Power Query (Web connector) or a custom connector. | Cloud to cloud, no gateway. OAuth tokens need a refresh-token flow, not a pasted key. | API rate limits per organisation and per minute; a full-history reload can hit them. Each Zoho organisation is a separate connection, and custom fields arrive as nested JSON. |
| Odoo | PostgreSQL read replica with the native PostgreSQL connector, or the JSON-RPC / XML-RPC API. | Gateway if the database is self-hosted or on a private network; API path is cloud-only. | Odoo Online (SaaS) gives no database access, so the API is the only route and it is slow for volume. Many-to-many tables and module differences between versions catch people out. |
| SAP Business One | Direct to the SQL Server or HANA database with the native connector, or the Service Layer. | Gateway in almost every case; hosting partners often need to open a read-only user and a port. | Table names (OINV, INV1, JDT1) are opaque and open and closed documents live apart. HANA builds should use views or the semantic layer rather than raw tables. |
| Dynamics 365 Business Central | Native Business Central connector (API v2 / OData) for BC online. | Cloud to cloud, no gateway. Refresh is limited by API throughput, not the gateway. | The standard API pages do not expose every table; GL entries at volume usually need a custom API page or query. One environment per company means one connection per entity. |
| Dynamics 365 Finance | Synapse Link or Fabric Link to Dataverse, or the older entity store / BYOD export. | Cloud to cloud. Link setup is an administrator task on the Finance side before any report can be built. | There is no direct SQL read of the production database. Data entities are wide and the finance ones need a dimension-set join that is easy to get wrong. |
| Oracle NetSuite | SuiteAnalytics Connect (ODBC/JDBC) or SuiteQL over the REST API. | Gateway for the ODBC route; REST route runs cloud to cloud. | SuiteAnalytics Connect is a paid add-on. The transaction / transactionline structure and subsidiary consolidation need modelling before the numbers match the NetSuite reports. |
| Sage (50, 200, 300, Intacct) | Sage 50/200/300: SQL or ODBC against the company database. Intacct: REST API or its ODBC driver. | Gateway for the on-premises editions; cloud to cloud for Intacct. | Schemas are edition-specific and change between versions, so a model built for Sage 200 does not port to Sage 300. Year-end routines can renumber periods. |
| QuickBooks Online | Native QuickBooks Online connector, or the API for entities the connector does not expose. | Cloud to cloud, no gateway. QuickBooks Desktop needs ODBC through a gateway instead. | One company file per connection and a fixed entity list; multi-currency and class tracking need API calls the connector skips. API throttling applies on full reloads. |
| Xero | Xero API through a third-party connector or Power Query. No Microsoft-maintained connector. | Cloud to cloud. Token refresh must be handled in the connector or the refresh fails quietly after expiry. | Rate limits per minute and per day, so incremental refresh is the norm rather than the option. Each Xero organisation is its own connection; tracking categories arrive unpivoted. |
| Excel and SharePoint | Native SharePoint folder, Excel and OneDrive connectors. | Cloud to cloud when the files live in SharePoint or OneDrive. A file server or network drive needs a gateway. | Files that change shape (a new column, a renamed sheet, a merged header cell) break refresh. Someone with the file open in the wrong mode can hold a lock during the refresh window. |
| SQL Server and Azure SQL | Native connector, DirectQuery or Import. | Gateway for on-premises or VM-hosted SQL Server; none for Azure SQL with the firewall opened to the service. | Query folding is lost the moment a step in Power Query cannot be translated to SQL, and refresh times balloon. Use views, not tables, so the model survives a schema change. |
The industry systems follow the same pattern. Opera PMS and IDS in hotels, Yardi and MRI in property, SAP EWM, Infor and custom TMS platforms in logistics, LS Central and Oracle Xstore at the till, and marketplace seller reports from Noon and Amazon.ae all come in through a database read, an API or a scheduled export, and each has its own catch. Those are covered on the industry pages under Power BI dashboards by industry UAE.
Multi-entity is the normal case, not the exception
A typical Dubai business is a mainland LLC plus a free-zone entity, sometimes a branch in Abu Dhabi or Saudi Arabia, often with a separate company file for each. Reporting across them means one extract per entity, a shared chart-of-accounts mapping (the entities rarely share one), currency conversion where a subsidiary trades in USD, SAR or INR, and intercompany eliminations. None of that is difficult in Power BI, but all of it has to be scoped, which is why entity count is one of the main cost drivers below.
The same model can carry the tax view. Sales and purchase transactions tagged by VAT treatment (standard-rated, zero-rated, exempt, out of scope, reverse-charge imports and designated-zone supplies) let a dashboard reconcile to the figures on the VAT return, and entity-level segregation keeps mainland and qualifying free-zone income apart for the Corporate Tax computation. To be clear about what that is: it is a reconciliation view of your own ledger. Oakwood Group is not a tax agent or an auditor, and the return itself stays with your accountant. The Excel to Power BI migration Dubai page goes into the VAT and Corporate Tax reporting shapes in more detail.
Arabic and bilingual reports — what is realistic
Most vendors either promise full Arabic support or do not mention it. Neither is honest. Here is what Power BI does and does not do.
Arabic text renders. Titles, labels, table cells, slicer values and tooltips display Arabic correctly, including mixed Arabic and English strings, and the Power BI service itself is available in Arabic. Fonts are the usual limitation: a custom theme font without Arabic glyphs falls back to boxes, so use one Power BI ships with or one you have tested.
Bilingual field names are a modelling job. Field parameters let a slicer switch a visual between an English measure and its Arabic-named twin, so one page serves both audiences. A translation table (one row per field, one column per language) does the same with a single DAX pattern and scales better past a dozen fields. Model-level metadata translations, which switch every name by the viewer’s locale, need a Premium or Fabric workspace and external tooling.
The canvas does not mirror. A right-to-left report in the full sense (slicers on the right, axes reversed, page navigation reversed) is not something Power BI supports. Some visuals honour a text-direction setting for their content, but the layout stays left-to-right. Where a document must be fully right-to-left, a paginated report or a formatted export is the practical answer.
Dates and numbers follow the viewer, mostly. Formats follow the browser or Power BI locale, and Arabic-Indic digits or Hijri dates appear only where the visual and the data support them. Most finance teams in Dubai want Western digits and Gregorian dates, and a model can fix formats so every viewer sees the same thing.
Our recommendation for most Dubai businesses: an English data model and measure names, with Arabic display labels where a specific audience needs them, such as a board pack for Arabic-speaking directors. It keeps the model maintainable by anyone and confines the translation work to the pages that need it.
How much does Power BI cost in Dubai?
Three separate costs, paid to two different parties. Only one of them comes from us, and that one is fixed before work starts.
- Licences (Microsoft)
- Per user (Pro or Premium Per User) or per capacity (Fabric F-SKU), paid to Microsoft or your reseller at their published rates. Many Dubai businesses already hold Pro inside Microsoft 365 and pay nothing extra for the first report.
- Build (Oakwood Group, fixed)
- One quote in writing against a written scope. The quote is the price. Builds start at AED 15,500 and most land between AED 15,500 to AED 62,000; the ranges by shape below say what moves a quote up or down inside that band. It covers the data model, the report pages, security, documentation, handover and the training agreed in the scope. How fixed pricing works is set out at the foot of this page.
- Run (optional managed service)
- A monthly arrangement for refresh monitoring, gateway upkeep, small changes and a named contact. Optional; some clients run their own reporting after handover and training, and the build is designed so they can.
What drives the build quote
- Number of sources. One ERP is one extract. An ERP plus payroll, CRM, a warehouse system and four spreadsheets is six, each with its own refresh and failure modes.
- Cleanliness. A tidy chart of accounts, customer names spelt one way and item codes that mean one thing shorten the work. Free text where a code should be lengthens it.
- Entities. Each legal entity adds an extract, a mapping and a reconciliation; intercompany eliminations and currency conversion add modelling.
- Security. Row-level security so a branch or a free-zone entity sees only its own rows needs a security model and testing per role.
- Pages and visuals. Four well-designed pages are a different job from twenty. We would usually argue for fewer.
- People trained. Two report authors is a workshop. Forty viewers across three sites is a programme.
Where a quote usually lands, by shape
Builds start at AED 15,500, and most fall between AED 15,500 to AED 62,000. A build is quoted rather than bought from a price list, so read the table as where a build of that shape usually sits in that band and what moves it either way — not as a quote for yours.
| Shape | Where it sits in the range | What moves the quote |
|---|---|---|
| Single source, one department | The bottom of the band, at or near the AED 15,500 starting point. One system, one audience, a handful of pages: a sales dashboard from Zoho, AR ageing from Tally, a warehouse KPI page from the WMS. | Up: history that only exists in spreadsheets, a source with no supported extract, more pages than the audience will read, a room full of people to train. Down: one clean source, one audience, and someone on your side who can settle a definition in a day. |
| Multi-entity finance model | The middle of the band. Two or more legal entities, a shared chart-of-accounts mapping, currency conversion, intercompany eliminations, P&L, balance sheet and cash flow, security by entity. | Up: every additional entity, a chart of accounts the entities do not share, subsidiaries trading in USD, SAR or INR, and eliminations that have never been reconciled. Down: one ERP holding every company, a mapping that already exists, and a trial balance the model can be reconciled against. |
| Group with ERP plus operational systems | The top of the band. The finance model above plus WMS, TMS, PMS, POS or CRM feeds, operational KPIs joined to financial ones, and several audiences with different security. | Up: each operational system is its own extract, its own refresh and its own failure modes, and each audience is another security role to build and test. Down: phasing. We would quote finance first, then one operational system at a time, each phase priced on its own and live before the next starts, so the first number is a fraction of the whole. |
We publish the method alongside the figures, because the drivers above are what put a build at one end of the band or the other. The band is where a conversation starts. Your number is written against your scope before any work begins, and that written number is the price.
How long does it take?
Timelines depend on the shape of the build more than the size of the business. Three shapes cover most Dubai engagements.
| Shape | What it involves | Indicative duration |
|---|---|---|
| Single source, one department | One system (an ERP, a CRM or a set of spreadsheets), one audience, a handful of pages. A sales dashboard from Zoho, an AR ageing report from Tally, a warehouse KPI page from the WMS. | The shortest shape: measured in weeks, and the first working page usually appears in the first of them. |
| Multi-entity finance model | Two or more legal entities, a shared chart-of-accounts mapping, currency conversion, intercompany eliminations, P&L, balance sheet and cash flow pages, row-level security by entity. | Longer, because the reconciliation to each entity’s own trial balance is the work, not the visuals. Typically a matter of months rather than weeks. |
| Group with ERP plus operational systems | The finance model above plus WMS, TMS, PMS, POS or CRM feeds, operational KPIs joined to financial ones, several audiences with different security, and a managed service afterwards. | The longest shape and the one we would phase: finance first, then one operational system at a time, each phase live before the next starts. |
What shortens it
- A clean chart of accounts, or at least one someone can explain.
- A named owner on your side who answers definition questions within a day.
- Read access to the source systems granted in the first week, not the fourth.
What lengthens it
- History that exists only in spreadsheets, each month in a slightly different layout.
- Undocumented Excel logic: formulas nobody can explain that still have to be matched.
- A hosting provider who controls database access and answers slowly.
- Two departments with two definitions of the same number and nobody empowered to choose.
Power BI or Tableau or Qlik?
A fair comparison. All three are capable; the differences are mostly about licensing shape and what the rest of your stack looks like.
| Consideration | Power BI | Tableau | Qlik Sense |
|---|---|---|---|
| Licensing model | Per user (Pro, PPU) or per capacity (Fabric F-SKU). Free viewing on F64 and above. | Per user in three tiers: Creator, Explorer, Viewer. Server or cloud. | Per user (Full and Analyzer) with capacity-based options for larger estates. |
| Microsoft 365 fit | Native: Entra ID sign-in, Teams embedding, Excel “Analyze in Excel”, SharePoint, Dataverse, Fabric. | Works with Entra ID and has an Excel connector; not embedded in the Microsoft stack. | Similar to Tableau: integrates, but sits alongside rather than inside. |
| Excel-heavy finance teams | The easiest transition. Power Query and DAX are already in Excel, and a Power BI model can be pivoted from Excel. | A different mental model; strong visual design once learned. | Associative model is a strength for exploration, a learning curve for finance users. |
| Cost at 50 users | All per user. Usually the lowest if Pro is already in the Microsoft 365 plan. | Per user across the three tiers; Viewer seats are cheaper than Creator seats. | Per user; Analyzer seats cheaper than Full. |
| Cost at 500 users | A Fabric capacity (F64+) with free viewers is usually cheaper than 500 Pro licences; it needs sizing and monitoring. | Viewer tier keeps the per-user cost down; no free-viewer capacity option. | Capacity-based pricing becomes relevant; needs a conversation with Qlik. |
| Where it is strongest | Governed reporting across Microsoft-centred businesses; self-service for Excel users; cost at scale. | Bespoke visual analysis, data-journalism-grade design, non-Microsoft stacks. | Free-form exploration across many tables; long-standing estates in larger groups. |
When we would not recommend Power BI
If your business runs on Google Workspace with no Microsoft identity platform, the integration advantages disappear and the cost comparison becomes closer. If you have a hard requirement for a fully mirrored right-to-left canvas, you should see Power BI’s limits before you commit. If you already have a Tableau or Qlik estate that works and a team that knows it, switching almost never pays back on the licence saving alone. We build in Power BI because it fits the businesses we work with; we will say so if it does not fit yours.
See it working
Two demo dashboards you can open now. Demo built on synthetic data to show layout, KPI definitions and interaction. Not client data.
Logistics and supply chain demo
Look for the on-time delivery measure and how it changes when you filter by lane, the cost-per-shipment definition in the tooltip, and the drill from region to customer to shipment.
Open the demoReal estate portfolio demo
Look for the drill from portfolio to building to unit, the occupancy and collection-rate definitions written into the visual titles, and how the comparable-period toggle handles a month that contains Ramadan.
Open the demoWhat we don’t claim
You will not find client logos, star ratings or a partner badge on this site. Oakwood Group is a new practice in the UAE and we would rather show you how we work than borrow proof. What we can show you: our process, our pricing method, demo dashboards built on synthetic data that you can open right now, and the partnership under which the work is delivered. Delivered in partnership with Roar Data, an Australian Power BI consultancy.
Questions people ask about Power BI in Dubai
Plain answers to the eight questions that come up before almost every engagement.
What does Power BI cost in the UAE?
Which Power BI licence do we need?
We already have Power BI licences. Can you use them?
Does Power BI support Arabic?
Do we need to replace our ERP to use Power BI?
Which data sources can Power BI connect to?
What AI features does Power BI have, and what do they need?
How does Power BI compare to Tableau?
How fixed pricing works
Every build is quoted before work starts, and the quote is the price. This is the sequence.
A short discovery call, no charge
Thirty minutes on Teams or WhatsApp, and a look at your current reports and the systems they pull from. We tell you the smallest practical next step, even if it is smaller than you expected.
A written scope
Sources, the data model, pages and visuals, users and their security, training and handover, all written down. If it is not in the scope, it is not in the quote.
A fixed quote against that scope
One number in writing. The quote is the price; there is no hourly rate underneath it to drift.
Surprises inside scope are our cost
If a source turns out messier than it looked, that is on us. If you want something outside the scope, we quote it separately, in writing, before doing it.
Payment stages
Agreed in the quote, in writing, before the work starts.
We publish the method as well as the figures, because the method is what tells you whether the figures apply to you. Builds start at AED 15,500 and most land between AED 15,500 to AED 62,000; which end yours sits at is settled by the scope, not by the starting price.
Ready to find out what Power BI would take for your business?
Four quick questions tell us the systems you run, the reports you assemble by hand and who reads them. From there, a 30-minute call, no charge, and a written scope if it makes sense to go further.