Infinet

Cybersecurity Awareness Month: Is Your Business as Protected as You Think?

October is Cybersecurity Awareness Month, making it a good time to take a closer look at how you’re protecting your business. 

You already know cybersecurity matters. You’ve likely invested in firewalls, antivirus software, backups, and other safeguards to protect your systems and information. But how confident are you that those protections are working the way they should? 

At InfiNet Solutions, we help organizations throughout Omaha and the surrounding communities answer that question. We help our partners understand that effective cybersecurity isn’t necessarily about having more technology. It’s about understanding your risks, maintaining the protections you already have, and making sure someone is paying attention. 

Having the right security tools is important, but how they’re managed matters just as much. 

Take your firewall, for example. It helps protect your network from unwanted traffic, but it needs to be properly configured and maintained. Antivirus and other security software can detect suspicious activity, but someone needs to review alerts and respond when a threat is identified. 

Even something as familiar as multi-factor authentication (MFA) deserves a second look. Requiring an additional form of verification helps protect your accounts when passwords are compromised. But if MFA isn’t enabled across your important systems, you may still have unnecessary exposure. 

The same goes for software updates. As vulnerabilities are discovered, updates help close security gaps before attackers can take advantage of them. 

You don’t need to know how to configure every security tool yourself. You do need to know that someone is maintaining them, monitoring their effectiveness, and addressing problems when they arise. 

Your employees make decisions every day that can affect your organization’s security. 

They open attachments, exchange documents, approve payments, and communicate with clients and vendors. Most of those interactions are perfectly ordinary, which is exactly why cybercriminals try to imitate them. 

A fraudulent invoice might appear to come from a familiar vendor. An email requesting sensitive information might look like it came from someone on your leadership team. And with increasingly sophisticated scams, suspicious messages aren’t always easy to recognize. 

That’s why cybersecurity awareness should be part of your everyday operations, not just an annual training exercise. 

Encourage your employees to verify unusual requests, particularly those involving money, passwords, or confidential information. Make sure they know how to report suspicious activity and feel comfortable doing so, even if they’re unsure whether something is actually wrong. 

Your team doesn’t need to become a group of cybersecurity experts. They just need the knowledge, tools, and confidence to recognize when something deserves a closer look. 

Imagine starting your workday and discovering that you can’t access your files, applications, or business systems. 

How long could you continue operating? 

Depending on your business, an outage could mean missed appointments, interrupted production, delayed orders, or an inability to serve your customers. 

You probably already have some form of data backup in place. But having backups and being able to recover from an outage aren’t necessarily the same thing. 

Do you know how frequently your information is backed up? When was the last time a backup was successfully restored? And how long would it take to get your most important systems running again? 

These questions matter because recovery is about more than retrieving lost files. It’s about getting your business back to work. 

Regular backup testing and a well-defined recovery plan help you understand what to expect if something goes wrong. They also give you an opportunity to identify problems before you’re depending on those systems in an emergency. 

You don’t need to personally manage your company’s cybersecurity, but you should know who’s responsible for it. 

Someone needs to monitor security alerts, manage employee access, maintain software, review vulnerabilities, and coordinate the response when an issue arises. 

That might be your internal IT department, an outside technology partner (hello there!), or a combination of both. What’s important is that those responsibilities are clearly defined and consistently carried out. 

It’s also worth understanding what happens when employees join or leave your organization. Are new employees given access only to the systems they need? Is that access adjusted when their responsibilities change? And is it promptly removed when they leave? 

These details are easy to overlook during the normal course of business, but they can create security gaps if no one is responsible for managing them. 

You don’t need to understand every technical detail. You should, however, feel confident that your security is being actively managed and that you know who to call when something needs attention. 

Cybersecurity Awareness Month is a good reminder that protecting your business requires ongoing attention. 

You don’t necessarily need new software, a larger technology budget, or an overhaul of your existing systems. Sometimes the most valuable thing you can do is ask a few questions. 

