Back to Articles

WPA3-Enterprise and 802.1X Wi-Fi Authentication - A UK Guide to Meraki and Entra ID

WPA3-Enterprise and 802.1X Wi-Fi Authentication - A UK Guide to Meraki and Entra ID

If your office Wi-Fi still runs on a single shared password that has not changed since the last office move, WPA3-Enterprise and 802.1X Wi-Fi authentication is the upgrade that closes the gap. Instead of one pre-shared key known to every current and former member of staff, each person and each company device proves who it is before it joins the network. On a Cisco Meraki estate tied to Microsoft Entra ID, that proof can come from the same identity and device records you already manage in Microsoft 365.

This how-to guide covers what 802.1X actually does, how WPA3-Enterprise differs from WPA2 and WPA3-Personal, the three realistic ways to connect Meraki access points to Entra ID, what a rollout costs a UK small or mid-sized business, and the step-by-step order we use to move an office from a shared key to certificate-based Wi-Fi without a Monday morning of locked-out laptops. It is written for office managers, IT leads and directors who own the decision rather than for network engineers, although the technical detail is there when you need it.

What is 802.1X Wi-Fi authentication? Definition and context

802.1X is an IEEE standard for port-based network access control. On a wireless network it means the access point does not let a device pass ordinary traffic until an authentication server has said yes. The conversation has three parties: the supplicant (the laptop or phone), the authenticator (the Meraki access point) and the authentication server (a RADIUS service). The access point simply relays an Extensible Authentication Protocol (EAP) exchange between the device and the RADIUS server, then opens the door — and optionally assigns a VLAN or group policy — based on the answer.

“WPA2-Enterprise” and “WPA3-Enterprise” are the Wi-Fi Alliance certification names for wireless networks that use 802.1X rather than a pre-shared key. The “Personal” variants (WPA2-PSK and WPA3-SAE) use a password. WPA3-Enterprise keeps the 802.1X model but mandates Protected Management Frames, tightens the allowed cipher suites and, in its optional 192-bit mode, enforces stronger cryptography designed for higher-assurance environments. On 6 GHz Wi-Fi 6E and Wi-Fi 7 bands, WPA3 is compulsory — legacy WPA2 is not permitted there at all — so any business buying new access points is already on a path towards it.

The EAP method chosen inside 802.1X matters as much as the WPA version. EAP-TLS uses a digital certificate on the device and is the method Microsoft, the NCSC and most vendors now recommend. PEAP-MSCHAPv2 uses a username and password inside a TLS tunnel; it is widespread but increasingly fragile, because Windows 11 Credential Guard blocks the saved-credential behaviour it relies on, and because a misconfigured client can be tricked into handing its password hash to a rogue access point. EAP-TTLS/PAP is a third option some cloud RADIUS providers use to check passwords directly against Entra ID. For a Microsoft 365 business, the practical end goal is almost always EAP-TLS with certificates issued through Intune.

Pro Tip

Keep a separate WPA3-Personal or captive-portal SSID for guests and for the handful of devices that cannot do 802.1X (some printers, meeting-room panels and IoT sensors). Put that SSID on its own VLAN with internet-only access. Trying to force every device onto 802.1X on day one is the most common reason projects stall.

Wi-Fi authentication readiness scoring — where most UK offices sit today

Before choosing a RADIUS service, it helps to be honest about the starting point. The score cards below reflect the pattern we see when auditing Microsoft 365 offices of 15 to 250 staff. They are not national statistics; they are the recurring conditions that decide whether a rollout takes two weeks or two months.

Where most offices fall short
Shared Wi-Fi key unchanged for over a yearHigh risk
Former staff still know the staff SSID passwordHigh risk
Guests and staff on the same flat networkHigh risk
No record of which devices are on Wi-FiMedium risk
Printers and IoT sharing the staff VLANMedium risk
Foundations that speed up a rollout
Laptops enrolled in IntuneReady
Entra ID groups that reflect real rolesReady
Meraki MR firmware on a current releaseCheck
Mobile phones enrolled or managed via app protectionCheck
Documented VLAN planCheck
Blockers that need a decision first
Personal devices used for core workDecide policy
Unsupported Windows or macOS versionsUpgrade
On-premises NPS server with no ownerRetire or adopt
Access points older than Wi-Fi 5 Wave 2Refresh plan

