ITCore
Cloud infrastructure

Microsoft 365 and cloud infrastructure

Microsoft 365, Entra ID, Exchange Online, Intune, Azure, Google Workspace. Migrations, security configuration, license management.

When clients come to us

When clients come to us

Three common scenarios and how we solve them.

Mail on your own server — nobody admins it, spam and phishing in waves

We migrate to Exchange Online preserving addresses, roll out DMARC/SPF/DKIM, anti-phishing, MFA, quarantine.

Users create accounts themselves, weak passwords, nobody revokes access at offboarding

Centralize in Entra ID with MFA, SSO, Conditional Access, automatic deprovisioning on exit, role-based licensing.

Microsoft 365 licenses are bought ad-hoc, someone on E5, someone without Office — the bill grows

License audit, persona-based plan (Frontline/Business/E3/E5), move to the right tier, 20-40% budget savings.

What is included

Clear boundaries: what is covered by the retainer and what is a separate project.

Included in the service

  • Migration from GSuite / legacy Exchange / IMAP provider to Microsoft 365
  • Exchange Online / Exchange on-prem / Hybrid configuration
  • Teams: deployment, channels, Teams Phone System with real numbers
  • SharePoint Online and OneDrive for Business: libraries, permissions, DLP
  • Microsoft Intune: device management, policies, conditional access
  • Mail security: SPF, DKIM, DMARC, Defender for Office 365, anti-spam
  • Training the client-side administrator — so you are not locked into the contractor

Not included / separate project

  • Custom Power Platform / Power Apps development (only configuration and automations)
  • Legal consulting on cloud data export
  • Migration from exotic on-premise mail systems without IMAP/MAPI — possible, but as a project
SLA

What is actually included in the contract

When we sign — both sides know exactly what you pay for and what you get. These are the four planes the SLA is built on.

Coverage hours

  • Business hours: Mon–Fri 08:00–20:00, L1 with guaranteed response
  • On-call evenings and weekends on request
  • 24/7 for critical services: mail, 1C, UNA, POS, website, VPN
  • Scheduled night windows for planned work without downtime

Contact channels

  • Single ticket portal with history and SLA timers
  • Hotline phone for P1 incidents
  • Email and Telegram bot for routine tasks
  • User chat with our on-duty engineer during business hours

Priorities and response

  • P1 (critical, service is down): response in 15 minutes, 24/7
  • P2 (severe impact): response within 1 hour in business hours
  • P3 (single-user issue): response within 4 hours
  • P4 (planned work, improvement): scheduled for the coming week

Contract scope of work

  • Planned maintenance: updates, backups, monitoring, patch management
  • Incident management: diagnostics, recovery, postmortems
  • Small projects within the retainer: up to N hours per month
  • Large projects (migrations, new equipment) — separately scoped

Technologies and tools

What we work with in this area.

Microsoft 365
Exchange Online
Exchange on-prem
Teams
SharePoint
OneDrive
Intune
Defender for Office 365
Azure AD Connect

How we onboard a new client

1

Kickoff and brief

30–60 minutes online or in the office: we discuss the business, the key systems, and the incidents that hurt last year. We sign an NDA.

2

Technical audit and risk map

1–2 weeks. Equipment inventory, checks on servers, network, backups, security, 1C/UNA, licensing. The outcome is a report with a risk map and priorities.

3

Work plan and contract

We build the plan: what gets fixed right away (P1 risks), what in the first month, what in the first quarter. We lock the SLA, hours, channels, price. We sign the contract.

4

Onboarding and infrastructure handover

We take over the access via a secure password manager, deploy our monitoring, plug in the ticket system, train the employees. The previous admin (if any) hands off by the playbook.

5

Ongoing operations and reporting

Monthly report: incidents, planned work, new risks, recommendations. Quarterly review with the CEO/CFO: strategy, budgets, major changes.

Case study

Mail domain migration from on-premise Exchange 2013 to Microsoft 365, 180 users

Distribution company, Moldova

Задача

Exchange 2013 out of support, poor spam filters, overloaded mailboxes, archives on local PST.

Решение

Planned hybrid migration, moved all mailboxes and archives, configured Entra ID MFA and Conditional Access, replaced PST with online archives.

  • 0 minutesMail downtime during migration
  • +99.5%Mail deliverability
  • Matched to actual rolesE3 licensing
  • Microsoft 365
  • Exchange Online
  • Entra ID
  • Intune
  • Microsoft Defender for Office 365

Frequently asked questions about this service

Do you migrate between Google Workspace and Microsoft 365?

Yes, both directions. Preserve mail, calendars, contacts, Drive/OneDrive files, shared drives. A typical 50-200 user migration is 2-4 weeks.

Where is data stored — EU or outside?

Microsoft 365 defaults to EU (Netherlands, Ireland). For Google Workspace we pick EU regions. Matches GDPR requirements for sensitive data.

Can we manage work laptops through Intune from Microsoft 365?

Yes, it's our strength (see "Workstations"). Intune + Autopilot + security policies — new laptops are production-ready from the first login.

How much does a Microsoft 365 Business Standard license cost in Moldova?

Depends on channel and volume. Typically €10-13/user/month via reseller. We often save clients 20-40% by moving to the right tier and disabling unused add-ons.

How do we move to business email on our own domain?

We verify your domain in Microsoft 365, create the mailboxes and match licenses to roles so you don't pay for extras nobody uses. Then we migrate the old mail and switch the MX records in an agreed window. SPF, DKIM and DMARC go in from day one: without them, mail from the new address lands in spam more often and it's easier to send phishing in your company's name. Staff keep their existing addresses.

What happens to our old email and archives?

We move mail, calendars and contacts from your old Exchange server, Google Workspace or any IMAP provider. Local PST archives can be uploaded into the new mailboxes, so they stop living on individual PCs. The old server stays on until we've confirmed everything made it across. If you run an unusual mail system with no IMAP or MAPI support, migration is still possible, but we scope it as a separate project.

Exchange Online or Google Workspace for company email?

We work with both, so the choice comes down to how your people work. If they live in Outlook and Excel, you have Active Directory, and you want Teams or laptop management through Intune, Exchange Online in Microsoft 365 is the natural fit. If the team works in the browser with Gmail and Google Docs, Google Workspace is more comfortable. SPF, DKIM and DMARC protection is set up the same way either way.

Let us talk about your IT

The first meeting — 30 minutes, free, no strings attached. We will tell you whether we are the right fit and what is worth doing first.

Microsoft 365 and cloud infrastructure | ITCore