

Publish Date
18/11/2026
Categories
Blogs
TL;DR
Business email continuity gives your organisation an alternative way to send and receive email when your primary email service is unavailable.
The recent Microsoft 365 outage demonstrated why this matters. If Exchange Online is unavailable, businesses without an alternative may have to wait for normal service to return.
An independent email continuity solution can help keep communication flowing, but it doesn’t restore Microsoft 365, Teams, SharePoint or other affected services. It works best as part of a wider business continuity, backup and disaster recovery plan.
Email is one of those services businesses expect to simply work.
It’s used for customer enquiries, orders, contracts, approvals, supplier communication and everyday collaboration. If it suddenly becomes unavailable, the impact can quickly extend beyond IT.
Business email continuity is designed to reduce that risk.
Put simply:
Business email continuity is the ability to keep sending, receiving and accessing email when your normal email service is unavailable.
It’s particularly relevant to organisations using cloud platforms such as Microsoft 365, where Exchange Online has become a critical communication service.
The recent Microsoft 365 outage provided a real-world example of this risk.
Exchange Online was particularly affected, with users experiencing problems accessing mailboxes and email services. Other Microsoft 365 functionality was affected too.
For businesses, the important question isn’t necessarily why an outage happened.
Rather, it’s: If Microsoft 365 email became unavailable, could we continue communicating with customers, suppliers and employees?
Microsoft builds significant resilience into Microsoft 365, but no cloud platform should be treated as incapable of experiencing disruption.
That’s why businesses need to think about business resilience as well as cloud resilience.
An independent email continuity service provides an alternative way to access and exchange email when your primary service isn’t available.
Depending on the technology and configuration, users can switch to an alternative email environment and continue sending and receiving messages.
When the primary service returns, messages handled during the continuity period can be synchronised back into the normal email environment.
In practical terms:
Without continuity:
Microsoft 365 unavailable → email unavailable → wait for service restoration.
With continuity:
Microsoft 365 unavailable → continuity activated → email continues → Microsoft 365 restored → normal service resumes.
For a business where email is essential for sales, customer service or operations, that difference could be significant.
For the email element of the outage, potentially yes.
An organisation with an independent email continuity solution correctly configured and tested could potentially have provided employees with another route for sending and receiving email while Exchange Online was unavailable.
However, that doesn’t mean everything would have continued working normally. This is where understanding the limitations matters.
Well, of course, it doesn’t restore Microsoft 365.
An email continuity provider cannot fix an underlying Microsoft problem. It provides an alternative email service while the primary environment is unavailable.
It also doesn’t keep every Microsoft 365 service running.
Email continuity is about email. If an incident affects Teams, SharePoint, OneDrive, Copilot or other Microsoft 365 services, email continuity doesn’t automatically restore them. That’s why email continuity should form part of a wider backup and disaster recovery strategy.
It doesn’t solve problems for organisations you’re emailing.
Your email might be working through an alternative service, but a customer or supplier could be affected by the same wider outage. You can improve your organisation’s resilience, but you can’t guarantee theirs.
Email continuity needs to be configured and tested.
Finding out how your continuity solution works during the outage is too late. Businesses need to know who activates continuity, how employees access it and whether dependencies such as authentication could also be affected. Regular testing is therefore as important as the technology itself!
Email continuity isn’t the same as backup.
This is an important distinction. Email continuity = keeping email available. Email backup = protecting and recovering email data.
Disaster recovery = restoring systems, applications and data after an incident. They solve different problems but should complement each other.
If you’re reviewing Microsoft 365 resilience, it’s also worth understanding whether you can rely on Microsoft 365 for full data backup.
A simple way to determine this is to ask:
What would happen if our normal business email stopped working for an entire working day?
Consider whether:
The greater the business impact, the stronger the case for independent email continuity.
This assessment should also sit alongside your wider cyber security and resilience planning. Service outages aren’t the only reason critical systems can become unavailable. Cyber incidents, connectivity failures and other disruptions can have a similar operational impact.
An email continuity service is only useful if your organisation knows what to do with it.
Your plan should answer five basic questions:
The same thinking should be applied to other critical services.
If Teams, SharePoint, OneDrive, identity services, telephony or a critical business application became unavailable, what would employees do?
Perhaps the most important lesson from a cloud outage is that outsourcing your infrastructure doesn’t outsource responsibility for business continuity.
Your cloud provider is responsible for the resilience and recovery of its underlying services, but your organisation is responsible for understanding what happens if those services aren’t available.
For businesses heavily dependent on Microsoft 365, that means understanding critical dependencies and putting appropriate contingency measures around them.
At Cobweb, our Managed IT Services help organisations manage and protect the technology their businesses depend on, while identifying opportunities to improve security, resilience and continuity.
The question isn’t:
“Will Microsoft 365 ever experience another outage?”
A more useful question is:
“If our email went down tomorrow, would everyone know what to do?”
If the answer isn’t an immediate yes, it may be time to review your business email continuity plans.
Business email continuity enables an organisation to continue sending, receiving and accessing email when its primary email service is unavailable.
An independent continuity solution provides an alternative email environment during an outage, helping employees continue communicating with customers, suppliers and colleagues.
If an outage affects Exchange Online, users may experience problems accessing, sending or receiving email through their normal Microsoft 365 environment.
An independent email continuity solution can provide an alternative route for email until normal service is restored.
Potentially, yes.
If your organisation has an independent email continuity solution that has been correctly configured, users may be able to continue sending and receiving email while Exchange Online is unavailable.
The exact capabilities will depend on the solution, configuration and nature of the outage.
Microsoft 365 is designed with significant resilience and availability capabilities. However, organisations should still plan for circumstances where a Microsoft 365 service becomes temporarily unavailable.
Businesses where email is critical may therefore consider an independent continuity service as an additional layer of resilience.
No.
Email continuity keeps email communication available during an outage. Email backup protects data so it can be recovered if it is lost, deleted, corrupted or encrypted.
Both can form part of a wider backup and disaster recovery strategy.
No.
Email continuity focuses specifically on maintaining email communication.
Disaster recovery is broader and focuses on restoring systems, applications, infrastructure and data following an incident.
Not necessarily.
An email continuity solution is designed primarily to maintain email communication. It won’t automatically restore Teams, SharePoint, OneDrive, Copilot or other Microsoft 365 services affected by an outage.
This is why businesses should understand their wider Microsoft 365 dependencies rather than considering email in isolation.
Email remains a critical communication channel for many organisations.
If losing email for several hours would significantly affect customers, sales, suppliers or business operations, an independent continuity solution can reduce the impact by providing an alternative way to communicate.
Start by identifying your critical Microsoft 365 services and the business processes that depend on them.
Consider independent email continuity, alternative communication channels, backup and disaster recovery, cyber security, documented incident procedures and regular testing.
For organisations without the resources to continually manage their Microsoft environment internally, a Microsoft 365 Managed Service can provide additional specialist support. Our team is happy to talk you through business continuity and what would work best for your organisation – you can always book a call with us here!
for your organisation