The first column is the business case. A shared key is, in effect, a credential that never expires and that you cannot revoke for one person. When somebody leaves, the only safe response is to change the key for everyone and re-enter it on every device — which is why most offices never do it. 802.1X turns Wi-Fi access into something that follows the identity: disable the account or retire the device in Intune and the Wi-Fi access goes with it. That links neatly into the joiner-mover-leaver process covered in our guide to Microsoft 365 offboarding for leavers.

802.1X Wi-Fi by the numbers

These figures frame the scale of a typical project for a single-site UK office. They are planning figures drawn from our own deployments and vendor documentation, not guarantees — your estate will differ.

3
Realistic RADIUS architectures for a Meraki and Entra ID office
2–6 wks
Typical elapsed time from audit to shared key retired
£0
Extra Meraki MR licence cost to enable 802.1X on existing SSIDs
6 GHz
Band where WPA3 is mandatory and WPA2 is not allowed

The third card surprises people. 802.1X, WPA3 and RADIUS-assigned VLANs and group policies are standard features of every Meraki MR licence tier; you do not buy an “enterprise Wi-Fi” upgrade from Cisco. The costs sit elsewhere — in the RADIUS service, in certificate issuance, and in the configuration time to get devices ready — and they are covered in the cost table later in this guide.

How WPA3-Enterprise compares to a shared Wi-Fi password

Many directors ask whether simply moving from WPA2-Personal to WPA3-Personal is enough. WPA3-Personal is a real improvement — its Simultaneous Authentication of Equals (SAE) handshake resists the offline password-guessing attacks that make weak WPA2 keys crackable — but it is still one secret shared by everyone. The comparison below sets out the practical difference for an office.

WPA2 / WPA3-Personal

One shared key for all staff

Revoking one leaver Change key for everyone
Who is connected Device MAC only
Per-role VLANs One per SSID
Key exposure Written down, shared, reused
Cyber Essentials story Weak on access control
Setup effort Minutes
Ongoing admin Low until a key change

WPA3-Enterprise with 802.1X

Per-user or per-device identity

Revoking one leaver Disable the account or device
Who is connected Named user and device
Per-role VLANs Assigned dynamically by RADIUS
Key exposure No shared secret to leak
Cyber Essentials story Clear, auditable control
Setup effort Days to weeks
Ongoing admin Low once automated via Intune

There is a middle ground worth knowing about: Meraki’s identity pre-shared keys (iPSK), which give each user or device group its own key on a single SSID. iPSK is useful for IoT and for devices that cannot do 802.1X, but it still relies on keys that people can share, so treat it as a complement rather than a replacement for 802.1X on staff devices.

Which EAP methods UK offices actually run

The bar chart shows the share of Meraki staff SSIDs using each authentication approach across the offices we audited before migration. It is a snapshot of our own client base rather than a market survey, but it illustrates how many networks are still on shared keys and how few have reached certificate-based EAP-TLS.

WPA2-Personal (shared key)
58%
WPA3-Personal / transition
11%
Meraki iPSK
6%
PEAP-MSCHAPv2 via NPS
15%
EAP-TTLS to cloud RADIUS
4%
EAP-TLS with certificates
6%

The PEAP-MSCHAPv2 slice is the one to watch. Those networks already “do 802.1X”, so they rarely get flagged in an audit, yet they depend on an ageing Windows Server running Network Policy Server, on password-based EAP that Credential Guard now disrupts, and frequently on clients configured not to validate the server certificate. If your NPS box is still on Windows Server 2016, our guide to Windows Server 2016 end of support explains why that platform has a deadline attached.

Where the effort goes in an 802.1X rollout

The access point configuration is the smallest part of the job. The donut shows the approximate share of project hours that goes into getting devices ready — certificate profiles, Wi-Fi profiles, testing and exceptions — on a typical 60-person office.

64%
Of project effort spent on device readiness, not on the Meraki dashboard

The remaining time splits roughly between RADIUS and certificate authority setup, Meraki SSID and group policy configuration, and cutover support. The lesson is that Intune maturity drives the timeline. An office where every laptop is Entra-joined and Intune-managed can push a trusted root certificate, a SCEP or PKCS certificate profile and a Wi-Fi profile in an afternoon. An office with a mix of unmanaged Macs, personal phones and laptops nobody has logged into for months needs that tidying first.

How to roll out 802.1X on Meraki with Entra ID — step by step

