<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Dynamics365 (D365) Developer - Adecco RSS Feed</title>
    <link>https://jobs.co.uk/job/dynamics365-d365-developer-adecco--76958956-6c91-47da-9a4c-ed451137a42e</link>
    <description>RSS feed for Dynamics365 (D365) Developer at Adecco.</description>
    <language>en-gb</language>
    <lastBuildDate>Sat, 25 Apr 2026 18:39:37 GMT</lastBuildDate>
    <item>
      <title>Dynamics365 (D365) Developer - Adecco</title>
      <link>https://jobs.co.uk/job/dynamics365-d365-developer-adecco--76958956-6c91-47da-9a4c-ed451137a42e</link>
      <guid>https://jobs.co.uk/job/dynamics365-d365-developer-adecco--76958956-6c91-47da-9a4c-ed451137a42e</guid>
      <pubDate>Fri, 24 Apr 2026 11:52:38 GMT</pubDate>
      <description>Location: London | Salary: 550.00-550.00 Daily | Type: Temporary | Job Title: Dynamics365 (D365) DeveloperDay Rate: £550 per day UmbrellaLocation: Newham (Hybrid Working) We are currently recruiting for a Dyanmics365 Developer on behalf of our public sector client based in Newham. The focus of this role is designing and deploying custom solutions across D365 modules, customizing workflows and plugins, integrating with enterprise systems using Power Platform and Azure, and maintaining existing applications. The role requires collaboration with stakeholders, adherence to best practices, and staying updated on Microsoft features.Key Responsibilities:Design, develop and deploy custom solutions within D365 (Finance and Operations, Customer Engagement, or Business Central depending on scope)Customise entities, workflows, plugins and business rules to support business processesIntegrate D365 with other enterprise systems using Power Platform, Azure service sand APISCollaborate with business analysts, stakeholders and other developers to gather requirements and translate them into technical specificationsMaintain and enhance existing D365 applications and troubleshoot issues as they ariseEnsure solutions are scalable, secure and aligned with best practice...</description>
      <category>Temporary</category>
    </item>
  </channel>
</rss>