Publish Date
11/11/2026
Categories
Blogs
Microsoft is changing how you pay for some Copilot features.
Rather than everything being covered by your licence, certain AI features will use a consumption-based model, where you pay based on usage. This is known as Usage-Based Billing (UBB) and is measured using Copilot Credits.
Microsoft has announced that UBB is expected to be switched on automatically for new Copilot Business purchases between January and March 2027, with the exact date still to be confirmed.
New licences will have a default monthly spending limit of 4,000 Copilot Credits per user (roughly £30). Importantly, this doesn’t mean you receive 4,000 Copilot Credits to use each month.
Copilot Credits are consumed when you use eligible usage-based AI features, and you’ll be charged based on what you actually use. The 4,000-credit figure is simply the default spending limit, helping to prevent costs going beyond this level unless you choose to increase the limit.
Read on to understand how Copilot Credits work, what consumes them and how you can control your spend.
Copilot Credits are how Microsoft measures the work AI does for you. The more work an AI feature does, the more credits it uses.
It’s important you know your Microsoft 365 Copilot licence isn’t going away, and you’re not moving to paying for every prompt. Credits sit alongside your licence for the more advanced AI features.
They apply to things like:
💡Microsoft states one Copilot Credit = $0.01 USD.
Unfortunately, there’s no single answer.
One credit doesn’t equal one prompt. It all depends how complex the task is. For example, which AI model is being used? Is Copilot having to fetch data from APIs? What other tools are involved?
A quick question uses fewer credits than an AI agent working through several steps. So your cost depends on what you ask AI to do, and how often.
The best way to understand how quickly you’ll use Copilot Credits is to test different tasks and keep a close eye on your usage. Microsoft also has a Copilot Credit Estimator you can use.
Pay-as-you-go. You pay for the credits you use. It’s flexible, but you’ll need to keep an eye on usage.
Pre-purchased credits. You buy credits up front. This suits you better if your usage is easy to predict.
As we mentioned at the start, Microsoft is switching on usage-based billing (UBB). Originally scheduled for December, Microsoft has delayed the automatic switch-on from customer feedback.
It’s now expected between January and March 2027, with the exact date is still to be confirmed.
From then, UBB will be turned on automatically when you buy new Microsoft Copilot Business licences. It isn’t a new way of paying – you can already switch UBB on yourself. The change is that it will be on by default for new purchases.
With the date still to be confirmed, now is a good time to prepare:
Usage can grow quickly.
Testing an AI agent with 20 people makes the cost look small. But roll it out to hundreds of staff, each using it several times a day, and the same agent is doing far more work, so the bill grows.
That’s why it’s worth working out your likely usage, and setting limits and budgets, before you scale up. Both IT and finance need to see what’s being used and what you’re getting back.
Once you understand how much each task uses and what that means for cost, the next step is to look at the value Copilot creates. Don’t just focus on the cost of the credits used – consider the time, effort and wider business costs the task could save.
Copilot is no longer just a licence for each person. With Copilot Credits and usage-based billing on the way, it pays to know what you’re using.
The aim isn’t to spend the least. It’s to know what you’re spending, why, and what you get back.
It’s a way of paying for some Copilot features based on how much you use them, rather than a flat fee per person. It runs on Copilot Credits.
Microsoft now expects this between January and March 2027. The exact date is still to be confirmed.
The planned change is for new Microsoft Copilot Business purchases. Usage-based billing is already available, so if you’d like to use it sooner, you can switch it on yourself.
No. Credits sit alongside your licence and cover the more advanced AI features, such as using an agent. You won’t be paying for every prompt.
It depends on what you use and how often. One credit doesn’t equal one prompt, and a task with several steps uses more credits than a quick question. The best way to get a feel for it is to test and watch your usage.
Yes. Microsoft provides spending controls and budget tools in the Microsoft 365 admin, so you can set limits and keep an eye on usage as it grows.
Our team is happy to talk you through the changes and help you understand the best way to manage Copilot Credits and usage-based billing, based on where your business is with AI today. You can get in contact with us here.