Are your security tools being monitored? Does your team know how to recognize suspicious activity? Have your backups been tested? And do you have a clear plan for responding to an incident? 

If you don’t know the answers, that’s a good place to start. 

At InfiNet Solutions, we believe good cybersecurity starts with understanding your business, your risks, and what you need to keep operating. We work with organizations throughout Omaha and the surrounding communities to identify vulnerabilities, strengthen protections, and make informed decisions about their technology. 

This October, take a closer look at how your business is protected. Ask questions, identify opportunities for improvement, and make sure the right people are looking out for your organization. 

Because cybersecurity isn’t just about protecting your technology. It’s about protecting everything your business depends on. 

Cybersecurity Awareness Month: Is Your Business as Protected as You Think? Read More »

Why Cyber Insurance Claims Get Denied (and How to Avoid It) 

Cyber insurance has become a standard part of risk management for many businesses. But having a policy does not necessarily mean every cyber incident will be covered. 
One area that can create problems is the information provided during the application and renewal process. 
Cyber insurance applications commonly ask businesses about security controls such as multi-factor authentication, backups, employee security training, patch management, and endpoint protection. Insurers use those answers to evaluate risk and determine coverage terms. 
The challenge is that businesses do not always have an accurate picture of what is actually in place. 
An organization may report that MFA is enabled, for example, without realizing that certain accounts or systems are excluded. A company may have reliable backups but no documented history of testing restores. Security awareness training may exist, but completion records may be incomplete. 
Those distinctions can become important when a claim is reviewed. 
Cyber insurance applications can be surprisingly specific. 
A question may not simply ask whether your organization uses MFA. It may ask whether MFA is required for email, remote access, administrative accounts, or other systems. 
The same applies to backups. An application may distinguish between having backups, protecting backups from unauthorized access, and regularly testing whether those backups can be restored. 
This is why technical questions should be verified rather than answered based on assumptions or previous configurations. 
Your environment also changes over time. New employees, applications, devices, locations, vendors, and remote access methods can all affect whether an answer that was accurate last year remains accurate today. 
Confirm exactly where MFA is required and whether there are accounts, applications, or access methods that are exceptions. 
Pay particular attention to email, remote access, administrative accounts, and any other systems specifically identified on the application. 
Verify what systems and data are backed up, how frequently backups occur, where they are stored, and whether recovery is tested. 
If your application states that backups or restores are tested regularly, maintain records of those tests. 
Confirm that required training is actually being completed and documented. 
Training records should identify who completed the training and when. If phishing simulations or other ongoing training are part of your security program, those records should also be maintained. 
Make sure the patching process described on the application reflects how systems are actually managed. 
This includes identifying devices that may have fallen outside normal management processes and understanding how operating systems and applications are kept current. 
Confirm that endpoint security tools are installed, active, and appropriately managed across applicable devices. 
New computers and other changes to the environment can create gaps if deployment is not regularly reviewed. 
It is useful to be able to demonstrate how a security control is configured rather than simply state that it exists. 
Depending on the control, documentation may include configuration reports, backup logs, restore-test results, training records, device inventories, patching reports, or endpoint-security reports. 
Good documentation serves more than an insurance purpose. It also gives the business a clearer understanding of its own security posture. 
If there is uncertainty about a technical question on an insurance application, the IT team or provider responsible for the environment should verify the answer. Questions about policy language, coverage, or how an insurer wants a particular question interpreted should be addressed with the insurance broker or carrier. 
One common mistake during renewal is relying too heavily on the previous year’s answers. 
A business can change significantly in twelve months. It may add employees, introduce new software, replace infrastructure, expand remote access, or change how data is stored. 
The renewal process is a good opportunity to compare the application against the current environment rather than simply confirming what was reported previously. 
A technical review should include the security controls addressed by the application as well as any significant technology changes that occurred during the policy period. 
For organizations using vCIO & IT Strategy services, this type of review can become part of the broader technology planning process rather than a separate exercise each year. 
No security review can guarantee that a future claim will be covered. Coverage depends on the policy, the circumstances of the incident, and applicable law. 
What a business can control is the accuracy of the information it provides. 
Before submitting or renewing a cyber insurance application, verify the technical answers, document the controls that are in place, and correct information that is no longer accurate. 
The objective is straightforward: the security environment described on the application should accurately reflect the security environment the business is operating. 
InfiNet Solutions helps organizations understand and document their technology environments, identify security gaps, and verify the technical controls that may appear on cyber insurance applications. 
If your cyber insurance renewal is approaching, we can help you review the technology side before you submit it. 
Claims can be denied for many reasons depending on the policy and circumstances. One potential issue is a material difference between information provided during the application process and the controls that were actually in place. The effect of any discrepancy depends on the policy language, facts of the incident, and applicable law. 
Confirm which users, accounts, applications, and access methods require MFA. Pay particular attention to email, remote access, and privileged or administrative accounts, as these are commonly addressed on cyber insurance applications. 
If your insurance application asks whether backups or recovery procedures are tested, verify that your practices support the answer you provide. Regardless of insurance requirements, restore testing is an important part of determining whether backups can actually be used during an incident. 
Documentation may include MFA configuration, backup and restore records, security awareness training records, device inventories, patching reports, and endpoint-security reports. The appropriate documentation depends on the controls your organization uses and the questions on your application. 
Your IT provider can help verify technical information about your environment. Questions involving coverage, policy interpretation, or insurance requirements should be discussed with your broker or carrier. 
Review it at every renewal and after significant changes to your technology environment. Rather than assuming last year’s answers are still correct, verify them against the systems and controls currently in place.

