What are the responsibilities and job description for the Microsoft 365 Copilot Architect || hybrid in Greenville, SC || Must work on our W2 position at 1 Point System?
Title: Microsoft 365 Copilot Architect
Duration: 12 Months
Job Location: Greenville, SC
Hybrid Role (2 days onsite and 3 days remote)
Need SC candidates first but we can take NC candidates as well who live 2 hours drive from SC
Must work on our W2
Need genuine LinkedIn profile
Need these skills
MS O365 Engineer/Architect using CoPilot, agents, connector and data sources hands on exp – MS graph a plus – 10 years of IT Admin/Engineering
4/22 Skills Matrix:
Microsoft 365 Copilot architecture, feature lifecycle, and rollout planning – 5 years
Hands-on knowledge of Copilot extensibility, including agents, connectors, and data sourcing – 3 years
Copilot Studio, custom agents, or AI orchestration patterns – 1 year
Familiarity with Microsoft Graph, data integration for search/knowledge architectures – 1 year (rest api process)
Day-to-Day
Evaluate, test, and position new Microsoft Copilot features within the AI portfolio
Design and lead enterprise rollout plans for Copilot, Agents, and AI extensibility scenarios
Architect solutions for Copilot Agents, agent interfaces, and enterprise knowledge experiences
Define integration patterns using Microsoft Graph Connectors and Copilot Search / knowledge sources
Lead complex, cross-functional AI adoption initiatives from concept to enterprise scale
Must Haves
Strong experience with Microsoft 365 Copilot architecture, feature lifecycle, and rollout planning
Ability to interpret new AI features and align them to enterprise use cases and product strategy
Hands-on knowledge of Copilot extensibility, including agents, connectors, and data sourcing
Strong architectural documentation and executive communication skills
Experience leading large-scale enterprise initiatives across IT, Security, and Business teams (e.g., portfolio, roadmap, demand intake)
Nice to Haves
Experience with Copilot Studio, custom agents, or AI orchestration patterns
Familiarity with Microsoft Graph, data integration for search/knowledge architectures
Exposure to AI governance, security, or compliance considerations in solution design
Highly regulated industry experience (i.e EU, automotive, State or Federal Government, etc.)