The timeline below is the sequence we follow. Each step has a clear exit condition, and the shared key stays live until the final step so nobody is cut off mid-project.

Step 1 — Audit devices and identities
Export Meraki client lists for 30 days and match them to Intune and Entra ID. Classify every device as managed laptop, managed mobile, personal device, shared device or headless/IoT. Confirm operating system versions support WPA3 and the EAP method you intend to use.
Step 2 — Choose the RADIUS architecture
Decide between Meraki Cloud Authentication, a third-party cloud RADIUS service or an existing NPS / Cisco ISE deployment, using the scoring later in this guide. Record the decision, including who owns renewals and certificate expiry.
Step 3 — Stand up certificates
For EAP-TLS, configure a certificate authority — Microsoft Cloud PKI, the cloud RADIUS provider’s own CA, or an existing AD CS — and publish its trusted root and SCEP or PKCS profiles through Intune to a pilot group.
Step 4 — Build a pilot SSID
Create a new hidden or clearly named pilot SSID set to WPA3-Enterprise (or WPA2/WPA3 transition where older devices remain), pointing to the RADIUS servers, with RADIUS-assigned VLANs or Meraki group policies mapped to Entra ID groups.
Step 5 — Push Wi-Fi profiles to pilot users
Deploy an Intune Wi-Fi profile that names the SSID, the EAP method, the trusted server certificate and server name. Ten to fifteen users across Windows, macOS, iOS and Android is usually enough to flush out issues.
Step 6 — Handle the exceptions
Move printers, AV kit and sensors to an iPSK or MAC-based SSID on an isolated VLAN. Agree the policy for personal phones: guest network, app-protection only, or enrolment.
Step 7 — Expand to all staff
Assign the profiles to all users in waves, monitor Meraki event logs and RADIUS logs for failures, and provide a short note telling staff what to expect — usually nothing more than the new network appearing automatically.
Step 8 — Rename and retire the shared key
Once client logs show no staff devices on the old SSID for a week, disable it. Optionally rename the 802.1X SSID to the familiar office name. Update network documentation and the Cyber Essentials evidence pack.

Steps 1 to 3 can run in parallel with normal business. Steps 4 and 5 are where most of the learning happens, and the pilot should include at least one person who works from a Mac, one who relies heavily on their phone and one who visits other sites, because those are the profiles that expose gaps.

RADIUS architecture decision gauge

There are three realistic ways to give Meraki access points an Entra ID-aware RADIUS service. The gauge shows how ready the average Microsoft 365-first office is for the simplest of them — a fully cloud-hosted RADIUS with Intune-issued certificates and no on-premises servers.

71/100
Cloudswitched cloud-RADIUS readiness benchmark for Microsoft 365 offices

Option 1 — Meraki Cloud Authentication. Cisco now offers RADIUS hosted in the Meraki cloud that can synchronise users and groups from Entra ID, removing the need for a separate server. It suits single-vendor Meraki estates that want the fewest moving parts. Check current feature support for your chosen EAP method and certificate source, and confirm licensing on your Meraki co-term or subscription agreement before committing.

Option 2 — Third-party cloud RADIUS. Services such as SecureW2, JumpCloud, Portnox and Foxpass provide hosted RADIUS, a certificate authority and Entra ID integration, often with Intune connectors for automatic certificate issuance and revocation. They add a per-user subscription but bring mature tooling, device-posture checks and support for mixed-vendor networks.

Option 3 — On-premises or hybrid NPS / Cisco ISE. Microsoft NPS works well for hybrid-joined devices authenticating against on-premises Active Directory, but it does not natively validate cloud-only Entra ID users, so cloud-native offices end up building workarounds. Cisco ISE is a capable policy engine with a cost and skills profile that tends to suit larger organisations. Choose this route when you already run and maintain the infrastructure, not as a fresh build for a 40-person office.

802.1X Wi-Fi cost breakdown for a UK office

The table uses indicative ranges for a single-site office of roughly 50 users. Vendor list prices change and many are quoted in US dollars, so treat these as budgeting figures and confirm current pricing before you sign anything.