Why Cyber Insurance Claims Get Denied (and How to Avoid It)  Read More »

Beyond Basic IT: What Architecture & Engineering Firms Really Need

Architecture and engineering firms ask a lot more of their technology than the average office. 
Large Revit models, CAD files, rendering software, plotters, high-performance workstations, and years of project data all have to work together. Add contractors, consultants, and clients who need access to project information, and even a relatively small firm can have a fairly complex IT environment. 
That means the technology supporting an A&E firm needs to be built around how the firm actually works — not around a standard office setup. 
Here are some of the areas that matter most. 
For an A&E firm, project files aren’t just documents sitting on a server. They’re active work product, project history, and often the result of hundreds or thousands of hours of work. 
Losing access to a model or drawing set can delay a project quickly. Even losing a few hours of recent work can create a significant headache when a deadline is approaching. 
That means determining how much recent work the firm can reasonably afford to lose, protecting the systems and project data that matter most, and keeping backup copies separate from the primary environment. 
It also means testing restores. 
A backup can report that it completed successfully every night, but that doesn’t necessarily tell you whether the data can be recovered when you actually need it. Regular restore testing helps make sure the recovery plan works before there’s an emergency. 
A computer used primarily for email and Microsoft Office has very different requirements from one running Revit, AutoCAD, Civil 3D, or rendering software all day. 
Memory, graphics capability, processors, storage, and even the way the workstation is configured can affect how well those applications perform. 
And simply buying the most expensive workstation isn’t necessarily the answer. 
Hardware should match the applications, project sizes, and workloads your team actually uses. It also needs to be maintained with those applications in mind. 
The same goes for support. If an administrative computer is having a minor issue, that’s inconvenient. If a project team’s workstation can’t open a model the day a drawing set is due, that’s a production problem. 
IT support should understand the difference. 
A&E firms also deal with something many other businesses don’t: different clients, consultants, and projects may require different versions of the same software. 
One project might still be in an older version of Revit while a new project starts in the latest release. A consultant may be using a different AutoCAD version. Certain plugins or add-ons may only work with specific releases. 
Updating everything at once isn’t always practical — and doing so without planning can create compatibility problems. 
IT needs to understand which versions are required, how updates affect active projects, and when upgrades can happen without disrupting production. 
That also means keeping track of licensing, plugins, workstation requirements, and dependencies instead of treating every software update like a routine “click install” situation. 
In a typical office, a printer problem is annoying. 
In an architecture or engineering firm, a plotter problem can hold up a deliverable. 
Plotters, scanners, conference-room technology, specialized peripherals, and other production equipment should be treated as part of the firm’s overall technology environment. 
That includes maintaining the network connections, drivers, permissions, and configurations those devices rely on. 
It’s easy to overlook this equipment when thinking about IT, right up until something stops working when the team needs it. 
Architecture and engineering projects involve a lot of people who don’t work for your firm. 
Contractors, structural engineers, MEP consultants, owners, and other partners may all need to exchange files or review project information. 
Business cloud services can make that much easier, but they also need to be configured properly. 
External users shouldn’t have access to more information than they need. Old project links shouldn’t remain open indefinitely. Employees shouldn’t have to fall back on personal accounts or improvised file-sharing methods because the approved process is too difficult to use. 
The goal is straightforward: make collaboration easy enough that people actually use the right tools while keeping access controlled and visible. 
Security matters, but so does usability. 
If security controls make everyday project work unnecessarily difficult, people tend to find ways around them. On the other hand, leaving everything wide open creates obvious risk. 
A practical cybersecurity plan should protect accounts, devices, project data, and backups without turning routine work into an obstacle course. 
That can include multi-factor authentication, endpoint protection, access controls, patching, secure backups, and monitoring for unusual activity. 
Monitoring can also help identify problems such as failing hardware or suspicious activity before they become larger disruptions. 
It’s worth understanding exactly what your IT provider means by monitoring, though. 24/7 system monitoring isn’t necessarily the same thing as having someone sitting at a help desk 24 hours a day. Firms should know how monitoring, support hours, and after-hours escalation actually work. 
Technology decisions shouldn’t only happen when something breaks. 
If you’re hiring more designers, opening another office, taking on larger projects, changing design software, moving more work into the cloud, or replacing aging workstations, those decisions affect the rest of the IT environment. 
Planning ahead gives the firm time to budget and make changes deliberately instead of discovering limitations in the middle of a project. 
InfiNet’s vCIO & IT Strategy approach connects those technology decisions to the firm’s broader plans. That can include workstation replacement cycles, storage capacity, software requirements, cybersecurity, backup and recovery, and future infrastructure needs. 
An IT provider doesn’t need to be an architect or engineer. 
But they should understand the environment they’re supporting. 
They should know why Revit performance matters, why different software versions may need to coexist, why a plotter can be production-critical, and why recovering yesterday’s project files isn’t always good enough. 
More importantly, they should be able to talk about technology in terms that matter to the firm: downtime, project schedules, productivity, risk, and client commitments. 
Because ultimately, that’s the job of IT in an A&E firm. 
A&E firms typically need support that understands CAD and BIM applications, high-performance workstations, plotters, project-file storage and backup, cybersecurity, and collaboration with outside contractors and consultants. IT should be designed around the firm’s production environment rather than a standard office setup. 
Applications such as Revit, AutoCAD, Civil 3D, and rendering software can require considerably more processing power, memory, graphics capability, and storage than typical office applications. Workstations should be selected based on the software and workloads each employee actually uses. 
Active projects, clients, consultants, plugins, or project requirements may depend on specific software versions. Upgrading too early can create compatibility problems, so firms may need to maintain multiple versions and plan upgrades around active projects. 
Backups should run often enough to reflect how much recent work the firm can reasonably afford to recreate. Important data should have protected copies separate from the primary environment, and restores should be tested regularly to confirm that files and systems can actually be recovered. 
Yes, when it’s configured appropriately for business use. Access should be limited to the people who need it, external users should be authenticated where appropriate, and sharing permissions should be reviewed as projects and teams change. 
Start with issues that could stop production or put project and client data at risk: failed or untested backups, aging hardware, account security, overly broad access, software compatibility problems, and inadequate protection of endpoints and project data. 
If your technology is becoming something your team has to work around instead of something that helps them work, it may be time to take a closer look.
Learn more about InfiNet’s Architecture & Engineering IT Support. 

