Microsoft 365 Partner · Selection & arades
The choice of the Microsoft 365 partner decides the success of your cloud initiative more than the license choice itself. This page first shows the six criteria against which every Microsoft 365 partner (or Office 365 partner) should be measured — and then positions where arades GmbH, as a mid-market-focused boutique partner with 17+ years of Microsoft 365 practice, is strong.
Selection criteria
Six levers that in our experience decide between smooth introductions and expensive learning loops. When comparing multiple Microsoft 365 partners — ask exactly these points. Vendor-neutral wording, so you can also classify competitor answers.
01 · Practice depth & platform history
Microsoft 365 emerged in 2020 from Office 365 — which itself has been in production since 2011 and developed from Office 365 BPOS (2008). Anyone who has worked with the earlier versions, with hybrid setups, and with on-premises Exchange/SharePoint migrations knows one and a half decades of platform history. That history later shows in architecture decisions that still hold up five years after go-live.
02 · Software development depth
Standard Microsoft 365 configuration is rarely enough for robust setups. A partner with real software development depth delivers SharePoint Framework extensions, Teams apps, Microsoft Graph integrations, and Power Platform extensions and can also develop outside the Microsoft stack when needed. Pure out-of-the-box configurators hit walls quickly when requirements go beyond M365 built-ins.
03 · Industry understanding
Industry experience shortens the discovery phase by weeks. A partner who knows member communication in associations, course management at education providers, or shift communication in industry from three running projects delivers qualified detail questions immediately instead of generic best-practice slides.
04 · Process maturity & delivery methodology
Consistent implementation quality comes from documented delivery processes, not individual talent. A partner with established process methodology can describe architecture review procedures, sprint structures, hypercare handovers, and Application Care transitions clearly — and delivers comparably from project to project. Ask for the delivery handbook or the quality management system.
05 · Pre-built modules & add-ons
A partner who operates its own ready add-ons on Microsoft 365 (Teams app templates, SharePoint solutions, Power Platform building blocks, adoption helpers) saves you configuration weeks and delivers proven architecture instead of greenfield risk. Look for concrete products with customers in live operation — not hypothetical "we could also build" lists.
06 · Partner size & personality
With large Microsoft generalists you negotiate in sales with senior architects and often get a junior or offshore team in delivery. With smaller boutique partners the same people are active pre- and post-contract, escalations reach management quickly, and responsibility doesn't get lost between hierarchy layers. The right size depends on the project — personal accessibility is more decisive than absolute firm size.
These six points are market standard for good selection diligence. In the next section we show where arades GmbH delivers solidly against each point.
arades as your Microsoft 365 partner
arades GmbH is not the largest Microsoft 365 partner in Germany and doesn't want to be. We specialize in European mid-market companies with 50–500 employees and deliver with the same team from the first idea to the fifth year of operation. Here's how that looks against the six criteria.
arades has worked on Microsoft cloud apps since 2008 — through Office 365 BPOS, classic Office 365, hybrid setups, SharePoint Online, the Teams introduction, and today's Microsoft 365 plus Copilot world. This platform depth makes the difference for architecture decisions that still need to hold up five years after go-live.
We don't just configure, we develop extensions: SharePoint Framework web parts and extensions, Teams apps with tab/bot/message-extension patterns, Microsoft Graph integrations for custom workflows, Azure Functions for asynchronous processing. Cross-stack development as needed in our Independent Engineering area.
Specialization on education providers (faculty/student licensing, Teams classrooms), professional associations and foreign trade chambers (member communication, SharePoint member portals), IT service providers, and mid-market industry & manufacturing (shift communication, frontline worker setups, Intune device management). Own solutions on Microsoft 365 as evidence of end-to-end platform competence.
Structured delivery methodology following the CMMI maturity model: documented architecture review procedures, defined sprint structures in the introduction phase, standardized hypercare handovers, and clear transitions into Application Care. The result is repeatable quality — independent of individual daily form.
We run several of our own solutions with customers in production: Education Institutes app, Associations & Chambers, and the License Cost Calculator. That clearly reduces time-to-value for the matching industry scenarios.
arades is intentionally small — no corporate apparatus, no account-manager-to-delivery wall. You speak in the sales process with the same architects who will lead your introduction. Management directly reachable. Application Care at a predictable monthly flat fee. Strategy workshop and architecture review at fixed prices — no surprises from time sheets.
Differentiation
Three points that have proven over more than a decade of Office 365/Microsoft 365 advisory to be K.O. criteria for mid-market initiatives:
Introduction scenarios
Three anonymized constellations from current introduction practice. Real projects with real tenant sizes and real duration — so you can match our delivery profile against your situation.
SMB · 10–50 employees
Fast introduction as a pure cloud setup: tenant setup, migration from IMAP/Exchange On-Prem, Teams adoption, Microsoft 365 Business Premium for all. Introduction duration 3–6 weeks, low customization share. Followed by Application Care at a fixed monthly price.
View →
Mid-market · 50–500 employees
Microsoft 365 E3 or E5 for the majority, Frontline F3 for production/warehouse. Full workload introduction: Teams (incl. telephony), SharePoint migration, Intune device management, Defender suite, Copilot piloting. Duration 4–8 months, staggered rollout waves.
View →
Industry specific
80 employees plus 1,200 course participants per year. Microsoft 365 A1/A3 tariffs for faculty and student, Teams for class rooms, SharePoint for learning content, integration with our Education Institutes app. Introduction duration 4–6 months, followed by Application Care.
View →
Frequently asked questions
Six criteria matter: practice depth and platform history (ideally with Office 365 BPOS and Office 2010 experience), software development depth beyond pure configuration (SharePoint Framework, Teams apps, Power Platform), industry understanding with concrete references, documented delivery methodology for repeatable quality, own solutions and add-ons, plus the right partner size — personal accessibility and the same people before and after contract signing are often more decisive than firm size.
Both terms mean the same today — Microsoft renamed the brand from "Office 365" to "Microsoft 365" in 2020 and expanded the scope with device management (Intune), security building blocks, and Copilot. Anyone saying "Office 365 partner" usually means a Microsoft 365 partner. arades has been working on this platform since the Office 365 BPOS days (2008) — that is 17+ years in a world many market peers only got to know with Microsoft 365.
The entry is free: 30-minute discovery conversation without obligation. Solid advisory formats from €2,400 net (strategy workshop, one day) and €8,400–€14,000 net (architecture review, 3–5 days). Mid-market introduction projects typically run €25,000 to €120,000 net, depending on tenant size and migration complexity. Licenses via Microsoft CSP at list price plus triennial and volume rebates. Application Care after go-live from about €1,200 net per month.
Three steps: (1) Discovery conversation to clarify tenant state, license estate, current contracts, and adoption level. (2) Architecture review as an objective baseline — even when the existing setup comes from another partner. (3) License takeover via partner-of-record switch in the Microsoft Admin Center. This is a documented Microsoft process and incurs no penalty fee.
Via the public Microsoft Partner Center (appsource.microsoft.com), Microsoft partners can be filtered by region, language, and solution area. More important than the filter list, though, is the discovery meeting: 30 minutes of conversation often show more than a data sheet. arades GmbH has been listed in the Microsoft ecosystem since 2007 and specializes in the European mid-market (50–500 employees), based in Offenbach am Main with on-site workshop capacity across the DACH region.
Further reading
Six follow-on topics in the order they typically become relevant after the partner choice.
Strategy workshop, license audit, Copilot readiness, security baseline — Microsoft 365 advisory for mid-market companies.
Business Basic/Standard/Premium, E1/E3/E5, Frontline F1/F3, Copilot — license models, NCE mechanics, triennial discounts.
Tenant setup, mailbox and SharePoint migration, Teams adoption, security baseline — the introduction in four phases.
Teams, SharePoint, Outlook, Copilot — role-specific curricula for end users, power users, and admins.
Engineering overview: Teams, SharePoint, Exchange, OneDrive, Intune, Defender — the Microsoft 365 platform explained technically.
Calculate yourself what your Microsoft 365 licenses would cost with the right plan mix — including Copilot.
30 min · free · no obligation
Tell us about your plan. We listen, classify, and give an honest assessment — whether Microsoft 365 fits, which tariff mix makes sense, and what investment range is realistic. If another partner or another product fits better, we say so.