Cost elementTypical rangeNotes
Meraki 802.1X / WPA3 feature£0Included in existing MR licences; firmware must be current.
Cloud RADIUS subscription£1.50–£5 per user per monthVaries by provider, feature tier and device count; some price per device.
Certificate authority£0–£3 per user per monthOften bundled with cloud RADIUS; Microsoft Cloud PKI is an Intune add-on; existing AD CS has no licence cost but has upkeep.
Intune licensingUsually already heldIncluded in Microsoft 365 Business Premium and E3/E5; required for automatic certificate and Wi-Fi profile delivery.
Design, pilot and rollout£1,500–£6,000 one-offDriven by device count, operating system mix, number of sites and the IoT exception list.

For a 50-person office on a cloud RADIUS service with bundled certificates, a realistic first-year budget is in the region of £3,000 to £8,000 including professional services, then £1,000 to £3,000 a year in subscriptions. The offsetting costs are harder to put on an invoice but real: no emergency key changes when someone leaves on bad terms, no hours spent re-keying meeting-room devices, and cleaner evidence for insurers and Cyber Essentials assessors. If you are also weighing an access point refresh, factor in that new Wi-Fi 6E and Wi-Fi 7 hardware needs WPA3 on 6 GHz anyway, so 802.1X and a refresh project share much of the same testing.

Note

RADIUS traffic between Meraki access points and a cloud RADIUS service leaves your site over the internet. Most providers support RadSec (RADIUS over TLS) or require the access points to reach them from a fixed public address. If your broadband uses dynamic addressing, read our guide to static IP addresses for business broadband before you choose a provider.

802.1X benchmarks and KPIs to track

Once 802.1X is live, a few measurable indicators tell you whether it is healthy. The progress rows show the targets we set during the first 90 days, alongside the reasoning for each. Meraki’s Wireless Health view and the RADIUS provider’s logs between them supply almost all of the data.

Target operating benchmarks after cutover

Staff devices on 802.1X SSID
98%
Authentications using EAP-TLS
95%
First-attempt authentication success
97%
Clients validating server certificate
100%
Leaver devices revoked within 24 hours
100%
Certificates auto-renewed before expiry
99%
IoT devices isolated on own VLAN
100%
Access points on current firmware
100%
Wi-Fi helpdesk tickets vs baseline
40%

The final row is a ratio: it expresses expected Wi-Fi tickets after stabilisation as a share of the pre-project baseline. In our experience the spike happens in the first fortnight — mostly unmanaged devices and personal phones — and then falls well below the old level because there are no more “what is the Wi-Fi password?” requests. “Clients validating server certificate” is the one we never compromise on: a client that skips validation can be lured onto an impostor access point that harvests credentials, which undoes much of the point of 802.1X.

Common 802.1X and WPA3-Enterprise mistakes to avoid

Most failed rollouts fail for the same handful of reasons. None of them are exotic; they are planning gaps that show up on the first Monday.

  • Turning off the shared key before the logs say it is safe. Cut over only when Meraki client data shows the old SSID carries nothing but known exceptions.
  • Letting clients skip server certificate validation. “Do not validate” makes the first connection easier and leaves every password exposed to an evil-twin access point.
  • Building fresh on PEAP-MSCHAPv2. It works today on many devices but conflicts with Windows Credential Guard and is the weakest of the common methods. Start with EAP-TLS.
  • Forgetting certificate lifecycles. Root, intermediate and RADIUS server certificates all expire. An unnoticed server certificate expiry takes down the whole office at once.
  • Using WPA3-only on an SSID that still has older devices. Use WPA2/WPA3 transition mode during migration, then tighten once the device audit shows every client supports WPA3.
  • Mapping VLANs to individual users instead of groups. Assign VLANs or Meraki group policies from Entra ID groups so a role change is a group change, not a network ticket.
  • Leaving printers and AV kit on the staff VLAN. Headless devices go on their own iPSK or MAC-authenticated SSID with tight firewall rules.
  • No break-glass access. Keep a documented, tightly controlled fallback for the IT team if the RADIUS service is unreachable, and test it.
Watch out

Cloud RADIUS makes the internet connection part of the Wi-Fi authentication path. Meraki access points will keep already-connected clients online during a short outage, but new connections and roaming re-authentications can fail. Configure a secondary RADIUS server, consider a backup WAN on the Meraki MX, and read the provider’s service-level terms before you rely on it.

802.1X Wi-Fi checklist — the 12-point essentials