Beyond Basic IT: What Architecture & Engineering Firms Really Need Read More »

The Omaha Business Cybersecurity Checklist (No IT Degree Required)

You don’t need to understand every cybersecurity tool your business uses. But there are a few questions you should be able to get a clear answer to. 

Is MFA turned on? Are your backups working? Are computers getting updated? Does your team know what to do with a suspicious email? And if something unusual happens, who is actually paying attention? 

If the answer to some of those is “I’m not sure,” that’s a good place to start. 

Here’s a straightforward cybersecurity checklist for businesses in Omaha, Lincoln, Council Bluffs, and the surrounding area.

Check: Can employees access email, financial systems, or other important business applications with only a password? 

If they can, turn on multi-factor authentication (MFA). 

MFA requires another form of verification in addition to a password. That means a stolen password alone usually isn’t enough to get someone into an account. 

At minimum, look at: 

• Microsoft 365 or Google Workspace 

• Accounting and financial applications  

• Remote access and VPN accounts 

• Administrative accounts 

• Other systems containing sensitive business or customer information

 Where available, consider stronger options such as passkeys or security keys. 

Software updates aren’t just about getting new features. They frequently fix known security problems. 

The important question isn’t whether employees occasionally click Update. It’s whether your business has a consistent process for keeping devices and applications current. 

