Most organisations that adopt Microsoft 365 use about 20% of what they're paying for. They set up email, maybe install Teams for video calls, and leave everything else untouched. The result is that they're paying a per-user monthly fee for capabilities sitting dormant — while also paying separately for Dropbox, WhatsApp Business, and whatever else fills the gaps that M365 could have handled.
What M365 Actually Includes
Microsoft 365 is a suite, not just email. The core components:
- Exchange Online: business email with your domain (@yourcompany.com), 50GB per mailbox, calendars and shared calendars
- Microsoft Teams: chat, video calls, file sharing, and channel-based collaboration — the WhatsApp replacement for internal communication
- SharePoint: team document libraries, intranet pages, and shared storage — the Dropbox replacement for team files
- OneDrive: personal cloud storage synced to each user's device — 1TB per user on most plans
- Microsoft Forms: survey and form builder — useful for internal surveys, leave requests, feedback forms
- Microsoft Planner: basic task and project management, integrated with Teams
- Office apps: Word, Excel, PowerPoint — either web-only or desktop installs depending on the plan
Higher tiers add Defender (endpoint security), Intune (device management), Azure AD Premium (advanced identity features), and Purview (compliance tools). For most teams under 50 people, you won't need these — but they matter once you hit a certain scale or operate in regulated industries.
Licensing Tiers in India
Microsoft's India pricing (approximate, as of early 2026):
- Microsoft 365 Business Basic: approximately ₹125–150 per user per month. Includes Exchange, Teams, SharePoint, OneDrive, and web versions of Office apps. No desktop Office installs.
- Microsoft 365 Business Standard: approximately ₹660–700 per user per month. Adds desktop Office apps (Word, Excel, PowerPoint, Outlook installed on up to 5 devices), plus Bookings, MileIQ, and Webinars in Teams.
- Microsoft 365 Business Premium: approximately ₹1,050–1,100 per user per month. Adds Defender for Business, Intune device management, Azure AD Premium P1, and Azure Information Protection.
For most small teams in India, Business Basic is sufficient for the first year. You get email, Teams, SharePoint, and OneDrive — which is the core stack most teams need. Upgrade to Standard when your team regularly needs to work in Office apps offline or needs desktop installs as part of a managed device policy.
What We Actually Use With Most Clients
In practice, the stack that delivers real value for a team of 5–50 people:
- Exchange Online for email: every person gets a professional @yourdomain.com address. Shared mailboxes (like info@, accounts@, support@) can be set up without additional licenses — any number of people can access them.
- Teams for internal communication: replaces WhatsApp groups for work conversation. Channels organised by department or project. Files shared in Teams are stored in SharePoint automatically.
- SharePoint for document management: company documents, policies, templates, and shared resources live here. Organised by department. OneDrive sync means it appears as a mapped drive on Windows desktops.
- OneDrive for personal work files: each person's work files backed up to the cloud automatically. When a laptop dies or someone leaves, the files don't go with them.
This combination replaces separate email hosting, Dropbox or Google Drive, and WhatsApp as the default internal communication tool — typically saving ₹3,000–8,000 per month for a 20-person team when you account for what they were paying separately.
What We Skip for Small Teams
Unless there's a specific requirement, we generally don't configure these for teams under 50:
- Azure AD Premium: the free tier of Azure AD (included with all M365 plans) handles authentication, MFA, and group management adequately for most small teams. Premium adds Conditional Access and Identity Protection — valuable, but complex to configure correctly and often overkill below 50 users.
- Microsoft Defender for Business: useful, but requires device enrolment. If you're not managing devices centrally (most small teams aren't), the value is limited.
- Purview compliance tools: relevant for heavily regulated industries (finance, healthcare, legal). For most businesses, the default data handling in M365 is compliant with what they need.
The Configuration That Actually Matters
Setting up accounts is the easy part. What most M365 deployments skip:
- Multi-factor authentication on every account: not optional. MFA stops the vast majority of credential-based attacks. It takes 10 minutes to enable, per user, and should be done before anyone sends their first work email from the new account.
- Email routing configuration: SPF, DKIM, and DMARC records in DNS. Without these, your emails are more likely to land in spam, and anyone can spoof your domain.
- Shared mailbox setup: info@, support@, accounts@ should be shared mailboxes, not individual accounts. Multiple people can monitor and respond without everyone needing their own license for those addresses.
- SharePoint folder structure: get this right at setup. Retrofitting a logical folder structure onto years of accumulated files is genuinely painful. Decide on the structure — by department, by client, by year — before people start saving files.
- Retention and backup policy: M365 includes basic retention (deleted items kept for 30–93 days depending on settings), but it's not a substitute for backup. For critical data, a third-party backup tool (Veeam, Acronis, or similar) is worth adding.
The M365 Mistake We See Most Often
Organisations buy the licenses, someone sets up the email accounts, everyone gets a login — and then nothing else is configured. Teams is installed but nobody uses it because "we already have WhatsApp." SharePoint exists but nobody knows the URL. OneDrive is enabled but nobody has synced it to their desktops. The organisation is paying for M365 Business Standard but effectively using it as expensive email hosting.
This is extremely common. The reason is that Microsoft makes provisioning accounts easy — you can set up 20 users in an afternoon. But provisioning isn't configuration. Configuration is the harder part: setting policies, organising SharePoint, training people on Teams, migrating email from the old provider without losing history, and making sure that by week two everyone is actually using the new tools.
What a Proper M365 Setup Actually Takes
A proper M365 setup for a team of 10–30 people typically takes 2–4 days of focused work:
- Day 1: DNS configuration, email routing setup, account provisioning, MFA enforcement
- Day 2: SharePoint structure, Teams channels, shared mailbox configuration, OneDrive desktop sync
- Day 3: Email migration from old provider, testing, troubleshooting
- Day 4: Team training — how to use Teams effectively, how SharePoint is organised, how to access email on mobile
Skip the training and you'll find the team reverts to old habits within two weeks. The tools are only valuable if people actually use them — which means they need to understand what they're for and why the new approach is better than what they were doing before.