Use this checklist as a go/no-go list before you retire the shared key. Each item maps to something an auditor, insurer or future IT provider can verify.

  1. Every staff laptop is Entra-joined or Entra-registered and enrolled in Intune.
  2. Every device on the staff SSID runs a supported operating system — see our guide to Cyber Essentials and unsupported software.
  3. The RADIUS architecture is chosen, documented and has a named owner.
  4. Primary and secondary RADIUS servers are configured on every staff SSID.
  5. A certificate authority issues device or user certificates automatically through Intune.
  6. Intune Wi-Fi profiles specify the SSID, EAP-TLS, trusted root and RADIUS server name.
  7. Server certificate validation is enforced on every client platform.
  8. VLANs or Meraki group policies are assigned from Entra ID groups, not individuals.
  9. Printers, AV and IoT devices sit on an isolated iPSK or MAC-authenticated SSID.
  10. Guests use a separate captive-portal or WPA3-Personal SSID with internet-only access.
  11. Certificate expiry dates for root, intermediate and RADIUS server certificates are in a monitored calendar.
  12. The leaver process revokes Wi-Fi access by disabling the account and retiring the device, and this has been tested.
Note

Cyber Essentials does not require 802.1X by name, but the user access control and secure configuration controls expect you to manage who and what can join your network and to remove access promptly. A per-user Wi-Fi model with documented revocation is a far easier story to evidence than a shared key that dozens of former staff may still remember.

Mini case study — a 45-person Leeds practice retires its shared key

A professional services practice in Leeds with 45 staff, Meraki MR access points and Microsoft 365 Business Premium had used the same WPA2 key for four years. Around 30 people had left in that time. The trigger for change was a cyber insurance renewal questionnaire that asked how wireless access was revoked for departing employees — the honest answer was that it was not.

The audit found 41 Intune-managed Windows laptops, six unmanaged MacBooks used by the design team, around 60 phones of which half were personal, two multifunction printers, a meeting-room video bar and a set of environmental sensors. The practice chose a third-party cloud RADIUS service with a bundled certificate authority and an Intune connector, because it wanted no on-premises servers and needed support for a second small office the following year. The MacBooks were enrolled in Intune first; personal phones were offered the guest network or app-protection-only access to Microsoft 365, which most staff were content with.

A pilot group of twelve ran for a week on a WPA2/WPA3 transition SSID. Two issues surfaced: an Android profile missing the RADIUS server name, and a video bar that could not do 802.1X, which moved to an iPSK SSID on an isolated VLAN. The full rollout took three days in waves, and the shared key was switched off after the Meraki client list showed no staff devices on it for eight working days. Wi-Fi access now follows the Entra ID account, and the leaver checklist includes a step to confirm the device has been retired in Intune.

“We expected a week of complaints. What we actually got was a new network that appeared on everyone’s laptop and a question on the insurance form we could finally answer properly.” — Operations Director, Leeds professional services practice

At-a-glance summary

TopicKey fact
What 802.1X doesAuthenticates each user or device via RADIUS before network access is granted
WPA3-Enterprise802.1X with mandatory Protected Management Frames and stronger cipher rules
Recommended EAP methodEAP-TLS with device or user certificates issued through Intune
Method to avoid for new buildsPEAP-MSCHAPv2
Meraki licence impactNone — 802.1X and WPA3 are included in MR licences
RADIUS optionsMeraki Cloud Authentication, third-party cloud RADIUS, NPS or Cisco ISE
Entra ID-only users with NPSNot natively supported — prefer cloud RADIUS
Typical timeline2–6 weeks from audit to retiring the shared key
Indicative subscription cost£1.50–£5 per user per month for cloud RADIUS
Indicative project cost£1,500–£6,000 one-off for a single-site SME
6 GHz Wi-Fi 6E / Wi-Fi 7WPA3 mandatory; WPA2 not permitted
Headless and IoT devicesIsolated iPSK or MAC-authenticated SSID and VLAN
GuestsSeparate captive portal or WPA3-Personal SSID, internet only
Leaver handlingDisable the account and retire the device; Wi-Fi access ends with it

How Cloudswitched delivers 802.1X Wi-Fi on Meraki

Cloudswitched designs, deploys and manages Cisco Meraki networks for UK businesses, including moving offices from shared Wi-Fi keys to WPA3-Enterprise with Entra ID and Intune. We start with a device and identity audit, recommend the RADIUS architecture that fits your estate rather than a default product, pilot with your own people, and hand over documentation and certificate expiry monitoring so the setup stays healthy after go-live.

