.NET SharePoint Backend API Development
Budget: €18 – €36 EUR
I’m modernising a .NET Framework 4.8 solution that sits on ASP.NET MVC + CSOM and surfaces data from SharePoint Online. The priority is the backend: I need new, well-structured APIs and a clean migration path away from legacy CAML queries.
Environment & tech you’ll touch every day
• SharePoint Online with PnP Core SDK
• Azure AD app-only and delegated flows via MSAL (OAuth/OIDC)
• Entity Framework + Azure SQL Database
• Azure App Service / Functions, Key Vault, Application Insights
What I need from you
• Replace existing CAML logic with LINQ using PnP Core SDK.
• Design and implement a set of secure API endpoints that expose SharePoint list data and Azure SQL entities. REST is the natural choice, but I’m open to GraphQL or even SOAP if you can justify the fit.
• Plug the APIs into our current authentication model (AAD tokens, app-only and delegated).
• Wire detailed telemetry to App Insights so I can trace every request end-to-end.
Acceptance is straightforward: code compiles on .NET 4.8, passes my unit tests, deploys to our Azure Dev environment with zero regression, and every endpoint is documented in Swagger.
If deep backend work, SharePoint intricacies, and Azure-centric deployments are your comfort zone, let’s get this moving.
Environment & tech you’ll touch every day
• SharePoint Online with PnP Core SDK
• Azure AD app-only and delegated flows via MSAL (OAuth/OIDC)
• Entity Framework + Azure SQL Database
• Azure App Service / Functions, Key Vault, Application Insights
What I need from you
• Replace existing CAML logic with LINQ using PnP Core SDK.
• Design and implement a set of secure API endpoints that expose SharePoint list data and Azure SQL entities. REST is the natural choice, but I’m open to GraphQL or even SOAP if you can justify the fit.
• Plug the APIs into our current authentication model (AAD tokens, app-only and delegated).
• Wire detailed telemetry to App Insights so I can trace every request end-to-end.
Acceptance is straightforward: code compiles on .NET 4.8, passes my unit tests, deploys to our Azure Dev environment with zero regression, and every endpoint is documented in Swagger.
If deep backend work, SharePoint intricacies, and Azure-centric deployments are your comfort zone, let’s get this moving.
Related categories:
C# Programming
Sharepoint
Azure
ASP.NET
Microsoft SQL Server
OAuth
.NET Core
API Development