- Can I use fungio/outlook-calendar-bundle in a Laravel application?
- Not as a supported Composer dependency. The package is a Symfony bundle built around a Bundle class, DependencyInjection extension, and YAML service definitions that Laravel's container has no concept of. You could strip-mine the underlying HTTP client and event-mapping logic, but the bundle scaffolding will not 'just work' in Laravel.
- Does this Outlook calendar package support Laravel 10, 11, or 12?
- There is no Laravel support to speak of. The bundle is Symfony 3-era and likely pins symfony/framework-bundle and symfony/dependency-injection to ^3.0, while modern Laravel 10/11/12 require Symfony 6.4 or 7.x components. Those constraints are mutually unsatisfiable, so Composer resolution will usually fail.
- What PHP version does fungio/outlook-calendar-bundle require?
- Expect a PHP 5.5–7.0 era codebase with no return types, typed properties, or strict_types declarations. Dropping it into a PHP 8.2+ Laravel app invites deprecation noise and possible hard failures where removed behaviours are touched. Check the actual composer.json before committing, but plan for modernization work.
- Does this bundle use Microsoft Graph or the legacy Outlook REST API?
- The blurb says Microsoft Graph, but the technical assessment finds the integration targets the legacy Outlook REST endpoints such as outlook.office.com/api/v2.0/me/events. Microsoft has steered new work to Graph for years and no longer recommends those Outlook endpoints. Starting a new build on this code puts you on a deprecation clock.
- How do I install fungio/outlook-calendar-bundle?
- In a Symfony app you would require it via Composer and register the bundle in AppKernel, then wire configuration through the bundle's extension. In Laravel there is no equivalent registration path, and forcing installation with --ignore-platform-reqs only defers the breakage to runtime. Treat it as reference code rather than an installable Laravel dependency.
- Is fungio/outlook-calendar-bundle actively maintained?
- The assessment flags critical abandonment risk: about 5 stars, 0 dependents, and a composite score of 0.235. There is effectively no user base, issue triage, or security-patch stream. Any fork you take on becomes a permanent fork you own.
- What should I use instead for Outlook calendar integration in Laravel?
- Build against Microsoft Graph directly, using the official Microsoft Graph SDK or a thin Guzzle client wrapped in a Laravel service provider. Choose delegated per-user OAuth or app-only daemon permissions with Calendars.ReadWrite based on your tenant model. This avoids importing Symfony 3 bundle scaffolding and keeps you on supported APIs.
- Can this package handle two-way calendar sync and event CRUD?
- Scope depends on what you need: one-way read/sync is materially lower risk than full create/update/delete, invites, and RSVP handling. The legacy Outlook REST surface can do CRUD, but change notifications and near-real-time subscriptions are Graph-only territory in practice. Polling is the fallback if you port the code.
- Does it support OAuth 2.0 and multi-tenant Azure AD consent?
- The bundle era typically relies on Symfony's hwi/oauth-bundle for OAuth flows, not a Laravel-native auth integration. Multi-tenant scenarios need an Azure AD app registration, admin consent flow, and Graph application permissions, which are outside this bundle's design. You would rebuild that auth layer for Laravel regardless.
- How hard is it to port this Symfony bundle to Laravel?
- Porting is a strip-mine, not a dependency swap. The reusable part is thin: a Guzzle client that authenticates against Microsoft endpoints and maps JSON into event entities. You would rewrite configuration, service wiring, and auth for Laravel, while accepting high API lifecycle and abandonment risk.