m365-clients

Create and provision Dataverse and Microsoft Graph resources from a TypeScript client.

12|4|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/markus41/Claude-m --skill m365-clients
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m365-clients
Source: https://github.com/markus41/Claude-m/tree/main/m365-platform-clients/skills/m365-clients
Command: npx skills add https://github.com/markus41/Claude-m --skill m365-clients

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables developers to build and consume TypeScript clients for the Dataverse Web API and Microsoft Graph with a unified authentication flow, reducing integration complexity.

Core Features & Use Cases

  • Typed Dataverse client with CRUD, OData queries, and WhoAmI helper.
  • Typed Graph service with common Microsoft 365 operations (users, groups, Teams, SharePoint, mail).
  • Shared authentication via Azure Identity (DefaultAzureCredential) across both services and sample workflows that provision interconnected resources (Dataverse records and Graph resources).

Quick Start

Run the combined provisioning workflow to bootstrap a Dataverse record and related Graph resources.

Frequently Asked Questions about m365-clients

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use a unified TypeScript client for Dataverse and Microsoft Graph?

A unified TypeScript client for Dataverse and Microsoft Graph uses Azure Identity authentication to automate resource provisioning. It provides typed CRUD operations, OData queries, and common Microsoft 365 operations like managing Teams channels and SharePoint assets.

Do I need Azure Identity permissions to provision Dataverse records and Graph resources?

Yes, Azure Identity permissions are required to provision Dataverse records and Graph resources. The client uses DefaultAzureCredential for shared authentication across both Dataverse Web API and Microsoft Graph services.

What's the best way to automate provisioning across Dataverse and Microsoft 365?

Automating provisioning across Dataverse and Microsoft 365 is best handled by a single TypeScript client. It executes end-to-end workflows that create interconnected Dataverse records, Teams channels, and SharePoint assets using unified patterns.

Can I query Dataverse Web API using OData with a typed TypeScript client?

Yes, you can query the Dataverse Web API using OData with this typed TypeScript client. It supports standard CRUD operations, OData queries, and includes a WhoAmI helper to verify connectivity and authentication.

Does this unified Graph and Dataverse client handle Microsoft 365 operations like mail and groups?

Yes, the unified client handles common Microsoft 365 operations. The typed Graph service supports managing users, groups, Teams, SharePoint assets, and mail alongside Dataverse records through a single authentication flow.

How does DefaultAzureCredential work across Dataverse and Graph services?

DefaultAzureCredential provides shared authentication across Dataverse and Graph services by using a single unified token flow. This reduces integration complexity by eliminating the need for separate authentication setups for each API.