A Microsoft work or school account
Use the Microsoft Entra tenant your organization already manages.
Desktop network workspace · active validation
Desktop release coming soonDOC Microsoft 365 setup
Prepare an organization-owned Entra public client, grant the delegated Microsoft Graph access Copilot Chat requires, and sign in from a supported Palshell installation.
Microsoft’s Copilot Chat API currently uses Microsoft Graph /beta. Microsoft says preview APIs can change and are not supported for production use. A successful Palshell test confirms access only for the tenant, user, license, and policy in front of you.
01 Before you begin
This path is for an existing Microsoft 365 organization. It does not create a tenant, license, or trial account.
Use the Microsoft Entra tenant your organization already manages.
The signed-in user needs an eligible Microsoft 365 Copilot license.
Microsoft’s quickstart uses at least the Application Developer role; tenant policy may be stricter.
The required delegated permissions need deliberate tenant review and approval.
02 Configuration
The IDs identify your app and directory; they are not credentials. Microsoft authentication remains delegated to the signed-in user.
MICROSOFT ENTRA ID
Paste this into Palshell’s Application (client) ID field.
Paste this into Palshell’s Tenant field.
Use Entra’s copy controls for both real values. Do not copy Object ID—it identifies a different directory object.
AUTHENTICATION
MICROSOFT GRAPH
Sites.Read.All
Mail.Read
People.Read.All
OnlineMeetingTranscript.Read.All
Chat.Read
ChannelMessage.Read.All
ExternalItem.Read.AllA new app registration may also show the default User.Read permission. It is not one of the seven Copilot Chat permissions Palshell requests.
TENANT REVIEW
Tenant-wide consent is a sensitive decision. For a limited rollout, your administrator can also require user assignment on the enterprise application and assign only approved users or groups.
PALSHELL SETTINGS
https://graph.microsoft.com/betaDEVICE LOGIN
03 API cost
Microsoft says this preview Chat API is available at no extra cost to users who already have a Microsoft 365 Copilot add-on license.
No separate per-token charge for this licensed API path.
Every user calling the API needs an eligible licensed account.
Palshell does not meter this integration by input and output tokens.
“No extra cost” does not mean the Microsoft product is free. Your organization still pays for the qualifying Microsoft 365 Copilot license under its Microsoft agreement. Microsoft also offers separate pay-as-you-go Copilot products, but those are not the licensed Chat API path configured by this guide. Checked September 7, 2026.
Microsoft Copilot Chat API licensingPalshell stores the resulting access and refresh-token envelope in macOS Keychain or Windows Credential Manager, bound to the client ID and tenant. Tokens stay behind the native credential boundary and are never displayed in the Palshell interface.
04 Troubleshooting
Most setup failures come from tenant consent, licensing, account choice, or organization policy—not from the Base URL.
05 Official references
Microsoft owns the Entra screens, permission contract, licensing rules, and preview API. These are the primary sources used for this guide.
App registration, supported account types, and application ID.
Why device-code authentication uses a public client without a secret.
Microsoft’s device-code sign-in protocol and security behavior.
License, account, preview, and platform requirements.
Required delegated permissions and the Microsoft Graph preview endpoint.
Authorized roles, review guidance, and the Entra consent workflow.
How tenant policy evaluates and can block device-code authentication.
Why this Palshell guide and fixed Base URL target the global commercial cloud.