Publish Date
05/11/2026
Categories
Blogs
Most ransomware response plans are written during the attack.
Someone notices files will not open, a ransom note appears, and the first hour goes on working out who is in charge and whether to switch everything off.
A response plan settles those questions beforehand, so the time is spent containing the damage and getting the business working again.
Download our incident response plan template here, or talk to us about ransomware protection and testing or developing your recovery plan.
A ransomware response plan is an agreed set of roles, decisions and actions covering the period between discovering a ransomware incident and returning the business to normal operations.
It should sit alongside your wider cyber incident response plan, as well as your backup and disaster recovery arrangements.
Although preventative controls such as multi-factor authentication, endpoint protection and employee awareness are intended to make an attack less likely to succeed, a response plan answers a different question: what happens if an attacker gets through anyway?
You would of course hope you would never have to use your ransomware response plan, but it’s far better to have one in place if you ever did need to. For an SME, a useful plan should cover five things:
It’s important you also keep it concise and so that it can be understood by everyone in the business.
💡How much could your business lose in a ransomware attack? Use this calculator to find out →
Who is in charge?
This is the main question your plan should answer. They should have sufficient authority to make decisions quickly, making sure you also have someone as deputy in case that person is unavailable.
If a ransomware incident did occur, decisions involving business operations, IT, customers, employees, insurance, finance and legal obligations will all be considerations – not just technical!
Responsibilities should therefore be agreed for the relevant people across IT, senior management, finance, HR and customer communications.
The next questions is how these people will contact each other – your usual tools may not be an option! If your systems are down, so might email or Teams and so you will need another communication route.
Keeping an offline contact list of internal contacts is vital, including:
The first hour of a ransomware incident response is about limiting further damage without destroying useful evidence.
After the incident lead has been contacted, affected devices should be isolated from networks (wired-connections/WiFi) as quickly as possible. Where possible, avoid simply wiping or unnecessarily powering down equipment before specialist advice, because information held on compromised systems may help investigators understand what happened.
Isolation is not the same as eradication – you still need to establish how the attacker got in, what they have accessed and whether they have other routes into your system.
Compromised accounts may therefore need to be disabled and credentials reset using a clean device. Your managed service provider or IT provider should investigate suspicious admin accounts, mailbox rules, remote-access software and other changes that might give the attacker continuing access.
Now, you need to check your backups. Confirm your backup copies are isolated and protected from the compromised environment. Do not assume that because backups ran successfully yesterday they are safe today! Your attacker could have targeted your backups because destroying an organisation’s ability to recover increases payment pressure to the ransom.
Finally, start a written timeline.
Record what was discovered by whom, when each decision was made and what action was taken. Keep logs and evidence rather than deleting or altering them. Your timeline can become invaluable for your managed service provider, insurer, legal adviser and any other involved parties.
A ransomware attack quickly becomes more than an IT problem. Your response plan should identify organisations and people that may need to know about it, along with who has the authority to contact them.
If you have cyber insurance, notify your insurer as early as possible.
Policies can contain specific notification requirements, and insurers may provide or specify incident response, forensic and legal specialists. Before appointing external specialists independently, check your policy so that you understand its requirements.
Keep both the policy information and claims contact details available offline.
A ransomware attack can also become a personal data breach.
UK GDPR’s definition of this includes accidental or unlawful destruction, loss or alteration of personal data, as well ad unauthorised disclosure or access. That means losing availability of personal data that can potentially constitute a breach, even where there is no evidence that the information was stolen.
Where a breach is likely to result in a risk to people’s rights and freedoms, organisations generally need to notify to ICO without delay, and where feasible, within 72 hours of becoming aware of it.
A ransomware incident does not mean you automatically need to report to the ICO. Your plan should establish who will assess the data protection impact and involve appropriate legal/data protection expertise when needed.
The plan should also identify the appropriate route for reporting the incident as a crime, and when specialist cyber security support should be engaged.
The National Cyber Security Centre (NCSC) publishes specific guidance on ransomware, as well as response and recovery guidance for smaller organisations. Those resources (so long as they are up to date) are worth including directly in the response documentation.
You may need to communicate with employees, customers, suppliers and partners. In your plan, decide who should:
Be careful to make definitive statements too early – saying ‘data has not been accessed’ for example is different from saying ‘there is currently no evidence that data has been accessed’.
This is arguably the hardest decision a business could face during a ransomware attack, which makes it one of the worst decisions to consider for the first time during one.
UK authorities including the NCSC do not encourage, endorse or condone the payment of ransomware demands.
There are good reasons for that. Paying a ransom does not guarantee that systems can be successfully decrypted. It does not guarantee that stolen information will be deleted. And paying does not remove an organisation’s data protection or other legal responsibilities.
There can also be significant legal considerations, including sanctions risk. If a ransomware demand is received, the business should obtain appropriate legal advice and consult its cyber insurer before taking action or communicating with an attacker.
The UK’s policy on ransomware payments and incident reporting is also developing. Government proposals have considered measures intended to reduce payments to ransomware criminals and increase incident reporting. Businesses should therefore check current UK government guidance rather than treating a response plan written today as fixed indefinitely.
Ultimately, one factor dramatically changes the position a business finds itself in: whether it can recover without a decryption key from the attacker.
That is why a ransomware response plan and tested backups belong together.
Trying to decide which application to restore first while half the company is unable to work is difficult.
That’s why it’s best to decide it now.
Create an agreed recovery order covering the systems the business cannot operate without. Depending on the organisation, that could include identity and authentication services, customer databases, finance systems, communications platforms, order processing or other operational applications.
Your ransomware recovery plan should also establish suitable recovery time objectives (RTOs) and recovery point objectives (RPOs).
An RTO describes how quickly a service needs to be restored, while an RPO addresses how much data loss the business can tolerate. Together, they turn “get everything back as quickly as possible” into measurable recovery priorities.
Crucially, do not restore systems simply because a backup is available.
Backups should be clean and tested, and affected systems may need to be rebuilt or verified before data is restored. Restoring your data onto an environment an attacker can still access risks creating a second incident.
Take a look at our backup and disaster recovery services if you’re looking to build greater resilience into your recovery arrangements.
Technology recovery is only part of the problem.
Think about the essential work that still has to happen if core systems are offline for a day, several days or longer.
How will the business:
Document simple manual workarounds for the most important processes, including where the information and forms needed to use them will be kept.
When technology is restored, validate the recovered data carefully and incorporate information generated during the outage back into the relevant systems. Enhanced security monitoring should continue after recovery so suspicious activity or signs of continued attacker access can be investigated quickly.
An untested response plan contains assumptions. Testing tells you which ones are wrong.
One of the simplest approaches for an SME is a tabletop exercise once or twice a year.
Bring together the people named in the response plan and give them a realistic scenario. For example:
It is 7.10am on a Monday. An employee reports a ransom message on their computer. Within 20 minutes, three other employees report that shared files are inaccessible. The finance director cannot access email. What happens next?
Work through the incident step by step: Who makes the first decision? Who contacts the IT provider? Can someone find the cyber insurance details without accessing the corporate network? Who can authorise customer communications? If email is unavailable, how does everybody communicate?
Record every gap and give it an owner.
Choose a priority system and perform a controlled recovery test. Record how long restoration takes, whether the required data is present and whether the application operates correctly afterwards.
Review the plan when important employees leave or change roles, when new systems are introduced, when suppliers change and following any genuine cyber incident.
Response planning is a cycle. Lessons from recovery should improve both the response plan and the controls used to prevent the next attack.
For a more structured template, please download our incident response plan.
| Decision | What to have written down |
|---|---|
| Who leads? | Incident lead, deputy and responsibilities for each team |
| Who do we call? | Offline contacts for the incident lead/deputy, IT provider, insurer, legal adviser and critical suppliers |
| What happens first? | Device isolation, account containment, evidence preservation and backup protection procedures |
| Who needs to know? | Employees, customers, legal advisers, your cyber insurer, managed service provider and potentially the ICO (and any other regulatory bodies) |
| What comes back first? | Prioritised restore order, including RTOs and RPOs |
| How do we know it works? | Dates and results from tabletop exercises and restore tests, plus owners for identified actions |
Begin by containing the incident. Isolate affected devices from the network, protect backups from the compromised environment and activate your incident response process. Contact the nominated incident lead and appropriate IT or incident response provider, and notify your cyber insurer in accordance with your policy.
Not every ransomware attack automatically requires notification to the Information Commissioners Office (ICO). However, some scenarios (where a personal data breach is likely to result in a risk to people’s rights and freedoms) mean the organisation needs to notify the ICO without delay and, where feasible, within 72 hours of becoming aware of the breach.
UK authorities do not encourage, endorse or condone ransom payments. Businesses should know payment does not guarantee that the attackers will recover your data/systems or that stolen data will be deleted.
There is no standard recovery time. It depends on factors including how many systems were affected, how quickly the attack was contained, the condition of the backups and whether the organisation has previously tested its restoration process.
A measured restore test of your priority systems provides a much more meaningful recovery estimate than simply checking whether backups have completed successfully.
A disaster recovery plan primarily covers how technology and data will be restored following disruption. A ransomware response plan is broader. It addresses containment, roles and responsibilities, evidence preservation, regulatory and contractual reporting, stakeholder communications and other decisions required during a ransomware incident, as well as the eventual recovery of technology.
Nobody wants to test their ransomware arrangements for the first time during a real attack.
Download our incident response plan template to start documenting the people, contacts and actions your organisation will need during an incident.
If you want greater confidence in your cyber security processes and recovery plans, our cyber security specialists are more than happy to talk about ransomware protection and test your recovery arrangements – please just contact us here. A practical recovery test can establish whether your backups and procedures will actually get the systems your business depends on running again when it matters.
Giving your business peace of mind

