Microsoft Copilot Studio Freelancer to package and deploy Enterprise AI Agents

We are looking for a hands-on Microsoft Copilot Studio + Power Platform ALM specialist to help productionize and package three internal AI agents for an enterprise customer. The functional scope, use cases, response boundaries, and early prototypes are already being defined. This is not a blank-sheet strategy role. We need someone who can take a structured handover pack and turn it into a robust, deployable Copilot Studio implementation. The main focus is Phase 1: policy-based agents grounded in approved SharePoint content, with access controlled via Microsoft Entra ID groups. Key Responsibilities • Configure and productionize agents in Microsoft Copilot Studio • Package the agents using Power Platform solutions • Apply proper managed / unmanaged solution discipline • Use environment variables and connection references for tenant-specific values • Set up / validate SharePoint-grounded knowledge sources • Support SharePoint architecture for segmented policy access • Work with Entra ID / security groups for role-based and country-based access • Support testing for grounding quality, permissions, access separation, channel behavior, and response behavior • Support controlled deployment into the customer tenant • Troubleshoot issues during import, publishing, UAT, and pilot • Document setup, deployment, and support procedures clearly Required skills • Microsoft Copilot Studio / Agent Builder • Power Platform ALM • Managed and unmanaged solutions • Dataverse concepts • Environment variables and connection references • SharePoint grounding / SharePoint permissions • Microsoft Entra ID / security groups • Teams / Microsoft 365 Copilot deployment • UAT, troubleshooting, and deployment support • Ability to document implementation steps clearly Strongly preferred experience with: • enterprise knowledge assistants • SharePoint knowledge-base architecture • multi-group / role-based access models • deploying solutions across dev/test/production environments • working with customer IT teams that control import, publish, and governance Nice to Have — Future Phase The first phase is SP based-only. A later phase may explore read-only integration with Dynamics 365 Finance & Operations / data. Nice-to-have experience: • Dynamics 365 F&O integration • MCP servers / MCP connectors • FinOps Database Connector • Power Platform connectors • Secure read-only data access patterns • User-scoped authorization and least-privilege design This is not required for Phase 1, but relevant experience would be valuable for future work. What We Will Provide • Functional agent prototypes / concept • Agent instructions and guardrail requirements • Policy categories and target use cases • Access segmentation requirements • Testing expectations and UAT scenarios • Customer-side deployment constraints as they become confirmed What Success Looks Like • The agents are packaged cleanly as deployable Copilot Studio / Power Platform solutions • Tenant-specific values are parameterized, not hard-coded • SharePoint grounding works reliably • Users only access policy content appropriate to their group • The customer IT team can import, configure, test, and publish the solution under its governance model • The implementation is documented well enough for handover and support