Connect Microsoft Word to Warp
Give Warp governed access to Microsoft Word’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft Word to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Microsoft Word in Runlayer
Add Microsoft Word from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Microsoft Word’s 4 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Microsoft Word
Each user signs in to Microsoft Word with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Microsoft Word from Warp
Microsoft Word’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
4 Microsoft Word tools in Warp
Runlayer policy decides which of these Warp users can call.
Add comment
Add a new comment in the Word document.
Create document
Create a new Word document in the root of the user's OneDrive.
Get document content
Fetch the raw Word document (DOCX) content from OneDrive/SharePoint given its SharePoint sharing URL.
Reply to comment
Reply to a comment in the Word document.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Microsoft Word call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more