Publish Date
22/10/2026
Categories
Blogs
A modern workplace is a IT focused but flexible work environment that uses online tools (in the cloud), hybrid work models and employee-focused initiatives to bring productivity and collaboration to the organisation.
Essentially it’s a way to bring people, IT tools and working habits together, so that everyday tasks are slightly easier and more secure, whether they’re in the office, at home, or on the move.
If you’ve ever searched through emails for a file or wondered which version of a document to use, you’ll recognise the problems it can help solve. Often, the answer isn’t more software, but making better use of what you already have!
Arguably, AI is now also an important element creeping into the modern workplace too for most organisations.
In practice, a modern workplace will mean your team knows where to find information and how to share it, while IT look after devices and access without making work unnecessarily complicated.
A few things included in the modern workplace model help make this possible:
When people talk about the Microsoft Modern Workplace, they mean using Microsoft’s tools to support this flexible way of working. Most organisations use Microsoft 365 – it’s often the centre of a business, bringing together familiar apps with tools for sharing documents, managing devices and protecting access:
The tools you use in Microsoft 365 will depend on your license, as Modern Workplace isn’t just one fixed package. Rather, it depends on how you set up your Microsoft subscriptions and how you train your employees on using them.
Less time lost on everyday tasks
When files are easy to find and updates are all done in one place, your team can spend less time chasing information or repeating work. They will actually be able to tick more off of their to-do list!
Better teamwork, wherever people are working
Working on the same document makes it easier for colleagues to contribute wherever they’re based, without pulling versions together. It also means meetings can happen any when, no matter where each person is, using virtual meeting rooms via Microsoft Teams.
More consistent security
Microsoft allows businesses to protect accounts, keep devices up to date and apply different permissions to data, reducing security risks.
A clearer view of your IT spending
Using software like Microsoft to create a modern workplace allows you to more easily review your setup. This could show overlapping subscriptions or useful features you’re already paying for, meaning you can budget better in the long run.
It’s important to remember that a modern workplace still needs to be managed regularly. Policies can change, people switch jobs, updates aren’t always automatic, and risky behaviour needs to be monitored. A lot of businesses therefore opt for a managed service to help reduce this workload.
Imagine your team is putting together a customer proposal. Rather than emailing attachments back and forth, everyone can work in the same document at the same time, stored in SharePoint and available through Teams. So long as permissions are correct, only the people who need it will have access.
There’s less confusion about which version to use because everyone knows where the document lives. It’s a simple change, but it shows how the tools and the way people can use them to work together.
Like we mentioned above, AI is now arguably part of the modern workplace. It can support a lot of this everyday work too, with drafting content, summarising information and finding answers – dependant on your model subscription and setup.
You don’t need to have AI to have a modern workplace – but if you’re considering it, ensure you start with clear use cases and a secure foundation.
There’s no need to change everything all at once. A useful starting point is to ask your team what slows them down, then look at where your existing tools (or enhanced licenses) could help.
Not quite. Microsoft 365 provides many of the tools, while a modern workplace also includes how your team uses them, organises information and keeps data safe.
No, it’s just as relevant to teams who work in the office. Being able to find information, share files and work securely matters wherever you’re based.
Yes. Smaller teams can benefit from easier file sharing, better account protection and simpler ways to work together. The setup should reflect what your business needs, rather than how many people you employ.
There isn’t a fixed price, as it depends on your users, licences, devices and security needs, along with any migration, training or support. Reviewing what you already pay for is a good place to start.
Not necessarily. You may be able to get more from the tools you already use. Where older systems need to stay, any changes should work alongside them without disrupting everyday work.
Not on its own. The tools can support compliance, but you’ll still need suitable settings, policies and training, with regular checks against the requirements that apply to your organisation.
A modern workplace will look different for every business. What matters is whether your setup helps people do their jobs and gives IT a manageable way to support them.
If you’re not sure where to start, talk to Cobweb about how your current IT setup and where you’d like things to work better.
Our friendly team will be more than happy to help!

