Power Automate and Power Platform Support Services for the Netherlands
Managed support, project rescue, and proactive monitoring for Dutch businesses running Power Automate, Power Apps, and Dynamics 365 Customer Engagement, inside CET business hours.
Need reliable Power Automate and Power Platform support in the Netherlands? Solzet provides managed services, project rescue, and proactive monitoring for Dutch businesses. Our engineers work from Yerevan inside CET business hours, with a working day that starts before yours, and cover complex flow troubleshooting, connector licensing, and Power Platform governance. We help Dutch companies stabilize the automation they already run, prevent the outages that come from expired connections and unowned flows, and get more out of the Microsoft 365 and Power Platform investment they are already paying for.
The short answer
- What we support. Power Automate cloud flows and desktop flows, Power Apps, Power Pages, Dataverse, custom PCF controls, and Dynamics 365 Customer Engagement. Not Business Central, not Finance and Operations.
- How it is delivered. Remotely from Yerevan, in your own Microsoft tenant, on a euro denominated B2B contract with a mutual NDA and a GDPR compliant data processing agreement.
- When we are available. Armenia is UTC+4 with no daylight saving, so we are two to three hours ahead of the Netherlands and our day starts before yours.
- What we are not. A Dutch company, a Dutch language helpdesk, or a manned twenty four hour operations centre. The page below is explicit about all three.
What CET coverage actually means when the team sits in Yerevan
Most nearshore and offshore support claims about time zones are unverifiable. This one is arithmetic. Armenia sits on UTC+4 and has not observed daylight saving since 2012, so the gap to the Netherlands is three hours in your winter and two in your summer. Our working day therefore opens before yours does.
| Period | Offset | Our 09:00 to 18:00 in your time | Overlap with a 09:00 to 17:30 Dutch day |
|---|---|---|---|
| Dutch winter time (CET, UTC+1) | Yerevan is 3 hours ahead | 06:00 to 15:00 in Amsterdam | 09:00 to 15:00, six hours of live overlap |
| Dutch summer time (CEST, UTC+2) | Yerevan is 2 hours ahead | 07:00 to 16:00 in Amsterdam | 09:00 to 16:00, seven hours of live overlap |
| Shifted schedule by agreement | Team starts two hours later in Yerevan | 08:00 to 17:00 in Amsterdam in winter | Almost the whole Dutch working day |
The practical consequence is the one that matters for support: a ticket raised first thing on a Dutch Monday morning lands in a working day that is already underway. It does not sit in a queue waiting for a time zone to wake up, which is the failure mode that makes far offshore support feel slow even when the engineers are good.
The flow failures we are actually called in for
Power Automate rarely breaks because the logic was wrong. It breaks because something around it moved: a person left, a policy changed, a licence lapsed, a volume grew. Start from the symptom you are seeing.
| What you see | What it usually is | What we do about it |
|---|---|---|
| A flow that ran for two years stopped overnight and the error mentions the connection | The connection was authenticated by a person, and that person has left, changed their password, or been caught by a new conditional access policy. The token behind the connection is theirs, not the company's. | Move production flows onto connection references owned by a dedicated service account inside solutions, and audit every connection in the environment for a human owner who no longer works there. |
| Microsoft emailed somebody who left to say the flow had been turned off | Flows are suspended after a long run of failures or a long period without a successful trigger, and the notification goes to the flow owner. If the owner has gone, nobody sees it until the business process breaks. | Give every production flow at least two owners, route platform notifications to a monitored shared mailbox or Teams channel, and add the ownership check to the joiners and leavers process. |
| Runs are queued, delayed, or failing with throttling errors under load | Service protection and request limits are being hit: too many Dataverse calls per user per period, an unbounded apply to each loop, or a nightly sync that lists every row and updates them one at a time. | Add pagination and concurrency control, batch the writes, split long flows into child flows, and move bulk work off the interactive window. Where the volume genuinely does not fit, move the heavy lifting to Azure and let the flow orchestrate. |
| A connector that always worked is suddenly blocked for everyone | A tenant data loss prevention policy changed, and the connector moved into a group that cannot share data with the other connectors in the same flow. The flow itself was not touched. | Review the DLP policy against what production actually uses, agree an exception route with the platform owner, and test policy changes in a non production environment before they reach the tenant. |
| The flow works for the person who built it and fails for everybody else | Two different things wear the same symptom: the running user lacks the Dataverse security role or record access the flow assumes, or they lack the licence the premium connector in the flow requires. | Separate the two by testing as the affected user, then fix the right one: security role and ownership on the data side, or the correct Power Automate licence on the connector side. |
| The flow cannot be moved to another environment, or it vanished when somebody left | It was built outside a solution, usually in the default environment, so it is a personal artefact rather than a deployable one. There is no clean export, no environment variable for the changing values, and no target environment to promote to. | Rebuild it as solution aware with environment variables and connection references, and put a development, test, and production path in place so the next change does not have to be repeated by hand. |
| A trigger fires far more often than the process it represents | An update trigger with no filtering columns and no trigger condition, so every touch of the row starts a run, including the ones the flow itself causes. | Set filtering columns and a trigger condition so the flow starts on the change it cares about, and check for the loop where a flow updates the row that triggers it. |
| A hybrid flow fails after a server patch or a password change | The on premises data gateway is offline, or the account the gateway runs under has expired credentials. The flow is fine; the bridge to the network is not. | Run the gateway under a managed service account, cluster it so a single machine is not a single point of failure, and alert on gateway health rather than waiting for the flow failure. |
Desktop flows fail differently, and for reasons that have nothing to do with the list above: selectors, waits, sessions, and machine groups. Those are covered in depth in our Power Automate Desktop production reliability guide.
Connector licensing, the thing that quietly decides your bill
Dutch mid market companies almost always come to the Power Platform from Microsoft 365, which is what makes licensing so easy to get wrong. The first flows are free, so nobody asks the question until the estate is already load bearing.
Standard connectors come with Microsoft 365, premium ones do not
The Power Automate use rights seeded into a Microsoft 365 subscription cover standard connectors: Outlook, SharePoint, Teams, OneDrive, Forms, Excel, Approvals. The moment a flow touches a premium connector, a custom connector, or the on premises data gateway, the flow needs a separate licence. This is the single most common reason a proof of concept works and the rollout does not.
Dataverse is premium, and that surprises people
Anything talking to Dataverse, and therefore anything talking to Dynamics 365 Customer Engagement, is on the premium side of the line. If your automation strategy is built on Dataverse as the data layer, which is usually the right architecture, then premium licensing is part of the design decision and not an afterthought discovered at renewal.
Per user or per flow, and the answer is not always per user
Licensing a premium flow can be attached to the people who use it or to the process itself. One tenant wide automation that every employee triggers indirectly is usually cheaper licensed per process; a team of makers each building their own premium flows is usually cheaper licensed per user. Getting this wrong in either direction is expensive, and it is one of the first things we check when we take over an estate.
RPA and AI Builder are separately licensed again
Attended desktop flows, unattended desktop flows, and AI Builder capacity are all licensed separately from cloud flows, and unattended RPA in particular carries its own requirement. A desktop automation costed as if it were a cloud flow will not survive its first budget review.
Trials expire, and they take production with them
A large share of the emergency calls we take start with a flow built by somebody on a trial licence, or by a consultant whose account has since been deprovisioned. When the licence goes, the flow stops. Part of taking over an estate is finding every flow whose continued existence depends on a licence nobody is deliberately paying for.
Check the current Microsoft licensing guide before you commit
Microsoft renames plans and changes what they include with some regularity, and the seeded rights in Microsoft 365 have been adjusted more than once. We work from the current Power Platform licensing guide for any number that goes into a budget, and we recommend you read it alongside us rather than trusting a page like this one, or any consultancy, for the figure.
We are not a licence reseller and we do not earn anything from what you buy, so the advice runs in whichever direction the numbers point, including downwards. If you are heading into a Microsoft renewal, our guide to Dynamics 365 licensing costs and renewal negotiation covers the commercial side in detail.
What proactive monitoring means here
Proactive is an easy word to put on a support page. These are the four things it maps to in our engagements, and the third one is the one that actually prevents outages.
Alerting inside your own tenant
Failure alerting is built where the flows run, not in a system you cannot see. A monitoring flow watches the runs that matter and raises a Teams message or an email to a shared, monitored destination, so an alert never depends on one person still working at the company.
Business level reconciliation, not just run history
A flow can report success and still not have done the work. For the processes where that matters, we add a check that counts what should have happened against what did, because the run history only tells you the actions completed.
A scheduled review by a named engineer
Alerts catch the outage. The review catches the drift: the flow that has been retrying every night for a month, the connection about to expire, the environment filling up, the licence about to be reassigned. That review happens on a fixed cadence and produces a short written list, not a dashboard nobody opens.
Release wave checks before they reach you
Microsoft ships two release waves a year plus continuous updates. We track what is changing in the areas your automation depends on and test the ones that touch you in a non production environment, so a platform update is a scheduled task rather than an incident.
How managed support is structured
Support scales with how much the business depends on the platform. Most Dutch clients start in the middle row and move in one direction or the other after the first quarter.
| Model | What it covers | Who it suits |
|---|---|---|
| Monitoring only | We put failure alerting and a health dashboard in place in your tenant, watch for failures, and tell your team what broke and why. Your people do the fixing. | Organizations with an internal maker or admin who can act, but no way of knowing something failed until a user complains. |
| Dedicated allocation, typically 20 to 40 hours a month | A named senior engineer with context on your environments. Flow maintenance, break fix, small enhancements as processes change, licensing reviews, and release wave checks. | The common case for a Dutch mid market company running a meaningful amount of Power Platform without a dedicated platform team. |
| Full managed service | A team that owns the platform with you: support plus governance, ALM, a backlog of improvements, and delivery of new automations alongside the support work. | Organizations where the Power Platform now carries processes the business cannot run without, and where new demand keeps arriving. |
| Response targets | Agreed in the support contract against your own severity definitions, in writing, before the engagement starts. We do not publish a single number here because it is a commercial term, not a property of the platform. | Every tier. What we will commit to is that a ticket raised at the start of a Dutch working day lands inside our working day, not the next one. |
How we move an existing estate into support
Whether the trigger is a partner who has stopped answering, an employee who built everything and then left, or a platform that simply grew past what one person can hold, the sequence is the same.
- 1
Inventory what you are actually running
Before anything is fixed, we build the list nobody has: every environment, every solution, every flow and app, who owns each one, which connections they depend on, which of those connections belong to a person who has left, and which premium connectors are in use. In most estates this stage alone finds flows nobody knew were running and flows everybody assumed were.
- 2
Take the platform off individual people
Production automation should not depend on one employee's account. We move production flows into solutions with connection references, re point them at a dedicated service account, add a second owner to everything that matters, and route Microsoft platform notifications to a shared destination that is actually monitored.
- 3
Triage the broken and the fragile by business impact
The backlog gets ordered by what it costs you when it fails, not by how old the ticket is. Anything that touches invoicing, customer commitments, or a regulatory deadline goes first. Everything else is scheduled, and the things that are broken but harmless are written down rather than silently carried.
- 4
Put monitoring and alerting in place
We build failure alerting into your tenant, add reconciliation checks for the processes where a successful run does not prove the work was done, and set the review cadence. From this point onwards you find out about a failure from us rather than from the person waiting on the output.
- 5
Fix the licensing and the DLP policy against reality
We map what is in use against what is licensed and what the tenant DLP policy allows, then reconcile the three. That produces two lists: the automations that are running on borrowed time, and the licence spend that is not buying anything. Both are usually a surprise.
- 6
Write the runbooks
Each supported process gets a short document: what it does, what it depends on, how it fails, and what to do about each failure. This is what makes support transferable between engineers and what stops the knowledge leaving again when a person does.
- 7
Set the guardrails so the estate stops sprawling
Environment strategy, a DLP policy that separates business from non business connectors, a development to test to production path with managed solutions and source control, and a clear answer to who may build what and where. Governance here means citizen development stays possible and stays safe, not that it gets banned.
- 8
Run steady state with a monthly review
Day to day support runs against the agreed response targets, and once a month we sit down with your platform owner: what broke, what changed, what Microsoft is about to change, what the licence position looks like, and what is worth building next. The support relationship should reduce the number of incidents over time, and the review is where you check that it is.
Where the problem is bigger than the automation, for instance a Dynamics 365 rollout that has stalled or a partner who has walked away mid programme, the same discipline runs at project scale in our Dynamics 365 project rescue and takeover service, and a scoped read of the current state is available as a health check and technical audit.
Working with a Dutch business from Armenia
Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy headquartered in Yerevan, Armenia. We are not a Dutch company and we do not pretend to be one. What Dutch clients get instead is a senior team, English as the working language with Russian and Armenian also available, and rates that a consultancy of equivalent seniority in the Randstad does not reach. Our engineers hold Microsoft certifications across the Power Platform (PL-200, PL-400, PL-600) and Dynamics 365 (MB-210, MB-230, MB-240).
Commercially, engagements run on a B2B contract, either time and materials or fixed price per milestone, invoiced in euros with international wire transfer, and in pounds or dollars where a group prefers it. For a Dutch VAT registered business buying services from a supplier outside the EU, the reverse charge normally applies, so we invoice without VAT and you account for it in your own return. Confirm that with your own adviser, since it depends on your registration and how the services are classified.
On data, we work inside your tenant rather than moving your data to ours. Your Dataverse and Power Platform data stays in the region you already chose for your environments, and support does not copy production data to Armenia. Access is through accounts you create in your own tenant with least privilege roles, which you grant and can revoke at any time, and where a problem has to be reproduced outside production we use masked or synthetic data. Every engagement carries a mutual NDA and a GDPR compliant data processing agreement, the AVG in Dutch terms, with IP ownership defined in the statement of work.
We also work as a white label subcontractor for Microsoft partners, including partners in the Netherlands, where our consultants operate under your brand, use your tooling, and do not appear to your end client as a third party. That is a different commercial shape from the support described on this page, and both can run at once.
Where we are the wrong answer
A support page that only lists strengths is not much use to somebody trying to choose, so here are the cases where you should call somebody else. If you need end user support in Dutch, for people who will phone rather than raise a ticket, we cannot provide it. If you need engineers physically on site, in a workshop room with your operations team, a local partner will serve you better. If your automation has to be watched through the night, our standard model does not cover it and the honest answer is that a follow the sun arrangement costs what it costs.
And if your problem lives in Business Central, Dynamics 365 Finance, or Supply Chain Management, that is outside what we do at all. We stay on the Customer Engagement side of Dynamics 365 and on the Power Platform, and we would rather integrate cleanly with your ERP partner than claim ground we do not hold. Where we are the right answer is the middle of the market: a Dutch company that has built real dependence on Power Automate and Power Apps, has nobody senior enough to own it full time, and needs that ownership at a price that makes sense against the size of the estate.
Frequently Asked Questions
Do you provide Power Automate support services in the Netherlands?
Yes. We provide Power Automate and Power Platform support to Dutch businesses as a managed service, delivered remotely from Yerevan, Armenia. That covers break fix on cloud and desktop flows, proactive monitoring and alerting, connector and licensing reviews, DLP and environment governance, ALM, and new automation work alongside the support. Engagements run on a B2B contract in euros with a mutual NDA and a GDPR compliant data processing agreement. We work in your tenant, using access you grant and can revoke.
You are in Armenia, so how does support inside CET business hours work?
Armenia sits on UTC+4 all year, with no daylight saving. That makes us three hours ahead of Dutch winter time and two hours ahead of Dutch summer time, so our working day starts before yours and ends in your mid afternoon. On a standard schedule that is six hours of live overlap in winter and seven in summer, and we shift the team start time later where afternoon cover matters more. In practice it means a ticket raised at nine in the morning in Amsterdam is picked up inside a working day rather than waiting for one to open.
Are you a local Dutch supplier?
No, and we would rather say so on the page than have you find out on the call. Solzet is an Armenian company with no office in the Netherlands and no Dutch language helpdesk. What we offer instead is CET working hours, English as the working language, euro invoicing, a GDPR compliant contract, and senior Microsoft certified engineers at a rate a Dutch consultancy of the same seniority does not reach. If your requirement is on site presence in Utrecht or end user support in Dutch, a local partner is the right answer and we will say so.
Can you take over Power Platform work built by a partner or an employee who has gone?
Yes. This is a large part of what we do. Taking over an estate starts with an inventory of environments, solutions, flows, owners, and connections, because the usual reason a handover was never clean is that nobody had that list. We then move production off personal accounts and onto service accounts and connection references, triage what is broken by business impact, and document each supported process in a runbook. We do the same for stalled or abandoned Dynamics 365 Customer Engagement projects through our project rescue and takeover service.
Which Power Automate licences do our flows actually need?
It depends on the connectors. Standard connectors such as Outlook, SharePoint, Teams, and Approvals are covered by the Power Automate use rights seeded into Microsoft 365. Premium connectors, custom connectors, and the on premises data gateway require a separate licence, either attached to the users or to the process, and anything touching Dataverse or Dynamics 365 is on the premium side. Desktop flows and AI Builder are licensed separately again, with unattended RPA carrying its own requirement. Because Microsoft renames plans and adjusts what they include, we work from the current Power Platform licensing guide for anything that goes into a budget rather than from memory.
What does proactive monitoring mean in practice?
It means alerting built inside your own tenant on the flows that matter, reconciliation checks for the processes where a successful run does not prove the work was done, a named engineer reviewing the estate on a fixed cadence, and release wave changes tested before they reach your production environment. It does not mean a manned twenty four hour operations centre, and we do not describe it as one. If your automation genuinely needs cover through the night, that is a separate conversation about scope and cost, not a checkbox.
Where does our data sit, and how is GDPR handled?
We work inside your Microsoft tenant, so your Dataverse and Power Platform data stays in the region you already chose for your environments and is not copied to Armenia as part of support. Access is through accounts you create in your own tenant with least privilege roles, which you can revoke at any time. Where we need to reproduce a problem outside production we use masked or synthetic data. Every engagement runs under a mutual NDA and a GDPR compliant data processing agreement, which Dutch readers will know as the AVG, with IP ownership defined in the statement of work.
How is a contract with an Armenian supplier handled for VAT and payment?
We invoice in euros on a B2B contract and support international wire transfer, and we can also invoice in pounds or dollars where a group prefers it. For a Dutch VAT registered business buying services from a supplier outside the EU, the reverse charge normally applies, so we invoice without VAT and you account for it in your own return. Confirm the treatment with your own adviser, since it depends on your registration and how the services are classified.
Do you support Business Central or Dynamics 365 Finance and Operations?
No. Solzet works on the Customer Engagement side of Dynamics 365, meaning Sales, Customer Service, Field Service, and Customer Insights, plus the Power Platform: Power Apps, Power Automate, Power Pages, Dataverse, Copilot Studio, and PCF controls. We do not work with Business Central, Finance, or Supply Chain Management. If your automation needs to integrate with one of those, we build and support the integration from the Power Platform side and work with whoever owns the ERP.
How quickly can support start, and what is the minimum commitment?
A senior engineer can usually start within weeks rather than the months an internal hire takes, and an emergency stabilization can start sooner where something in production is down. For an ongoing allocation we recommend at least 20 hours a month, because below that the context retention costs more than the hours buy. Monitoring only engagements are smaller. We also take fixed price work for a defined piece of remediation where you want cost certainty before committing to a retainer.
Power Platform support for your Dutch business
Tell us what is running, what keeps breaking, and who owns it today. We will come back with what we would inventory first, what we think it costs to stabilize, and whether we are the right people for it.
Building rather than fixing? See standing up a Power Apps Center of Excellence with a nearshore team and our Power Platform development and support service.