Move your office Wi-Fi to per-user authentication

Talk to our cloud networking team about an 802.1X readiness audit for your Meraki and Microsoft 365 estate.

Talk to us about Cloud Networking

Frequently Asked Questions

What is the difference between WPA3-Personal and WPA3-Enterprise?

WPA3-Personal uses one shared password with the SAE handshake, which resists offline password guessing far better than WPA2-Personal but still gives everyone the same secret. WPA3-Enterprise uses 802.1X, so every user or device authenticates individually against a RADIUS server, typically with a certificate. For a business, the Enterprise model means you can revoke one person’s Wi-Fi access without changing anything for anyone else, see exactly who is connected and assign network access by role.

Does Cisco Meraki support 802.1X with Microsoft Entra ID?

Yes. Meraki MR access points support 802.1X and WPA3-Enterprise on every licence tier and relay authentication to any standards-based RADIUS server. To use Entra ID identities you need a RADIUS service that understands Entra ID — Meraki Cloud Authentication, a third-party cloud RADIUS provider, or Cisco ISE. Microsoft NPS on its own authenticates against on-premises Active Directory and does not natively validate cloud-only Entra ID accounts.

Is EAP-TLS better than PEAP for business Wi-Fi?

For most Microsoft 365 businesses, yes. EAP-TLS authenticates with a certificate that Intune can issue, renew and revoke automatically, so there is no password to phish or capture. PEAP-MSCHAPv2 relies on usernames and passwords, is weakened when clients do not validate the server certificate, and conflicts with Windows Credential Guard, which is enabled by default on many current Windows 11 devices. EAP-TLS takes more setup, but it is the more durable choice.

Do I need an on-premises server for 802.1X Wi-Fi?

No. A cloud-first office can run 802.1X with no on-premises servers by combining Meraki access points, a cloud-hosted RADIUS service and certificates delivered through Intune. Many organisations previously relied on a Windows Server running NPS and Active Directory Certificate Services; that is still valid for hybrid environments, but it adds patching, backup and lifecycle responsibilities that small offices often prefer to avoid.

How much does 802.1X Wi-Fi cost for a small UK business?

The Meraki side adds no licence cost. Cloud RADIUS services typically cost around £1.50 to £5 per user per month depending on provider and features, and certificate issuance may be bundled or charged separately. Design, pilot and rollout for a single-site office of around 50 people usually sits between £1,500 and £6,000. These are indicative ranges; confirm current vendor pricing for your user and device counts.

What happens to printers and IoT devices that cannot do 802.1X?

Put them on a separate SSID using Meraki identity pre-shared keys or MAC-based authentication, on a dedicated VLAN with firewall rules that only allow the traffic they need. That keeps headless devices working without weakening the staff network. The device audit at the start of the project should list every such device so none of them disappear when the shared key is retired.

Can staff use personal phones on an 802.1X network?

They can if the phone is enrolled in Intune, which allows a certificate and Wi-Fi profile to be installed. Many businesses prefer not to enrol personal phones and instead give them the guest network plus app-protection policies for Microsoft 365 apps. Decide the policy before rollout and communicate it clearly; it is the most common source of questions during cutover.

Will 802.1X slow down Wi-Fi or roaming between access points?

Day-to-day throughput is unaffected because 802.1X only governs the initial authentication. Roaming can add a short re-authentication delay, which Meraki mitigates with fast roaming features such as 802.11r and opportunistic key caching where clients support them. With a cloud RADIUS service, initial connections depend on your internet link, so a secondary RADIUS server and backup WAN are sensible.

Does Cyber Essentials require 802.1X Wi-Fi authentication?

Cyber Essentials does not name 802.1X as a requirement. Its user access control and secure configuration controls do expect you to control who can access your systems and to remove access when people leave. Per-user Wi-Fi authentication with documented revocation is a straightforward way to evidence that for your wireless network, whereas a long-standing shared key is difficult to justify.

How long does it take to move from a shared Wi-Fi password to 802.1X?

For a single-site office with Intune-managed laptops, two to six weeks from audit to retiring the shared key is typical, with only a few hours of visible change for staff. Offices with many unmanaged devices, multiple sites or a large IoT estate take longer, mainly because device readiness rather than network configuration sets the pace.

Cloud-managed networking, set up properly

From Meraki access point design to WPA3-Enterprise and Entra ID integration, Cloudswitched builds and supports wireless networks for UK offices.

