What should we use - Power Platform or Azure Native services

Ranjan Bhasin 20 Reputation points
2026-07-29T11:42:11.5166667+00:00

We would like to automate ServiceNow based tickets. Current process is for each ticket raised by an employee, our ITSD team members get required training list info from a PDF and match it with actual completed training list of the employee from Workday. Then both lists gets matched and accordingly, ServiceNow ticket is updated.

In our technical design, we have converted PDF document to excel based information so that capturing information every time for a ticket becomes easy and accurate, instead of extracting information from PDF which can be a probabilistic ask. There will be a web portal which will do 4 tasks - a) store this excel based information, b) capture and show very detailed business journey logs to a leader, and, c) enable and facilitate inputs from humans during human in the loop (HITL).

We are thinking it to use native Azure services like Function Apps, Queues, to make the solution modular, resilient and scalable. Also, App Service and Azure PostgreSQL for web portal. We are planning to use C#.NET for APIs (backend) and writing modular code within Function Apps. Data from ServiceNow and Workday will be read and written through APIs provided by ServiceNow and Workday.

ITSD leader has asked us to explore if we can do all of this through Power Automate and Power Apps instead of using Azure cloud native services. Our team has highly skilled team in full stack development including C# and .NET.

Considering that our solution has to be highly scalable, observable (logging), resilient and very low maintenance effort, I would like to know which direction should we take - Azure native services with C# and .NET or Power Platform ?

Developer technologies | ASP.NET Core | ASP.NET API
Answer accepted by question author
Danny Nguyen (WICLOUD CORPORATION) 8,725 Reputation points Microsoft External Staff Moderator
2026-07-30T06:55:57.1833333+00:00

Hi @Ranjan Bhasin

I recommend an Azure Native or Fusion Development approach. Because your team is constrained by strict requirements for observability, scalability, and modularity, and already possesses high-level C#/.NET skills, forcing a low-code platform will likely introduce limitations and friction.

  1. Observability and Logging: Azure Functions combined with Application Insights provide unparalleled, granular telemetry and custom logging required for your "very detailed business journey logs." Troubleshooting complex, high-volume automated flows in Power Automate can be difficult due to platform abstractions. You can check out more details on how to set this up here: Monitor Azure Functions.
  2. Developer Experience & Scalability: Pro-code teams generally prefer the flexibility, version control, scaling, and CI/CD capabilities of Azure services. C# Azure Functions and Queues natively support the high scalability and low maintenance decoupling you are looking for.
  3. Bridging the Gap (Fusion Development): If your leader wants to leverage low-code for the integrations, consider Azure Logic Apps instead of Power Automate. Logic Apps are the Azure-native equivalent; they use the same ServiceNow and Workday premium connectors but integrate natively with Azure Functions, Queues, and standard developer CI/CD pipelines. This keeps the orchestration visual but retains the backend processing in Azure. You can learn more about picking the right service here: Choose between Flow, Logic Apps, Functions, and WebJobs, and explore hybrid approaches here: Fusion development approach.

I recommend moving forward with your proposed Azure Native design using C# for the heavy backend APIs, potentially dropping in Azure Logic Apps if you want to accelerate the ServiceNow/Workday connectivity.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.

Thank you. 

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.