Publish Date
13/10/2026
Categories
Blogs
Cyber security gaps aren’t always caused by businesses having no security technology in place. More often, the IT environment has changed while security controls haven’t kept pace.
People join, leave and change roles. New devices and applications are introduced. Temporary exceptions become permanent. Over time, a gap can develop between the security you think you have and the security actually protecting your organisation.
An IT security review helps uncover those weaknesses, understand where genuine risk exists and identify what should be addressed first.
Here are five common security gaps worth looking for.
Identity is a critical part of cyber security. If an attacker gains access to a legitimate account, they may also gain a route into business systems and information.
Multi-factor authentication (MFA) provides an important additional layer of protection, but simply having MFA enabled doesn’t mean identity security is fully addressed. Exceptions, legacy configurations and inconsistent policies can all create gaps.
Modern identity controls can strengthen that protection further. Passkeys, phishing-resistant MFA, Authentication Strengths, token protection and risk-based Conditional Access can all form part of a stronger approach to protecting identities and access.
In a Microsoft 365 environment, Conditional Access can provide greater control over access to company resources, while Microsoft Intune can support device compliance and management.
An effective IT security review should therefore look beyond whether MFA is switched on and assess whether identity controls are appropriate and consistently applied across the organisation.
You can learn more about Cobweb’s Cyber Security Solutions, covering areas including endpoint, email and data security.
Permissions have a habit of accumulating.
Someone changes role but retains access to information from their previous department. A supplier finishes a project but their account remains active. An employee receives additional privileges that are never subsequently removed.
Individually these issues may seem minor, but collectively they increase the potential impact of a compromised account and can contribute to data oversharing.
This becomes particularly important as businesses adopt AI tools such as Microsoft 365 Copilot. Copilot readiness isn’t only about deploying the technology. It also means understanding what information employees already have permission to access.
Applying least privilege helps ensure people have the access they need without unnecessary permissions remaining indefinitely. Information protection and sensitivity labels can also form part of a wider approach to protecting sensitive information and managing areas such as insider risk.
Cobweb’s Data Security services include managing user and device permissions alongside measures designed to protect business information.
A security review provides an opportunity to establish who has access to important information, how much access they have and whether they still need it.
Patching might sound like routine IT housekeeping, but it’s an important part of cyber security.
Vulnerabilities are continually discovered across operating systems, applications and devices. As IT environments grow, keeping visibility over everything becomes harder.
Older devices can be overlooked, applications can remain on outdated versions and some systems may sit outside automated update processes. Remote and infrequently connected devices can make the problem harder still.
Effective patch management therefore needs to sit within a wider vulnerability management approach.
That can include vulnerability scanning, exposure management and attack surface reduction, helping businesses understand where weaknesses exist and prioritise the issues representing the greatest risk.
Cobweb includes patch management within its Endpoint Security services, alongside Microsoft Defender for Business, device management and security monitoring.
A security review can help bring those areas together, providing a clearer picture of whether devices and applications are being managed consistently rather than assuming everything is up to date.
Buying good security technology doesn’t automatically result in good security.
Many organisations already have sophisticated capabilities through Microsoft 365, Microsoft Defender, Microsoft Intune and specialist third-party security products. The challenge is making sure those technologies are correctly configured, managed and reviewed.
Settings that made sense two years ago may no longer reflect the way the organisation operates today.
Employees change. Devices change. New cloud applications are introduced. Data moves. Working practices evolve. Security configuration needs to evolve with them.
This is particularly relevant to Microsoft 365, where users, devices, permissions and security policies require ongoing management.
Cobweb’s Microsoft 365 Managed Services include management of tenants, users and devices, proactive monitoring and an integrated Security Operations Centre.
A security assessment can help determine whether your existing investment is delivering the protection you expect, rather than simply identifying more technology to buy.
Cyber security isn’t only about preventing incidents. Organisations also need to recognise suspicious activity and respond when something happens.
Modern security technologies can generate significant amounts of information and alerts. But generating an alert is very different from someone assessing it, understanding its significance and taking appropriate action.
Without active security monitoring, potentially important activity can become another notification among hundreds of others.
For organisations without an internal security operation, managed security and a Security Operations Centre (SOC) can help close this gap.
Cobweb’s Microsoft 365 Managed Services include a 24/7 SOC, where systems are continuously monitored and security alerts reviewed and responded to.
This also forms part of Cobweb’s wider Managed IT Services, combining ongoing IT management with monitoring, maintenance and security capabilities.
A useful IT security review should consider the overall environment rather than individual security products in isolation. It should examine areas such as:
Increasingly, it should also consider AI and data governance.
As organisations adopt Microsoft 365 Copilot and other AI tools, Copilot readiness, data oversharing, information protection, sensitivity labels and insider risk become part of the wider security conversation.
AI gives employees new ways to find and interact with company information. That makes understanding existing permissions and how sensitive information is protected increasingly important.
The purpose of an IT security review isn’t to produce the longest possible list of technical problems. It’s to identify the risks that genuinely matter and establish what should be prioritised.
For example, weaknesses around phishing, spoofing or malware could make Email Security a priority. Concerns around resilience and recovering business information could highlight the need to review Backup & Disaster Recovery.
None of these issues necessarily means an organisation has poor cyber security. Gaps often emerge because businesses and their technology continually change.
People join and leave. Devices are replaced. Applications are introduced. More information moves into the cloud. AI is changing how employees discover and interact with company information. Meanwhile, cyber threats continue to evolve.
That’s why an IT security review shouldn’t simply be an exercise in finding more security products to buy.
It should establish where you are today, identify the gaps that genuinely matter and prioritise what you should do next.
The objective is simple: make sure the security you think you have is the security you actually have.
Talk to Cobweb about reviewing your IT security environment to understand where you’re protected, where the gaps are and what you should prioritise next.
An IT security review examines an organisation’s technology environment and security controls to identify potential weaknesses, unnecessary exposure and opportunities to improve protection.
An IT security review can consider identity and access, MFA, permissions, endpoint security, patch management, Microsoft 365 security configuration, email security, data protection, backup, security monitoring and incident response.
Keeping systems appropriately updated helps address known vulnerabilities where fixes have been made available. Cobweb includes patch management as part of its Endpoint Security services.
Security isn’t only about having access to the technology. Appropriate configuration and ongoing management of users, devices and security controls are also important. Cobweb’s Microsoft 365 Managed Services include tenant, user and device management alongside proactive monitoring and a 24/7 SOC.
A SOC provides dedicated security monitoring and response. Within Cobweb’s Microsoft 365 Managed Service, the 24/7 SOC continuously monitors systems, with a cyber security team watching for threats and responding to security activity.
Tuesday 21st January 2025 | 10:00 - 10:30 GMT
In our webinar, we'll discuss:
If you'd like to learn more, please sign up via the form above.