• Operating systems receive security updates 

• Business applications are kept current 

• Browsers are updated 

• Network equipment and other business technology receive appropriate updates 

• Someone is responsible for identifying devices that fall behind 

If updates depend entirely on employees remembering to install them, there’s room for improvement.

Most businesses will confidently say they have backups.

The better question is: When was the last time you tested one?

A backup is useful only if you can recover what you need from it.

• Important business data is backed up

• Backups run automatically

• Backup failures are reviewed 

• Restore tests are performed periodically 

• You know how long recovery would realistically take 

If nobody can remember the last successful restore test, put this one near the top of your list.

You don’t need an elaborate 20-page password policy. You do need some basic rules that everyone follows. 

• Employees use unique passwords for work accounts 

• Passwords aren’t shared through email, Teams, or sticky notes 

• A business-approved password manager is available 

• Shared or administrative credentials are controlled 

• MFA is used wherever possible

The policy only matters if it reflects what people actually do.

Email remains one of the easiest ways to get in front of an employee. 

Fake invoices, password-reset notices, Microsoft 365 login pages, messages that appear to come from an executive, and requests to change payment information can all look convincing. 

Your email system should have tools in place to identify and filter suspicious messages before employees ever see them. 

But filtering isn’t perfect—which brings us to the people using it.

Security awareness training doesn’t need to mean sitting through the same hour-long presentation every year. 

Short, practical training throughout the year is generally more useful. 

Employees should know:

• How to recognize common phishing attempts

• Where to report a suspicious message 

• What to do if they accidentally click something 

• Not to approve an unexpected MFA request 

• How to verify unusual requests involving money or sensitive information

That last one is especially important. 

If someone receives an email asking them to change banking information, send a wire, buy gift cards, or provide sensitive employee information, verify the request another way. Call a known number or speak to the person directly rather than using the contact information provided in the message. 

Mistakes happen. What matters next is how quickly your business knows about them. 

Employees should know exactly who to contact if they:

• Click a suspicious link 

• Enter a password on a questionable website 

• Approve an MFA request they didn’t initiate 

• Open a suspicious attachment 

• Notice unusual activity on their computer or account 

You want people reporting those situations immediately—not spending an hour worrying that they’ll get in trouble.

