Maisy Studio
Maisy Blog

Microsoft My Company Policy Agent: Give Employees One Place to Ask How the Company Works

Employees ask policy questions constantly.

How much PTO do I get? What is the remote-work policy? Which holidays are paid? How do I submit an expense? What happens during my first 90 days? Where do I go for IT help?

Most companies already have the answers. The problem is that they are scattered across SharePoint, handbooks, HR documents, intranet pages, and service portals.

Microsoft’s My Company Policy agent is designed to turn those approved sources into one conversational employee reference point.

What Is the My Company Policy Agent?

My Company Policy is a Microsoft 365 Copilot agent template designed to answer employee questions about company policies and services.

Microsoft says the agent can answer questions across HR, IT, travel, expenses, compliance, and other internal policy areas using authoritative company documents stored in SharePoint and information published on the organization’s website.

It is not supposed to answer from generic knowledge.

The useful version of this agent answers: “What does our company say?” not “What do companies usually do?”

What Can Employees Ask?

An employee could ask the agent to summarize the types of leave available to them, explain parental-leave requirements, list paid holidays, describe the first 90 days for a new employee, or surface information from company documentation.

Other realistic questions might include:

“Can I work remotely from another state?”

“How much PTO carries over into next year?”

“Where do I submit an expense report?”

“What is our travel-booking process?”

“Who do I contact about payroll?”

“What is the policy for replacing company equipment?”

These are exactly the questions that frequently interrupt HR, managers, IT staff, and administrative employees.

SharePoint Is the Important Part

Microsoft explicitly recommends grounding the agent in a SharePoint knowledge source containing the organization’s authoritative policy documents.

That is the part companies should pay attention to.

The agent itself is only the conversational layer.

If SharePoint contains one current remote-work policy, two obsolete versions, a draft revision, and an old PDF somebody uploaded three years ago, the organization still has a policy-management problem.

AI does not make those documents agree.

The better architecture is to identify the official source, archive superseded material, assign ownership, establish review dates, and then connect the agent to the approved information.

That is the same architecture described in Maisy’s guide to a Knowledge Hub built on SharePoint and Microsoft 365: SharePoint remains the governed system of record while focused Copilot agents provide conversational access to that knowledge.

It Can Personalize Answers by Employee Context

One particularly useful capability is Microsoft’s support for contextual answers.

The agent can use information such as the employee’s location and job title from their Microsoft 365 profile to help identify the most relevant policy version.

That matters for companies operating across multiple states, countries, locations, or employee classifications.

A PTO policy may differ between employees in Texas and California.

A travel policy might differ for executives.

An expense limit might vary by role.

A generic answer is therefore not always sufficient.

A well-designed agent can lead with the rule that appears relevant to the employee while acknowledging that other regional or role-specific policies may exist.

It Can Become an Employee Services Directory

The template can also provide links to common employee systems.

Microsoft specifically describes links to services such as payroll, IT support, facilities requests, HR case submission, and travel-booking tools.

That seems mundane, but it solves a very common problem.

Employees often know what they need to do but do not know where they are supposed to do it.

Instead of searching the intranet for the payroll portal, they could ask: “Where do I change my direct deposit?”

The agent explains the process and sends them to the correct system.

That is a much better use of AI than trying to make the agent perform every transaction itself.

Onboarding Is an Obvious Extension

Microsoft also suggests expanding the agent with onboarding knowledge such as new-hire requirements, 30-60-90-day plans, and buddy-program information.

That could turn My Company Policy into something closer to an employee onboarding assistant.

A new hire could ask: “What should I complete during my first week?”, “How do I request software?”, “Where is the expense policy?”, “What meetings should happen during my first month?”, or “Who approves time off?”

This is where organized policy knowledge starts reducing dependence on individual managers.

A strong onboarding system should map common employee questions back to approved sources, ownership, actions, and escalation paths rather than simply handing a new employee a folder of documents.

Policy Agents Need Strong Permission Controls

Company policies may sound harmless, but the broader knowledge environment often contains sensitive HR, payroll, financial, legal, and management information.

Those sources should not all be exposed simply because they live near the employee handbook.

The underlying access model therefore matters as much as the agent instructions.

Maisy’s Knowledge Hub security and permissions architecture follows the same rule: the AI layer should respect the organization’s existing identity and SharePoint permissions rather than becoming a shortcut around them.

The Agent Should Not Become the Final Authority

My Company Policy output should be treated as a starting point, not the official policy itself. Generative AI can make mistakes, and organizations remain responsible for ensuring answers comply with applicable laws, regulations, and internal rules.

That is particularly important for questions involving HR, leave, legal rights, compensation, or other circumstances where small details can materially change the answer.

A good policy agent should therefore provide citations and make escalation easy.

If the answer is uncertain, the safest response may simply be: “Here is the applicable policy. HR should confirm how it applies to your situation.”

That is not a failure.

That is good agent design.

Why My Company Policy Is One of the Strongest Templates

This agent addresses a problem almost every organization already has.

Employees repeatedly ask questions.

The answers already exist.

The people answering those questions are usually more expensive than the act of retrieving the information warrants.

Microsoft provides the conversational framework. SharePoint provides the governed knowledge. The organization still has to make sure that knowledge is current, authoritative, permissioned, and maintained.

Get that foundation right and My Company Policy becomes much more than another chatbot.

It becomes the place employees ask, “How do we do this here?”