Why SMBs Must Move Beyond Awareness to Action Now More Than Ever
Publish Date
01/10/2024
Categories
Blogs Hot Topic
During Cyber Awareness Month, it’s essential for small and medium-sized businesses (SMBs) to move beyond awareness and take action against cyber threats. SMBs are increasingly targeted by hackers due to underinvestment in security and more open infrastructures. Larger organisations are now requiring suppliers to meet baseline security standards, like Cyber Essentials Plus. To protect themselves, SMBs should implement measures such as multi-factor authentication, managed backups, email security, password managers, and continuous employee training. Awareness is no longer enough—taking action is crucial for survival in today’s digital landscape.
October marks Cyber Awareness Month, an important opportunity to reflect on the ever-evolving cybersecurity landscape. For years, awareness campaigns have been crucial in educating individuals and businesses about cybersecurity—encouraging them to use strong passwords, avoid phishing scams, and protect sensitive data. While awareness provides a vital foundation, it’s no longer enough—especially for small and medium-sized businesses (SMBs). With cyber threats growing more sophisticated every day, SMBs must take urgent, tangible action.
In the past, hackers primarily targeted large corporations, viewing them as high-value targets with vast stores of sensitive data. However, SMBs are now firmly in the crosshairs for several reasons:
For SMBs, taking action isn’t just about survival—it’s about securing future growth. Moving beyond awareness means developing and implementing a comprehensive cybersecurity strategy. Here’s how SMBs can shift from knowing to doing:
It’s no longer enough to be aware of the risks—action is imperative. SMBs must adopt proactive cybersecurity measures to protect their businesses, customers, and reputations. With the right combination of investment, strategy, and ongoing employee engagement, SMBs can build the defences needed to thrive in an increasingly dangerous digital world.
This October, during Cyber Awareness Month, don’t just be aware. Take action—your business’s survival may depend on it.
Join our webinar to explore the rising threat of Business Email Compromise (BEC) attacks and why traditional security methods are falling short. We’ll discuss the evolving tactics of BEC attackers and the need for advanced defences. Discover how Mimecast’s AI-driven technology enhances detection, reduces false positives, and offers stronger protection against these sophisticated threats.
Tuesday 1st October 2024 | 10:00 - 10:30 GMT
AI is no longer just a buzzword—it's a critical tool in the fight against cyber threats. As malicious AI-driven attacks become more prevalent, leveraging AI to counter these threats and protect against other cyber risks is essential.
In our webinar, we'll discuss:
You'll also have the opportunity to put forward your questions to Mimecast expert, Mark Olding.
If you'd like to learn more, please sign up via the form above.