Security tools can generate warnings about things like unusual logins, failed backups, missing updates, or systems that suddenly stop checking in. 

But an alert doesn’t accomplish much if nobody reviews it. 

Ask:

• Who reviews security alerts? 

• Who checks backup failures? 

• Who identifies computers missing important updates? 

• Who investigates unusual login activity? 

• Who is responsible for responding when something needs attention? 

You don’t necessarily need someone staring at a dashboard around the clock. You do need tools watching for problems and a clear process for deciding what happens when they find one. 

If you don’t want to go through the entire list today, start here. 

Ask whoever handles your IT these five questions: 

1. Is MFA required for everyone’s email? 

2. When did we last successfully restore something from backup? 

3. Are all of our computers current on security updates? 

4. What should an employee do immediately after clicking a suspicious link? 

5. Who reviews our security alerts? 

You’re looking for specific answers. 

“We should be.” 

“I think so.” 

“Probably.” 

“Someone gets those alerts.” 

Those aren’t really answers. 

Not every business needs an internal cybersecurity department. But somebody needs to own these responsibilities. 

If you went through this checklist and found several questions you couldn’t answer, that doesn’t automatically mean your business has a major security problem. It means you’ve identified what needs to be checked. 

Start there. 

InfiNet works with businesses throughout Omaha, Bellevue, Council Bluffs, Papillion, Lincoln, and surrounding communities to understand what protections are already in place, identify gaps, and prioritize what actually needs attention. 

You don’t need to become a cybersecurity expert. You just need to know the right questions to ask. 

Need help getting those answers? Let’s talk. 

What is the most important cybersecurity step for a business owner to take right now? 

Start by making sure MFA is required for email and other important business accounts. A password by itself shouldn’t be enough to access sensitive systems. Where available, consider phishing-resistant methods such as passkeys or security keys. 

Do I need an IT background to understand my company’s cybersecurity risk? 

No. You don’t need to understand how every security tool works. You should, however, be able to get clear answers about MFA, backups, updates, employee training, monitoring, and who is responsible for each. 

How often should employees receive security awareness training? 

Security awareness works best as an ongoing practice rather than a once-a-year event. Include it during onboarding, reinforce important habits throughout the year, and provide additional guidance when threats or business processes change. 

How do I know whether our backups are good? 

Test them. A successful backup notification tells you the backup process ran; a successful restore tells you that you can actually recover your data. Periodic restore testing is an important part of a reliable backup strategy. 

What does proactive monitoring mean? 

It means using tools to watch for conditions that may need attention, such as unusual logins, failed backups, missing security updates, or security tools that stop reporting. Just as importantly, someone needs to be responsible for reviewing and responding to those alerts. 

When has a business outgrown informal IT support? 

One warning sign is when important questions consistently get uncertain answers. If nobody can confirm whether backups work, updates are current, security alerts are being reviewed, or former employees have lost access, your business probably needs a more defined IT process. 

Do small businesses really need cybersecurity? 

Yes. Phishing, compromised accounts, ransomware, and other threats aren’t limited to large companies. The appropriate tools may differ based on the size and needs of the business, but basic protections matter at any size.

The Omaha Business Cybersecurity Checklist (No IT Degree Required) Read More »

Microsoft Is Phasing Out Text-Message MFA. Here’s What Businesses Need to Know 

If you’re used to signing into Microsoft 365 and waiting for a six-digit code to arrive by text, that experience is on its way out. 

Microsoft is moving away from SMS and voice calls as preferred methods of verifying sign-ins and pushing users toward more secure options, including passkeys and the Microsoft Authenticator app. 

For businesses, this is less about learning another Microsoft feature and more about making sure employees are ready before their familiar sign-in option changes.

Text-message verification was a big improvement over using a password alone. The problem is that attackers have gotten better at getting around it. 

