dcblogdev / laravel-microsoft-graph
A Laravel Microsoft Graph API (Office365) package
Fund package maintenance!
dcblogdev
Installs: 161 150
Dependents: 0
Suggesters: 0
Security: 0
Stars: 125
Watchers: 7
Forks: 56
Open Issues: 2
Requires
- ext-curl: *
- ext-fileinfo: *
- ext-json: *
- guzzlehttp/guzzle: 7.x
- illuminate/support: ^10.0|^11.0
- league/oauth2-client: ^2
- microsoft/microsoft-graph: ^1.110
- shitware-ltd/flysystem-msgraph: ^1.0
Requires (Dev)
- laravel/pint: ^1.13
- mockery/mockery: ^1.6
- orchestra/testbench: v8.0|v9.0
- pestphp/pest: ^v2.34
- pestphp/pest-plugin-laravel: v2.4
- pestphp/pest-plugin-type-coverage: ^2.8
- dev-master
- v4.0.2
- v4.0.1
- v4.0.0
- v3.2.6
- v3.2.5
- v3.2.4
- v3.2.3
- v3.2.2
- v3.2.1
- v3.2.0
- v3.1.9
- v3.1.8
- v3.1.7
- v3.1.6
- v3.1.5
- v3.1.4
- v3.1.3
- v3.1.2
- v3.1.1
- v3.1.0
- v3.0.11
- v3.0.10
- v3.0.9
- v3.0.8
- v3.0.7
- v3.0.6
- v3.0.5
- v3.0.4
- v3.0.3
- v3.0.2
- v3.0.1
- v3.0.0
- v2.04
- v2.03
- v2.02
- v2.0.1
- 2.0.0.x-dev
- v2.0.0
- 1.3.0
- 1.2.0
- 1.1.5
- 1.1.4
- 1.1.3
- 1.1.2
- 1.1.1
- 1.1.0
- 1.0.0
- dev-add-id-to-is-connected-inside-get-access-token
- dev-eminiarts/master
- dev-eminiarts-master
- dev-fix/cross-origin-authorization
This package is auto-updated.
Last update: 2024-11-19 11:50:34 UTC
README
There is a Discord community. https://discord.gg/VYau8hgwrm For quick help, ask questions in the appropriate channel.
Laravel Microsoft Graph
A Laravel package for working with Microsoft Graph API.
MsGraph comes in two flavours:
- MsGraph: login in as a user.
- MsGraphAdmin: login as a tenant (administrator) useful for running background tasks.
API documentation can be found at https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/beta-overview
Documentation and install instructions
https://dcblog.dev/docs/laravel-microsoft-graph
Change log
Please see the changelog for more information on what has changed recently.
Contributing
Contributions are welcome and will be fully credited.
Contributions are accepted via Pull Requests on Github.
Pull Requests
-
Document any change in behaviour - Make sure the
readme.mdand any other relevant documentation are kept up-to-date. -
Consider our release cycle - We try to follow SemVer v2.0.0. Randomly breaking public APIs is not an option.
-
One pull request per feature - If you want to do more than one thing, send multiple pull requests.
Security
If you discover any security related issues, please email dave@dcblog.dev email instead of using the issue tracker.
License
license. Please see the license file for more information.