Publish Date
24/05/2024
Categories
Blogs
This article was last reviewed and verified for accuracy in June 2026.
With the increasing threat of cyber-attacks, it is crucial for organisations to protect their sensitive data and prevent unauthorised access to their systems. However, it can be challenging for companies to identify and address vulnerabilities within their IT infrastructure – but that’s where Microsoft Secure Score can help.
Microsoft Secure Score assesses and measures your organisation’s security posture to give you an idea as to how well you are protected from threats. It provides guidance and actions to help strengthen your Microsoft environment for three primary areas, including: Identity, Data and Apps.
In the Microsoft Secure Score overview page, you can see how points are split between these groups and what points are available. The overview page is also the place to get an all-up view of the total score, historical trend of your secure score with benchmark comparisons, and prioritised improvement actions that can be taken to improve your score. You can use this data to act and make big differences in your security posture.
You are given points for configuring recommended security features, performing security-related tasks (such as viewing reports), or addressing the improvement action with a third-party application or software. Some actions are scored for partial completion, like enabling multi-factor authentication (MFA) for your users. Security should always be balanced with usability, and not every recommendation will work for your environment.
💡It’s important to note that your Microsoft Secure Score reflects only the security controls available within your current licensing (for example, Microsoft 365 Business Premium).
You may also see a higher potential score in the portal, which represents the full set of security recommendations available across the wider Microsoft 365 suite (including higher-tier plans like E5). This can highlight additional capabilities that aren’t included in your current licence.
To find your Microsoft Secure Score, go to the Microsoft 365 Defender portal and select Secure Score from the menu.