SMS codes can be intercepted or stolen through phishing and SIM-swapping attacks. They also depend on your mobile carrier actually delivering the message. Anyone who has stared at a login screen waiting for a code that never arrives knows that isn’t always a given. 

Microsoft now recommends stronger authentication methods that don’t rely on a text message being sent to your phone. 

That includes Microsoft Authenticator, Windows Hello for Business, security keys and, increasingly, passkeys. 

A passkey is essentially a replacement for a traditional password that uses something you already have, such as your phone or computer, to verify that you’re really you. 

Depending on the device, that might mean using your fingerprint, Face ID, Windows Hello or your device PIN. 

The important part isn’t the terminology. It’s that passkeys are designed to be much harder for an attacker to steal through a fake login page. 

Microsoft Authenticator can also be part of this experience. The app supports MFA approvals, verification codes, passwordless sign-in and passkeys. 

Microsoft has been moving users toward stronger authentication for some time, but there are now some important dates for businesses using Microsoft Entra ID. 

Beginning September 1, 2026, Microsoft plans to start automatically enabling passkey registration prompts for users who are still enabled for SMS or voice authentication. 

Then, beginning February 1, 2027, Microsoft-provided SMS and voice authentication will be retired in Microsoft Entra ID. 

That doesn’t mean everyone’s text-message MFA will suddenly disappear tomorrow. Organizations have time to prepare, and Microsoft provides administrators with options for managing the transition. 

But it does mean businesses shouldn’t wait until employees are confronted with an unfamiliar sign-in screen to figure out what they’re supposed to do. 

For most users, the biggest change will simply be how they prove it’s really them when they sign in. 

Instead of:

Password → Receive text → Enter six-digit code 

they may use something like: 

Password → Approve sign-in through Authenticator 

or eventually: 

Passkey → Face, fingerprint or device PIN  

Depending on how your Microsoft environment is configured, the exact experience may look different.


And that’s important: businesses shouldn’t tell employees to blindly follow every unexpected authentication prompt they receive. Your IT provider or internal IT team should determine which authentication methods your organization is using and communicate that process to employees.


Any change to the login process can be annoying at first. From a security standpoint, though, moving away from SMS makes sense. 


Passwords get stolen. Text-message codes can be phished. Attackers routinely create convincing Microsoft login pages designed specifically to capture credentials and verification codes. 


Modern authentication methods make that considerably harder. 


Microsoft is also increasingly using system-preferred authentication, which means that when someone has multiple authentication methods registered, Microsoft can prompt them to use the strongest available option instead of automatically falling back to something weaker.


The goal is pretty simple: make the easiest way to sign in also one of the safest. 


You don’t need to panic, and you don’t need to wait until 2027 either. 


This is a good time to have your team review:


• Which employees are still using SMS or voice calls for MFA


• Whether Microsoft Authenticator is properly configured 


• Whether passkeys are appropriate for your organization 


• Which authentication methods are allowed in Microsoft Entra ID 


• How employees will be notified and trained before their sign-in experience changes 


• What your recovery process looks like when someone loses or replaces a phone 


A little preparation now can prevent a lot of “I can’t get into my email” calls later.


The takeaway isn’t that Microsoft is getting rid of multi-factor authentication. 


Quite the opposite. 


Microsoft is moving away from some of the older ways of doing MFA and toward methods that are harder for attackers to steal, intercept or trick users into handing over.


If your business still relies heavily on text-message codes, now is a good time to review how your Microsoft 365 accounts are protected and start preparing employees for what’s coming. 


Not sure which authentication methods your organization is currently using? InfiNet Solutions can review your Microsoft 365 security configuration, identify users still relying on older authentication methods and help you plan the transition without turning it into a company-wide login headache. 

Microsoft Is Phasing Out Text-Message MFA. Here’s What Businesses Need to Know  Read More »

Global Microsoft Outlook Outage: Email service may be disrupted. If you need assistance with a non email related issue, please call our office or submit a ticket through the client portal.

Close Welcome Bar
Talk to our Team