Welcome to the Office JavaScript API Reference documentation repository. For the best experience, we recommend you view this content on docs.microsoft.com.
Note: You can find the documentation source files for Office JavaScript API concepts, quick starts, tutorials, and how-to guides in the OfficeDev/office-js-docs-pr repository.
Your feedback is important to us.
-
To let us know about any questions or issues you find in the docs, submit an issue in this repository. Make sure you state the version + build number of the client you are using, and provide repro steps, console output, and error messages, as appropriate.
-
We also welcome your contributions to this documentation. To contribute, fork this repository, update the files as you deem necessary, and submit a pull request with your proposed changes. For details, see Contribute to this documentation.
IMPORTANT: Do not modify files within the /docs/docs-ref-autogen folder of this repository. All of the files in that folder are autogenerated, so it is not possible to update them via pull request. To request a change to any of the files in the /docs/docs-ref-autogen folder, please submit an issue in this repository. You can read more about how the tooling in this repository here.
-
To submit a feature request for the Office.js API or platform, post your idea to the Microsoft 365 Developer Platform Tech Community, or if the feature request already exists there, add your vote for it.
Get a free sandbox, tools, and other resources you need to build solutions for the Microsoft 365 platform.
- Free developer sandbox Get a free, renewable 90-day Microsoft 365 E5 developer subscription.
- Sample data packs Automatically configure your sandbox by installing user data and content to help you build your solutions.
- Access to experts Access community events to learn from Microsoft 365 experts.
- Personalized recommendations Find developer resources quickly from your personalized dashboard.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ, or contact [email protected] with any additional questions or comments.