Microsoft 365

Refund Rules

Microsoft 365 generally follows a strict no-refund policy for subscription services once the commitment period begins. However, they offer: (1) 30-day money-back guarantee for new subscriptions, (2) Pro-rated refunds for mid-cycle downgrades in seat count, (3) Refunds for billing errors or unauthorized charges when disputed within 60 days, (4) Annual commitment customers can cancel but forfeit remaining months unless for cause (service failure). Enterprise Agreement customers have more flexible terms negotiated in their contract.

Credit Policies

Microsoft offers Service Level Agreement (SLA) credits: (1) 99.9% uptime SLA with 25% monthly credit for 99.0-99.9% availability, 50% for 95.0-99.0%, 100% for <95%, (2) Credits must be claimed within 60 days of incident, (3) Maximum monthly credit of 100% of monthly service fees, (4) No automatic credits - customer must submit claims through Service Request, (5) Planned maintenance excluded from SLA calculations, (6) Some enterprise customers negotiate additional credits for prolonged outages.

Contractual Terms

Key cost optimization terms: (1) Auto-renewal enabled by default with same term length, can be disabled 30 days before renewal, (2) 30-day notice required for cancellation of monthly plans, annual plans typically cannot be cancelled mid-term, (3) Price increases limited to once per year with 60-day advance notice for commercial customers, (4) Seat count changes take effect immediately for additions, downgrades effective at next billing cycle, (5) Enterprise Agreement customers have 3-year commitment with annual true-ups and more flexible terms, (6) Academic and non-profit pricing requires verification and annual recertification.

Integration Complexity

Technical Notes

Microsoft Graph API is well-documented and mature. Key considerations: (1) Authentication via Azure AD OAuth 2.0 requiring admin consent for organization-wide permissions, (2) Rate limits of 10,000 requests per 10 minutes per application per tenant, (3) Some premium features like signInActivity require Azure AD P1/P2 licenses, (4) Pagination required for large datasets using @odata.nextLink, (5) Permissions are granular - User.Read.All, Reports.Read.All, AuditLog.Read.All needed for full utilization analysis, (6) Usage reports API has 48-hour data latency, (7) Tenant ID required for multi-tenant applications.