Arabic and right-to-left: the part that usually gets skipped
This is where we start because it is where most Gulf Power Platform work quietly fails.
Building an app in Arabic is not translating the labels. Right-to-left layout changes the reading order of every screen: navigation flips, form fields mirror, icons that imply direction have to reverse, and numbers and Latin product names embedded inside Arabic text have their own ordering rules that break if nobody has thought about them. A form that looks correct to an English-speaking developer can be subtly wrong to every user who actually uses it.
We publish this entire website in Arabic with right-to-left layout, and we handle Latin product names inside Arabic text correctly throughout — which is a specific engineering problem, not a translation one.
We mention it because it is unusual. Several Gulf Microsoft partners declare Arabic support in their structured data while publishing English-only pages. If your warehouse staff, site supervisors or finance team work in Arabic, the Power Apps forms and Power BI reports they use can work in Arabic too.
Where Power Platform genuinely fits, and where it does not
Power Apps is the right answer more often than custom-development firms admit. It is also the wrong answer more often than low-code enthusiasts admit.
It fits when the app is forms over data — inspections, approvals, requests, asset registers, site checklists — with an internal audience, where you already pay for Microsoft 365, and where speed to a working thing matters more than pixel control.
It stops fitting at identifiable points: a few hundred users on premium licences, an external or customer-facing audience, Dataverse storage climbing past your entitlement, or integration traffic pushing against the platform's request limits.
We build both Power Platform and custom .NET, which is why we are willing to say that plainly. A firm that only sells one of the two has a structural reason to tell you it is the answer.
The licensing traps, and the February 2027 date
Two things cost UAE companies money here, and both are avoidable if you know before you build.
The first is the premium trigger. The moment an app touches SQL Server, an on-premises gateway, Dataverse or any API you wrote yourself, every user of that app needs a premium licence. Not the maker — every user. Teams routinely design an app around a custom connector without realising they have just changed the per-user cost for the whole department.
The second is dated. Microsoft has stated that from February 2027, licensing requirements applied leniently until now will be enforced — including that in a managed environment the requirement attaches to active usage in the environment rather than to the app type. If your governance plan is to turn on Managed Environments broadly, price that before the date rather than after it.
We would rather raise this at design time than have you discover it at renewal.
Power BI for UAE finance and operations
The reporting requests we see most often in the Gulf cluster around three things: VAT position and return preparation, multi-entity consolidation across mainland and free-zone companies, and operational dashboards for trading, contracting and logistics businesses.
Multi-entity is the one that catches people. A UAE group frequently runs several entities with different licences, different jurisdictions and sometimes different functional currencies, and wants one view across them without waiting for the month-end close. That is a data modelling problem before it is a visualisation problem, and it is usually where a dashboard project either works or quietly becomes a spreadsheet again.
On residency: Power BI and Fabric workload availability differs between UAE North and UAE Central, and Fabric capacity region support is not identical to Azure infrastructure region support. We check it per workload during design.
What we deliver
• Power Apps — canvas and model-driven applications, in English and Arabic, including right-to-left layouts • Power BI — semantic models, reports and governed workspaces, with row-level security where entities must not see each other's data • Power Automate — approval flows, integrations and document automation • Dataverse design, environment strategy and DLP policy • Licensing review before you build, not after • Rescue work on Power Platform estates that have grown past anyone's control
Governance, before it is forty apps
The pattern is consistent and it arrives faster than people expect. One app becomes forty. Nobody knows which are in use. Several were built by someone who has left. Two connect to production data through a personal account. None have a test environment.
The fix is not complicated but it is real work: separate development, test and production environments; the default environment locked down; data loss prevention policies classifying connectors tenant-wide; solution-aware development so deployments go through a pipeline rather than a person.
None of this is UAE-specific, but it matters more here than it might elsewhere, because Gulf organisations frequently have a small IT function supporting a business that adopts tools fast. That combination produces sprawl quickly.
Dubai delivery, Indore engineering
Workshops, requirement sessions and user training run from Dubai. Build runs from Indore, where our 20 Microsoft-certified engineers are. Our week is Monday to Friday, Gulf Standard Time.
For Power Platform specifically this split works well, because the hard part is usually understanding the process, and that has to happen in the room with the people who do the work.
Frequently asked questions
Can Power Apps really work properly in Arabic?
Yes, and it is more than translated labels. Right-to-left layout changes navigation, field order and directional icons, and Latin product names inside Arabic text have ordering rules of their own. We build it rather than translate it — this site is published the same way.
What makes an app need a premium licence?
Touching SQL Server, an on-premises gateway, Dataverse or any custom API. The moment your app does, every user of it needs a premium licence — not just the person who built it.
What changes in February 2027?
Microsoft has said licensing requirements applied leniently until now will be enforced, including that in a managed environment the requirement attaches to usage in the environment rather than to the app type. If you plan to use Managed Environments broadly, price it before then.
Can Power BI handle our multi-entity UAE group?
Yes, including different jurisdictions and functional currencies across mainland and free-zone entities. The work is in the data model, not the dashboard, and row-level security keeps entities from seeing each other where required.
Can Power Platform data stay in the UAE?
Power Platform and Fabric workload availability differs between UAE North and UAE Central and does not exactly match Azure infrastructure availability. We verify it per workload during design rather than inferring it from the Azure region list.
We already have forty Power Apps nobody manages. Can you help?
Yes, and it is common work. It starts with an inventory of what exists, what is actually used and what connects to production data, then an environment and DLP strategy, then migration of the apps worth keeping.
Should we build this in Power Apps or as a custom application?
It depends on user count, audience and integration complexity. We build both, so we will tell you when Power Apps is the cheaper answer even though the custom project would be the bigger contract.
Do you build Power BI reports in Arabic?
Yes, including right-to-left report layouts and Arabic labelling. The numeric formatting conventions need deciding up front, because Gulf organisations differ on which numeral set they want.
How quickly can we see something working?
For a contained forms-over-data app, a usable first version in weeks rather than months. That speed is the main reason to choose Power Platform, and losing it to a long requirements phase defeats the purpose.
Do you have UAE Power Platform references?
Not yet — the Dubai office is new and we will not invent one. We can introduce you to clients elsewhere on comparable work, and our published case studies are real.