Power Platform Developer in Armenia: Power Apps, Power Automate, and Power BI Development and Support from Yerevan
Hire senior Power Apps, Power Automate, and Power BI developers in Yerevan: a fixed scope build, the rescue of an environment somebody else built, white-label work behind your brand, or a developer inside your own team, with support afterwards.
Solzet is where you hire a Power Platform developer in Armenia. Our Yerevan team works as Power Apps developers, Power Automate developers, and Power BI developers on Dynamics 365 Customer Engagement and Dataverse, and the same engineers stay with you for support after go live. Every one of them is senior, with 8+ years in the Microsoft ecosystem, so nobody learns the platform on your project. Working with local Power Platform experts in Armenia gets you custom Power Apps, automated workflows in Power Automate, customer and partner portals on Power Pages, Power BI reporting over Dataverse, and PCF controls written in TypeScript and React. Solzet is a Microsoft Dynamics 365 and Power Platform consultancy headquartered in Yerevan, Armenia, working on B2B contracts with mid-market companies and Microsoft partners across the Caucasus, Europe, and the US, on full projects, on project rescues, and as a white-label subcontractor.
Hire a Power Platform developer in Armenia
If you arrived looking for a Power Apps developer, a Power Automate developer, or a Power BI developer in Armenia, these are the developer profiles our Yerevan team covers, what each one actually does on a project, and the platform work that sits under all of them. The same people scope the work, build it, and support it afterwards, so there is no handover between a consultant who promised something and a developer who has to make it real.
- Power Apps developer
- Builds the applications people open every morning: canvas apps where the screen layout and the mobile experience matter, and model-driven apps on Dataverse where the process and the data model matter. Day to day that means tables, relationships and keys, forms, views, business process flows, Power Fx logic, security roles and column level security, and connectors to SharePoint, SQL, or an API. Where a standard control cannot express what users need, the same developer writes a PCF control instead of compromising the screen.
- Power Automate developer
- Builds the processes behind the screens: cloud flows for approvals, notifications, scheduled jobs, and data synchronization between Dynamics 365, SharePoint, SQL, and third-party APIs, plus desktop flows that drive legacy Windows applications with no API. The part that separates a senior developer here is the error path. Every flow ships with error handling, retry logic, monitoring, and a named owner who is told when it fails, because that is where Power Automate implementations actually break.
- Power BI developer
- Builds the reporting layer over the platform: Power BI reports and dashboards on Dataverse and Dynamics 365 data, the semantic model and DAX measures underneath them, and the embedded views that put a chart inside a model-driven app rather than in a separate tool. Reporting is designed to respect the same Dataverse security model as the app it reports on, so a user sees in a dashboard exactly what they can see in the CRM. We deliver Power BI as the reporting end of the Power Platform work we build and support, not as a separate data warehouse practice.
- PCF and pro-code developer
- Writes the code for the places where low code runs out: PCF (PowerApps Component Framework) controls in TypeScript and React with Fluent UI, following the full lifecycle of init, updateView, getOutputs, and destroy, plus C# plugins and custom API against the Dataverse event pipeline, custom connectors, and integration through the Dataverse Web API. Controls ship as managed solutions ready to import, with source code and documentation so your team can maintain them.
- Dataverse and Dynamics 365 CE
- Underneath all four roles sits the platform work: the Dataverse data model the rest stands on, the security model, and application lifecycle management with managed solutions and pipelines across development, test, and production environments. Our developers work exclusively on Dynamics 365 Customer Engagement (Sales, Customer Service, Field Service, Customer Insights) and the Power Platform. We do not take on the Microsoft finance and supply chain applications; where you run one, we integrate with it.
The team model: senior only, based in Yerevan
Solzet is a senior-only consultancy. Every developer has 8+ years of hands-on experience in the Dynamics 365 and Power Platform ecosystem, and there is no delivery pyramid of juniors underneath them, so the person who scopes your work is the person who writes it. Certifications on the team include PL-200, PL-400 (the certification Microsoft itself names Power Platform Developer), and PL-600 for the Power Platform, plus MB-210, MB-230, and MB-240 for Dynamics 365 Customer Engagement.
Everyone sits in Yerevan, in the GMT+4 time zone, which leaves 4 to 6 hours of daily overlap with Western European hours and 6 to 8 with the UK. That is a shared working day rather than an overnight handover. We work in English, with Russian and Armenian also available, on B2B contracts with a mutual NDA and a GDPR-compliant DPA, and IP ownership is defined in the statement of work.
How you engage a Power Platform developer from Armenia
Full project, fixed scope
We specify, build, test, and hand over a defined app, flow set, portal, or reporting pack against dated milestones, with the source and the solutions belonging to you. Priced fixed per milestone or time and materials, whichever fits the certainty of the scope.
Project rescue and takeover
We take over Power Platform and Dynamics 365 environments built by other partners. The first step is an audit and a written picture of the technical debt, then a remediation roadmap, before anything is touched in production. It is a large enough part of our work to have its own service page.
White-label subcontracting
Microsoft partners engage our developers under their own brand and email, as part of their delivery team, in front of their end client. We do not list those end clients on public profiles.
Dedicated developer inside your team
One of our developers works with your team for an agreed number of days per month, in your Azure DevOps, GitHub, or Jira, at your standups and your code reviews, rather than running a separate process alongside. The allocation moves up and down with your backlog.
Managed support after go live
A monthly allocation for change requests, new flows as processes change, Power BI reporting, PCF upgrades, release wave updates, and user support. From roughly 20 hours a month with a part-time consultant up to a full managed-service team.
What the delivery process looks like from here
Send us the problem rather than a specification, if a specification is the thing you do not have yet. We reply within one business day, run a short scoping call, and come back within 5 business days with a proposal naming the scope, the engagement model, and the people who would do the work.
After that the developer works inside your tooling, whether that is Azure DevOps, GitHub, or Jira, joins your standups and sprint reviews, and follows your branching and review rules. Changes move between development, test, and production as managed solutions through deployment pipelines rather than by hand, and everything we build is handed over with source code and documentation so your own team can maintain it after we step back.
If the geography is not the deciding factor, the page on how to hire a Power Platform developer or Power Apps developer covers the role itself in more depth. For the narrower briefs, there is Power Automate workflow and RPA development, PCF controls development, and Dynamics 365 project rescue and takeover. Microsoft partners looking for capacity rather than a supplier should start at white-label subcontracting. If the CRM side is what you are really buying, the CRM consulting in Armenia page is the wider view, and the consulting firm Power Platform case study shows a canvas app, Power Automate approvals, and Power BI dashboards delivered together.
Power Platform vs. Off-the-Shelf CRM: A Guide for Armenian Businesses
Most people who go looking for Power Platform consultants in Yerevan are not shopping for developers yet. They are deciding something earlier: buy a closed CRM product and live inside it, or build on a platform that can be made to fit the business. Solzet answers that question for a living from Yerevan, and this is the guide we would talk you through on the call, before anyone quotes anything.
The generic version of this comparison is a feature grid, and it is useless here, because the features are not where the two options separate for a company operating in Armenia. They separate on Armenian and Russian vocabulary on screen next to English, dram beside foreign currency on the same deal, VAT at 20 percent and the counterparty tax ID enforced on the record rather than remembered by the accountant, the signed acceptance act as part of the document set, and an automated join to 1C or a local payment or banking rail. Those are the rows below, with a three year cost analysis at Yerevan rates underneath them.
The comparison that actually decides it in Armenia
Off the shelf here means a closed SaaS product configured only as far as its settings screen allows, which in this market usually means Bitrix24, amoCRM, Zoho, HubSpot, or Salesforce bought without its development platform. The Power Platform column includes the standard Dynamics 365 Customer Engagement apps, because on this platform the pre-built app and the custom extension are the same system rather than two purchases.
| What it comes down to | Off-the-shelf CRM product | Power Platform, built from Yerevan |
|---|---|---|
| Where the product stops | You get what the settings screen exposes. When a requirement falls outside it, the answer is a workaround, a spreadsheet living beside the CRM, or a request to a vendor roadmap you do not control. | The configuration layer is where every build starts here too. The difference is what happens at the edge of it: Power Fx, a Power Automate flow, a plug-in, or a PCF control. The requirement stops being impossible and becomes a priced line item. |
| Armenian and Russian alongside English | Interface languages are whatever the vendor ships, and Armenian is rarely among them. Staff work in Russian or English while the labels on screen never quite match the words the business uses out loud. | The base interface language is one Microsoft ships, and we will not pretend Armenian is on that list. What is yours is every table, column, view, form, and option set label, because those are strings you write. The vocabulary people read is the business vocabulary, and Dataverse holds Armenian, Russian, and Latin script in the same record without transliterating anything at the door. |
| Dram beside foreign currency | Multi-currency support ranges from good to a single fixed base currency. Where the product decides the base, AMD reporting happens in a spreadsheet after the fact. | Dataverse carries a base currency plus a transaction currency and exchange rate per record, so a deal quoted in dollars and reported to the board in dram is one record rather than two systems and a reconciliation. |
| VAT at 20 percent and the tax identity on the record | Tax handling is built for the vendor home market. The Armenian VAT rate, the counterparty tax ID, and the validation that should stop a document leaving without one are pushed to the accountant. | Tax logic, the TIN on the account record, and a rule that blocks a save or a document until it is present are ordinary configuration and plug-in work. It is the same category of change as any other business rule, priced in engineer days. |
| The acceptance act and the local document set | Quote, order, invoice, and little else. The signed acceptance act that Armenian and wider regional accounting practice expects at delivery is not a concept most products have, so it is produced by hand outside the system. | Documents follow the process you actually run, including the act, generated from the record, numbered the way your finance team numbers things, in the language the counterparty signs in. |
| Talking to 1C, the bank, and local payment rails | Integration is limited to the connectors the vendor chose to sell. 1C, ArCa, Idram, Telcell, and Armenian bank statement formats are not on that list, so the join between CRM and accounting is an export and somebody re-keying it. | Power Automate has both a maintained connector library and custom connectors for anything with an API, and where there is genuinely no API a desktop flow drives the application directly. The integration becomes engineering work with a price and an owner instead of a feature request with no date. |
| Where the data sits and which law applies | Data lands wherever the vendor hosts it, on terms published rather than negotiated. | The Dataverse geography is chosen when the environment is created, and the platform carries the compliance posture Microsoft publishes for it. There is no Azure region inside Armenia, so this is about choosing deliberately and being able to answer the question, both for the Armenian personal data law and for an Armenian company processing EU customer data under GDPR. |
| What the licence bill does as you grow | A per user subscription that scales linearly with headcount, charged in dollars or euros, renegotiated at renewal on the vendor terms. | Also per user, and worth sizing deliberately during design rather than discovering at renewal. The differences are that seats can be mixed by what each person actually does, and that the build itself is a one-time cost which does not repeat every month once it is done. |
| Who can change it in year two, and what you keep | The vendor, on their roadmap, plus whatever an administrator can reach from a settings screen. If you leave, you leave with an export of the records and nothing else: not the process, not the automations, not the reports. | You own the managed solutions, the source code, and the documentation, so the work can stay with a partner, move to your own team, or be split. Nothing about the system is reachable only by the people who built it. |
What each one costs here: 25 seats, three years, Yerevan numbers
The comparison buyers usually run is a build quote against a monthly subscription, which flatters the subscription because it stops after year one and leaves out the work people do to compensate for a system that does not fit. This one runs three years and puts a number on both sides. Subscription figures are public list prices at the time of writing and they move, so treat them as the shape of the arithmetic rather than a quote.
| Cost line | Off-the-shelf CRM product | Power Platform, built from Yerevan |
|---|---|---|
| Software, per user per month | Roughly USD 10 to 25 per user for the lighter products common in this region, and USD 80 to 165 at the mid tiers of the well known Western suites. List prices before any agreement discount. | Power Apps Premium sits around USD 20 per user per month at list, and standard Customer Engagement seats run from roughly USD 65 for Sales Professional to roughly USD 105 for the Enterprise tiers. Microsoft revises these, so confirm the current number during design rather than after go live. |
| Three years of subscription for 25 seats | About USD 9,000 at the low end, about USD 22,500 at the top of the regional band, and about USD 148,000 at the mid tier of a Western suite. The number recurs whether or not anyone changed the system that year. | The same arithmetic on the seats you genuinely need: about USD 18,000 for 25 Power Apps Premium seats, about USD 58,500 for 25 Sales Professional seats, about USD 94,500 at the Enterprise tier. Sizing by role during design is the single cheapest hour anyone spends on this. |
| The build itself, at Yerevan rates | Configuration inside the product by an administrator or a local reseller. Genuinely cheap while every requirement stays inside the product, and the ceiling is the product. | A certified senior engineer in Yerevan bills in the USD 40 to 70 per hour band, and a first Customer Engagement app is normally counted in tens of engineer days, not hundreds. Our decision guide breaks that into line items you can accept or defer before anyone quotes you a total. |
| Making it speak Armenian business | Mostly unavailable at any price, because it is not a paid option, it is a product boundary. The cost shows up as people working around the system. | Labels, the document set including the act, the tax fields, and dram reporting are ordinary configuration done once, inside the build days rather than as a separate invoice line. |
| The join to 1C and the local rails | A middleware subscription plus a developer, or people re-keying data twice. The recurring cost here is a person, and it is easy to miss precisely because it never reaches an invoice. | Priced as engineering days per endpoint, once, and shipped with error handling, retry logic, and a named owner who is told when it fails. |
| Change and support in years two and three | The subscription continues. Change beyond the settings screen has no path except a workaround or a migration. | From around 20 hours a month with a Yerevan consultant, which is a budget line you set on purpose rather than a number you discover in month fourteen. |
| How it is contracted and invoiced here | A card charged in foreign currency by a foreign entity. Fine until finance asks for a contract, an act, and an invoice that will satisfy an audit in Armenia. | Microsoft licences are billed by Microsoft or a partner and are separate either way. The delivery side is contracted with Solzet, an Armenian company in Yerevan, so a domestic client gets the document set an Armenian accountant expects, and an international client gets the B2B contract, mutual NDA, and GDPR-compliant DPA we work under everywhere else. |
| What you are holding after three years | A renewal, and an export if you leave. | A data model, apps, flows, reports, and source code that belong to you, plus the same discipline about seats. The subscription is still there; what it buys is no longer the ceiling. |
The effort behind the middle of that table, line item by line item, is set out in our guide to hiring a consultant against doing it yourself, including the rate bands by supplier origin and the ranges per line item. If the licence side is the part that worries you, the licensing cost and renewal guide covers seat tiers and renewal preparation properly rather than in one row.
When buying the product is the right answer
A build nobody needed is the most expensive thing on this page, so here is the honest half. Buy the product when all of these are true.
- •Your sales or service process is a pipeline with stages, and nothing about pricing, service commitments, or documents differs from the way any other company runs them.
- •The team is small enough that one administrator holds the whole configuration in their head, and their leaving would be inconvenient rather than dangerous.
- •Nothing outside the CRM has to read or write records automatically, and the handoff to accounting is genuinely a monthly export somebody does not mind doing.
- •You are still testing whether the company will use a CRM at all, and being wrong is cheap to undo.
- •Having something working this quarter matters more than what the system can become in three years.
If two or more of them are false, the question has quietly changed. It is no longer buy against build, it is which platform you build on, and how much of the first version you can configure before anyone writes code.
Why the consultant sitting in Yerevan changes the answer
Half the reason companies here buy the closed product is not the product. It is that building looked like a project with a foreign supplier, a foreign rate, a time difference, and a contract nobody in finance recognises. Delivery from Yerevan removes most of that. You are in the same working day, meetings can happen in a room, the engineering band is the regional one rather than the Western European one, and Solzet is an Armenian company, so a domestic client contracts and is invoiced the way an Armenian audit expects. English, Russian, and Armenian are all working languages here, which matters when the process being mapped is described in one language and the system has to be explained in another.
It also changes who does the work. Every Solzet consultant is senior, with 8+ years in the Microsoft ecosystem, and the person who scopes the decision is the person who builds what follows. That is what makes the honest half above possible: there is no junior bench to keep busy, so telling a company to buy the product and come back when they outgrow it costs us nothing except a project we should not have taken.
For the wider view of local delivery and the consultancy models available in the region, read the Dynamics 365 and Power Platform experts in Yerevan delivery guide. If you are checking who you would actually be signing with, the Solzet company profile has the company facts in one place. And when the decision is settled and the question is the role rather than the geography, the Power Platform developer and Power Apps developer service page covers what that person does day to day.
What Solzet builds on the Power Platform
Six delivery areas, each integrated with Dynamics 365 Customer Engagement and Dataverse rather than treated as isolated tools.
Custom Power Apps (canvas and model-driven)
We build both canvas apps, with pixel-level control over the UI for mobile and tablet scenarios, and model-driven apps on Dataverse for data-rich, process-driven work such as CRM, case management, and field data collection. Typical builds include inspection and audit apps, approval workflows, inventory tracking, and employee onboarding tools. Where standard controls fall short, we extend the app with custom PCF components rather than compromising on the experience.
Power Automate workflow automation and RPA
We design cloud flows for event-driven and scheduled automation, such as lead qualification, document approval chains, and data synchronization between Dynamics 365, SharePoint, SQL, and third-party APIs. For legacy Windows applications with no API, desktop flows automate the UI directly. Every automation ships with error handling, retry logic, monitoring, and documentation, because most Power Automate implementations fail on the error path, not the happy path.
Power Pages portals
We build external-facing Power Pages sites for customer self-service, partner collaboration, and public data access, connected to Dataverse and secured with Azure AD B2C or local authentication. Portals reuse the same data model and business logic as your internal model-driven apps, so customers and staff work from one source of truth instead of duplicated records.
Power BI reporting on Dataverse
Reporting is part of the build rather than an afterthought bolted on later. Our Power BI developers model the semantic layer over Dataverse and Dynamics 365 data, write the DAX behind the measures leadership actually asks about, and embed the result inside model-driven apps so the numbers sit next to the records they came from. Reports follow the same Dataverse security model as the apps, so nobody sees in a dashboard what they cannot see in the CRM.
PCF controls in TypeScript and React
PCF (PowerApps Component Framework) controls are our specialty. We build custom UI components, such as interactive data grids, map visualizations, signature capture, and rich editors, in TypeScript and React with Fluent UI, following the full PCF lifecycle (init, updateView, getOutputs, destroy). They run natively in both model-driven and canvas apps and ship as managed solutions ready to import, with source code and documentation so your team can maintain them.
Dynamics 365 Customer Engagement integration
Everything above sits on top of Dynamics 365 Customer Engagement: Sales, Customer Service, Field Service, and Customer Insights, all on Dataverse. We model tables and security roles, write plugins and business rules, connect D365 to ERP, telephony, email, and BI systems, and use the Power Platform to extend the CRM with the exact experiences your teams need. We focus exclusively on Dynamics 365 Customer Engagement and the Power Platform, and do not cover the Microsoft ERP and finance modules.
Ongoing Power Platform support from Yerevan
Development is only half the picture. Most of the value comes after go-live, when the environment has to keep evolving with the business.
Managed support for existing environments
A large part of our work is ongoing support for organizations that already run Power Platform and Dynamics 365 but need continuous improvement, bug fixes, new features, and user support. Packages range from a part-time consultant (around 20 hours a month) to a full managed-service team. Common tasks include new Power Automate flows as processes change, Power BI reporting on Dataverse, PCF upgrades, and applying Microsoft release-wave updates.
Project rescue and takeover
We regularly take over environments built by other partners. We audit the current state, document the technical debt, and propose a remediation roadmap before touching production, so you get a clear picture of what is fixable and in what order rather than another rebuild.
Governance and Center of Excellence
For organizations scaling Power Platform adoption, we set up governance: environment strategy across dev, test, and production, DLP policies, connector management, license right-sizing, the CoE Starter Kit, and maker training. This keeps citizen development productive without losing control of data or spend.
How nearshore delivery from Armenia works
Solzet is headquartered in Yerevan, Armenia, in the GMT+4 time zone. That gives roughly 4 to 6 hours of daily overlap with Western European business hours and 6 to 8 hours with the UK, enough for daily standups, sprint reviews, and stakeholder workshops over Teams or Zoom.
We work on B2B contracts, either time-and-materials or fixed-price per milestone, and communicate in English, with Russian and Armenian also available. Our engineers use the same Azure DevOps, GitHub, or Jira tooling as your internal teams and hold Microsoft certifications across Power Platform (PL-200, PL-400, PL-600) and Dynamics 365 (MB-210, MB-230, MB-240).
Every engagement runs under a mutual NDA and a GDPR-compliant DPA, with IP ownership defined in the statement of work. Microsoft partners can engage us on a white-label basis, where our consultants work under your brand as part of your delivery team.
Frequently Asked Questions
Can I hire a Power Platform developer in Armenia?
Yes. Solzet is a Yerevan based team of senior Power Platform developers, working as Power Apps developers, Power Automate developers, and Power BI developers on Dynamics 365 Customer Engagement and Dataverse. Every developer has 8+ years in the Microsoft ecosystem and holds Microsoft certifications including PL-200, PL-400 (the certification Microsoft itself names Power Platform Developer), and PL-600. You can engage us for a fixed scope project, for the rescue of an environment another partner built, as a white-label subcontractor behind your own brand, or as a dedicated developer who joins your team for an agreed number of days per month.
Where do I find Power Platform consultants in Yerevan?
Solzet is a Power Platform consultancy based in Yerevan, Armenia. Our consultants are senior, Microsoft certified engineers with 8+ years in the ecosystem, working across Power Apps, Power Automate, Power Pages, Power BI, PCF controls, and Dynamics 365 Customer Engagement. Because we sit in Yerevan we scope in the same working day as clients across the Caucasus, keep 4 to 6 hours of daily overlap with Western Europe, meet in person in Armenia when that is useful, and contract as an Armenian company for domestic clients. Engagements run as a fixed scope build, the rescue of an environment another partner built, white-label work behind a Microsoft partner brand, or a dedicated consultant inside your own team for an agreed number of days a month.
Should an Armenian business use the Power Platform or an off-the-shelf CRM?
Buy the closed product when your process is standard, the team is small, nothing has to integrate automatically, and being wrong is cheap to redo. Build on the Power Platform when the requirements a closed product cannot reach are the ones that matter here: Armenian and Russian vocabulary on screen alongside English, dram beside foreign currency on the same deal, VAT at 20 percent and the counterparty tax ID enforced on the record, the signed acceptance act as part of the document set, and an automated join to 1C or a local payment or banking rail. The comparison table and the three year cost analysis on this page work the decision through with Yerevan numbers, including the cases where we would tell you to buy the product.
What does a Power Platform build cost in Armenia compared with a CRM subscription?
A subscription is a recurring per user cost that does not stop when the system stops changing. Twenty five seats at USD 10 to 25 per user per month is roughly USD 9,000 to USD 22,500 over three years, and the same twenty five seats at the mid tier of a well known Western suite reach around USD 148,000. A Power Platform build is a one-time engineering cost on top of a per user licence, delivered at the USD 40 to 70 per hour band a certified senior engineer in Yerevan bills in, and it leaves you owning the data model, the apps, the flows, and the source code. Which is cheaper depends entirely on how much of your process the closed product can actually express, which is why we scope that before quoting anything. Microsoft list prices move, so confirm the current figures during design.
What is the difference between a Power Apps developer, a Power Automate developer, and a Power BI developer?
They are three parts of the same platform and often the same person. A Power Apps developer builds the applications people work in: canvas and model-driven apps, forms, views, business process flows, and the Dataverse data model underneath. A Power Automate developer builds the processes behind them: cloud flows for approvals, notifications, and data synchronization, desktop flows for legacy applications with no API, and the error handling and monitoring that keep them running. A Power BI developer builds the reporting layer over that data: the semantic model, DAX measures, dashboards, and views embedded in model-driven apps. Solzet developers work across all three, so the scope can shift without changing the person doing the work.
How much does it cost to hire a Power Platform developer in Armenia?
It depends on scope and duration, and any number quoted before scoping is a guess, so we do not publish a day rate. We work fixed price per milestone, time and materials, or as a dedicated developer booked for an agreed number of days per month. Armenian rates sit below Western European consultancy rates for the same certified senior people, and hiring this way carries no recruitment fee, payroll, or notice period. Send us the requirement and you get a proposal within 5 business days naming the scope, the engagement model, and the people who would do the work. Microsoft licences are billed separately by Microsoft and are worth sizing during design rather than after go live.
Which Power Platform and Dynamics 365 companies operate in Armenia?
Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy based in Yerevan, Armenia. We deliver Power Apps, Power Automate, Power Pages, PCF controls, and Dynamics 365 CE work for mid-market companies and as a white-label subcontractor for Microsoft partners across Europe and the US. Our engineers hold Microsoft certifications including PL-200, PL-400, and PL-600 for Power Platform, and MB-210, MB-230, and MB-240 for Dynamics 365.
How does remote Power Platform delivery from Armenia work?
Armenia sits in the GMT+4 time zone, giving roughly 4 to 6 hours of daily overlap with Western European business hours and 6 to 8 hours with the UK. That is enough for daily standups, sprint reviews, and stakeholder workshops over Teams or Zoom. We work on B2B contracts, communicate in English (with Russian and Armenian available), and use the same Azure DevOps, GitHub, or Jira tooling as your internal teams.
Can Solzet support an existing Power Platform or Dynamics 365 setup?
Yes. Alongside new builds, we provide ongoing managed support for organizations that already run Power Platform and Dynamics 365. That covers bug fixes, new Power Automate flows, PCF upgrades, Power BI reporting, release-wave updates, and user support. We also take over environments built by other partners, audit them, and propose a remediation roadmap before making changes.
Does Solzet build custom PCF controls for Power Apps?
Yes. Custom PCF (PowerApps Component Framework) controls are a core specialty. We build them in TypeScript and React with Fluent UI for both model-driven and canvas apps, from interactive data grids and maps to signature capture and custom editors. Delivery includes the managed solution ready to import, plus source code and documentation so your team can maintain the control.
How is data security and IP handled on a B2B contract?
All engagements run on B2B contracts with mutual NDAs and a GDPR-compliant DPA. IP created during the work belongs to your organization or your end client as defined in the statement of work. For white-label subcontracting, our consultants work under your brand and do not list your end clients on their public profiles.
Need Power Platform experts in Armenia?
Whether you need a Power Apps developer for a new build, a Power Automate developer for an automation pack, a Power BI developer for the reporting on top, a custom PCF control, or ongoing support for a Dynamics 365 environment, our Yerevan team can help. Tell us what you are working on and we will scope it with you.