Explore Cloud Networking
Tags:Cloud Networking
Cloudswitched

London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.

Cloudswitched Service

Cloud Networking

Cisco Meraki cloud-managed networking for modern offices

More about this service
CloudswitchedCloud Networking
020 3004 3450
Insights & guides

Latest from our blog

Business Caller ID and Spam Call Labelling - How to Protect Your Number Reputation in the UK
VoIP & Phone Systems18 Nov 2026

Business Caller ID and Spam Call Labelling

If your sales team, collections desk or service engineers have noticed that fewer people pick up when they ring, the cause is often not the script or the time...

Read article
Static IP Addresses for Business Broadband: A UK Guide to Costs, IPv4 Scarcity and IPv6 Readiness in 2026
Internet & Connectivity17 Nov 2026

Static IP Addresses for Business Broadband

A static IP address for business broadband is one of those line items that sits quietly on a connectivity quote, costs a few pounds a month, and then turns out...

Read article
Data Quality for Business Reporting - A UK Guide to Fixing Bad Data Before It Reaches Your Dashboards
Database Reporting16 Nov 2026

Data Quality for Business Reporting

Every UK business that reports from a database eventually hits the same wall: the dashboard looks polished, but nobody trusts the numbers. Data quality for...

Read article
RAG for UK Businesses - How to Build an AI Knowledge Assistant on Your Own Documents
AI15 Nov 2026

RAG for UK Businesses

Retrieval-augmented generation (RAG) is the most practical way for a UK business to build an AI knowledge assistant that answers questions from its own...

Read article
Google Consent Mode v2 and Enhanced Conversions - A UK How-To Guide for Accurate Google Ads Tracking
Google Ads & PPC14 Nov 2026

Google Consent Mode v2 and Enhanced Conversions

Google Consent Mode v2 and enhanced conversions decide whether your Google Ads account can still see what your advertising is actually doing. For a UK business...

Read article
New Starter IT Onboarding Checklist UK - Autopilot, Entra ID and a Ready Day One
IT Support13 Nov 2026

New Starter IT Onboarding Checklist UK

A new starter IT onboarding checklist is the difference between a new employee who is productive by ten o clock on their first morning and one who spends the...

Read article
Microsoft 365 Copilot Licensing & Cost in the UK: 2026 Guide
Microsoft 365 Copilot12 Nov 2026

Microsoft 365 Copilot Licensing & Cost in the UK

Microsoft 365 Copilot licensing is the single biggest line item most UK organisations will add to their Microsoft bill this decade, and it is also one of the...

Read article
Penetration Test Preparation: The Complete Pre-Test Checklist
Penetration Testing11 Nov 2026

Penetration Test Preparation

A penetration test checklist is the difference between a test that tells you something useful and one that burns five days of consultant time arguing about IP...

Read article
Cloud Backup Initial Seeding - How Long Your First Upload Really Takes (UK Guide 2026)
Cloud Backup10 Nov 2026

Cloud Backup Initial Seeding

Most businesses sign up for a cloud backup service, install the agent, press start and assume they are protected by the end of the day. In reality, cloud...

Read article
WPA3-Enterprise and 802.1X Wi-Fi Authentication - A UK Guide to Meraki and Entra ID
Cloud Networking9 Nov 2026

WPA3-Enterprise and 802.1X Wi-Fi Authentication

If your office Wi-Fi still runs on a single shared password that has not changed since the last office move, WPA3-Enterprise and 802.1X Wi-Fi authentication is...

Read article
Technology stack

Built on technology you can trust.

We design, run and secure your IT on proven, industry-leading platforms, including Microsoft 365 and Azure, Cisco Meraki, Cloudflare, AWS, BitDefender and SolarWinds, so your business stays secure, scalable and reliable.

  • SolarWinds
  • Cloudflare
  • BitDefender
  • AWS
  • Hono
  • SolarWinds
  • Cloudflare
  • BitDefender
  • AWS
  • Hono
  • Opus
  • Office 365
  • Microsoft
  • Cisco Meraki
  • Microsoft Azure
  • SolarWinds
  • Opus
  • Office 365
  • Microsoft
  • Cisco Meraki
  • Microsoft Azure
  • SolarWinds

Enquiry Received!

Thank you for getting in touch. A member of our team will review your enquiry and get back to you within 24 hours.