Microsoft Secure Score is a measurement of an organisation’s security posture. Your score reflects your progress against a set of recommended security actions, with the total possible score varying depending on your Microsoft 365 services and configuration. Secure Scores can also vary depending on the size and complexity of the organisation, but a higher score indicates better adherence to security best practices.
Here are some guidelines for what might be considered a good score:
The ideal score also depends on the industry and regulatory requirements. For instance, organisations in highly regulated sectors like finance or healthcare may aim for a higher secure score to comply with stringent security standards.
It’s important to regularly review and act on the recommendations provided by the Secure Score to improve and maintain a robust security posture.
If your licence includes the features below and you haven’t already configured them, a good place to start improving your score is by focusing on:
Our engineers can help guide you through your Microsoft Secure Score and carry out any remediation work to improve your score and security posture. If you’d like to find out more, please get in touch by calling 0345 223 9000 or by emailing hello@cobweb.com.

Publish Date
29/04/2024
Categories
Blogs
In the ever-evolving landscape of digital transformation, where businesses and individuals increasingly rely on online platforms for their daily operations and transactions, the risk of falling prey to sophisticated cyber threats has escalated. As a Managed Service Provider (MSP) committed to safeguarding your digital journey, we believe it’s imperative to address a crucial aspect of cybersecurity: the normalisation of discussions around online scams. It’s not a matter of if you might encounter a scam or attack, but when.
Online scams have undergone a dramatic evolution, leveraging advanced technology and psychological tactics to exploit vulnerabilities. These scams range from phishing attempts that mimic trusted entities to elaborate schemes promising high returns on investments. It’s essential to understand that these scams are designed to deceive, making no one immune to their traps, regardless of their level of digital savviness or intelligence.
There’s a pervasive stigma surrounding victims of online scams, often tinged with embarrassment and self-blame. This sentiment stems from a misconception that falling victim to a scam is a sign of naivety. However, the real danger of this stigma lies in its potential to deter victims from reporting these incidents, thereby hindering their recovery process and allowing scammers to operate with impunity.
As your MSP, we are on the front lines of your digital security, and part of our mission is to change the narrative around online scams. Here’s how we’re doing it:
Proactive Communication: We are committed to keeping you informed about the latest scam tactics and preventive measures. Regular updates and educational content are part of our strategy to empower you and your team, ensuring you’re always a step ahead.
Offering Robust Support Systems: Our dedicated support team is here to assist you in the event of a scam. From identifying the breach to navigating the recovery process, we provide the resources and expertise needed to minimize the impact on your operations.
Emphasising the ‘When’ Not ‘If’: We operate under the premise that encountering online scams and attacks is a matter of ‘when’ not ‘if’. This mindset is crucial for developing robust prevention strategies and resilience against potential threats.
Advocating for Transparency and Reporting: Encouraging transparency and prompt reporting of scams within your organisation can significantly mitigate risks. It also plays a vital role in our collective efforts to combat online fraud, enabling us to update our defensive measures in real-time.
Educating your business: We work with leading awareness training companies to provide cost effective training and education, and threat simulations to your employees. We help you prepare for the ‘when’, meaning these threats will go no further.
Managing Your Services: Our management of the products we provide, such as Microsoft 365, Azure, Acronis, and Mimecast & KnowBe4 means that threats are being monitored and dealt with by experts who work in this field day in and day out. They are also the most up-to-date on changes to products and licenses and evolving threats.
Together, by fostering an environment of openness, education, and support, we can strengthen our defences and maintain the integrity of our digital ecosystem. Remember, in the realm of cybersecurity, preparedness and partnership are our most potent weapons.
Recent Comments