IT & MICROSOFT 365 · MICROSOFT 365 ADMINISTRATION

Microsoft 365 Administration in Dresden. A Clear Working Environment.

Tenant setup, Exchange, Teams, SharePoint, Entra ID, Intune and licence management. We build Microsoft 365 environments to scale rather than create problems tomorrow.

Three people collaborate in front of a shared display in a meeting room.

Typical Starting Points

  1. Permissions have accumulated over time, and nobody knows who has access to what.
  2. Licences are expensive, but nobody checks whether they are being used.
  3. Backups, compliance and endpoint protection are missing or fragmented.
  4. Migration to Microsoft 365 started but stalled halfway through.

The Focus of Microsoft 365 Administration

Microsoft 365 administration concerns the tenant and digital working environment: identities, communication, collaboration, devices and policies. IT infrastructure addresses networks and servers as the operational foundation. The connections between the two are considered together.

The Service in Detail

Tenant & Identities

Tenant Architecture
A clean setup or rearchitecture: naming, licence tiers, Conditional Access and tagging.
Entra ID / Azure AD
Conditional Access, MFA, PIM, group strategy and B2B/B2C scenarios.

Communication & Collaboration

Exchange Online
Mail flow, mailbox migration, shared mailboxes, anti-spam, DMARC, DKIM and SPF.
Teams & SharePoint
Governance, site architecture, external sharing, Microsoft 365 Groups and sensitivity labels.

Devices & Data Protection

Intune & Endpoints
Device management for Windows, macOS, iOS and Android. Autopilot, compliance and app protection.
Backup & Compliance
Third-party Microsoft 365 backup, retention policies, eDiscovery and audit logs.

The Approach

  1. Assessment

    Tenant audit: licences, permissions, security score and compliance status.

  2. Roadmap

    Prioritised actions — what reduces risk immediately and what adds long-term value.

  3. Implementation

    Step-by-step hardening, migrations and policy rollouts with pilot groups.

  4. Documentation

    Architecture diagrams, runbooks and emergency processes — ready for audits and handover.

  5. Operations

    Monthly health checks, patch strategy, licence optimisation and on-call support for incidents.

The Service Within Its Competence Area

The competence hub explains the wider connections. Microsoft 365 Administration focuses here on the specific task.

IT & Microsoft 365 →

Microsoft 365 Migration

Selected Project / Portfolio

The existing migration project moved an on-premises Exchange environment to Microsoft 365. Teams adoption, Azure AD integration and the user structure formed part of that work.

View the Selected Project in the Portfolio →

Technical and Practical Foundations

  • Microsoft 365
  • Exchange Online
  • Teams
  • SharePoint Online
  • Entra ID
  • Intune
  • Defender
  • PowerShell

How the Elements Connect

  1. Users
  2. Permissions
  3. Collaboration
  4. Administration

Project, Handover and Ongoing Work

A Defined Project

In a defined project, we review tenant structure, access and ongoing administration of your working environment and agree the scope around the existing environment.

After Implementation

For the continuing work on Microsoft 365 Administration, the existing process includes: Monthly health checks, patch strategy, licence optimisation and on-call support for incidents.

Scott Nowak, your personal contact.
Scott NowakMicrosoft 365 Administration

Scott Nowak. Direct Collaboration on Microsoft 365 Administration.

I am Scott Nowak, your direct contact for Microsoft 365 Administration. We discuss tenant structure, access and ongoing administration of your working environment and connect the requirements with their implementation.

More About Scott →

Questions About Microsoft 365 Administration

Which Microsoft 365 licence suits our SME?

For Dresden SMEs with 10–100 employees, Microsoft 365 Business Premium can be a cost-effective option: Office apps, Entra ID, Intune, Defender for Business and Conditional Access in one package. For larger environments, we assess E3/E5 or targeted add-ons.

Should we migrate all at once or in stages?

We recommend a pilot with 5–10 users from different departments, followed by migration waves at intervals of 2–4 weeks. This helps identify issues early, before they affect the whole company.

Does Microsoft 365 alone provide sufficient backup?

No. Microsoft replicates your data, but this does not cover accidental deletion or ransomware attacks. We configure third-party backup, such as Veeam or AvePoint, with clear retention rules.

How can we reduce licence costs?

A licence analysis typically identifies savings of 10–25% through unused licences, unsuitable licence tiers and duplicate add-ons. We offer the analysis as a one-off service or as part of Microsoft 365 maintenance.

Do you also manage ongoing operations?

Yes. We offer managed service packages with monthly health checks, tickets, patch strategy and an emergency contact number. These scale from 4 hours to 20+ hours per month.

What needs to change in your Microsoft 365 environment?

Describe tenant structure, access and ongoing administration of your working environment. The existing project brief lets you share your starting point and supporting materials.

Would you like to speak first? →

Response time: < 48 h
Project start: typically 2–4 weeks

Within 48 hours on business days.