Connect every location without creating a network nobody can manage
Running one office can be complicated enough.
When your organisation operates across several locations, every connectivity decision becomes more important.
One site may have a leased line. Another may use Full Fibre broadband. A smaller branch may depend on an older connection nobody has reviewed for years. Remote employees may connect through home broadband, while cloud applications, telephone systems and security services need to work consistently everywhere.
When the network has grown one site at a time, problems often follow.
Employees at one office experience slow cloud access. Video calls break up at another. A local router fails and nobody knows who supports it. Security policies differ between locations, and opening a new branch becomes a separate technical project every time.
Stratiis helps organisations connect offices, branches, remote sites and cloud services through a more consistent, secure and manageable network.
Reliable connectivity at every site. Central visibility. One clear support route.
What is multi-site connectivity?
Multi-site connectivity describes the services and network technologies used to connect several business locations.
These locations may include:
- Head offices
- Branch offices
- Customer-service centres
- Warehouses
- Community locations
- Construction sites
- Data centres
- Remote facilities
- Home workers
- Cloud platforms
A multi-site network may allow employees to:
- Access shared business systems
- Use Microsoft 365
- Make and receive business calls
- Join video meetings
- Connect securely to cloud applications
- Use shared printers or specialist systems
- Work from different offices
- Access central security services
- Communicate between locations
The network may use a combination of:
- Business broadband
- Leased lines
- Full Fibre
- 4G and 5G
- Site-to-site VPNs
- SD-WAN
- Private circuits
- Managed routers
- Firewalls
- Cloud gateways
- Internet failover
There is rarely one connection type that suits every location.
The goal is to create one joined-up design using the right service at each site.
Is your multi-site network becoming difficult to support?
Multi-site networks often develop gradually.
A new office opens and receives whatever connection is available. Another site keeps its existing supplier. A temporary router becomes permanent. Different IT providers configure different firewalls.
Eventually, nobody has a complete picture.
You may recognise some of these problems:
- Different sites use different broadband providers
- Nobody knows when contracts renew
- Router models vary between offices
- Security settings are inconsistent
- Cloud applications perform differently at each location
- One site depends on another office for internet access
- Employees cannot move easily between sites
- Video calls and Hosted Voice are unreliable
- Small branches have no backup connection
- Faults are passed between several suppliers
- Site-to-site VPNs disconnect regularly
- New offices take too long to connect
- Traffic is routed inefficiently
- Local Wi-Fi problems are blamed on the wide-area network
- Former sites still generate telecoms charges
- Nobody monitors connectivity centrally
A more structured design can improve reliability without forcing every site onto the most expensive service.
Our multi-site connectivity services
Stratiis can help with:
- Multi-office internet connectivity
- SD-WAN
- Site-to-site VPNs
- Leased lines
- Business broadband
- Full Fibre
- 4G and 5G connectivity
- Private circuits
- Managed routers
- Managed firewalls
- Internet failover
- Cloud connectivity
- Microsoft 365 connectivity
- Hosted Voice networking
- Centralised monitoring
- Network segmentation
- Secure remote access
- New-site connectivity
- Office moves
- Network documentation
- Contract and supplier consolidation
- Ongoing support
Different sites need different connections
It may be tempting to give every office the same service.
That is not always practical or cost-effective.
A head office may need:
- A leased line
- Strong service levels
- A backup broadband connection
- Automatic failover
- A managed firewall
- High upload capacity
A small branch may need:
- Full Fibre business broadband
- A managed router
- 4G or 5G failover
- Secure cloud access
A temporary site may need:
- A mobile router
- Multi-network connectivity
- Temporary Wi-Fi
- A clear transition plan
A contact centre may require:
- Dedicated bandwidth
- Strong voice quality
- Resilience
- Provider-level call continuity
The connection should reflect:
- Number of users
- Applications
- Voice and video use
- Customer impact
- Criticality
- Location
- Available services
- Budget
- Growth plans
Traditional private networks or internet-based connectivity?
Multi-site networks have traditionally used private circuits to connect offices.
Cloud applications and modern security models have changed the available options.
Private connectivity
Private circuits may provide:
- Controlled routing
- Predictable performance
- Separation from the public internet
- Site-to-site communication
- Centralised access to business systems
They may also create:
- Higher cost
- Longer installation times
- Dependence on central locations
- Complex provider contracts
- Limited flexibility
Internet-based connectivity
Modern internet connections can be combined with:
- Encrypted VPNs
- SD-WAN
- Cloud security
- Local internet access
- Managed firewalls
This may provide:
- Lower cost
- Greater provider choice
- Faster site deployment
- Easier cloud access
- More flexible resilience
The correct design may use private and internet-based services together.
Key multi-site networking technologies
What is a Wide Area Network?
A Wide Area Network, usually shortened to WAN, connects networks across different locations.
Your office network is normally called a Local Area Network.
The WAN connects those local networks to:
- Other offices
- Data centres
- Cloud applications
- The internet
- Remote employees
A WAN may use:
- Leased circuits
- Internet connections
- VPNs
- SD-WAN
- Mobile networks
- Private provider networks
The design affects how employees reach applications and how faults are managed.
What is SD-WAN?
SD-WAN stands for Software-Defined Wide Area Networking.
It uses software and centrally managed policies to control how network traffic moves between sites, cloud services and internet connections.
An SD-WAN solution may help an organisation:
- Use several connection types
- Prioritise important applications
- Switch between connections automatically
- Improve visibility
- Standardise site configuration
- Support local internet access
- Connect sites more quickly
- Reduce dependence on traditional private networks
- Manage performance centrally
For example, a site may have:
- Full Fibre as the main connection
- 5G as backup
- Microsoft Teams traffic prioritised
- Automatic failover when the main service fails
- Central security and reporting
SD-WAN is not one standard product.
Features, security and management vary between providers.
Is SD-WAN right for every business?
No.
SD-WAN may be valuable when:
- You operate several locations
- Sites use different connection types
- Cloud applications are important
- You need central visibility
- Resilience needs to improve
- You want faster site deployment
- Traditional WAN costs are high
- Traffic needs to be prioritised
- You need more consistent policies
A simpler managed VPN and firewall design may be enough when:
- You have only two or three small offices
- Most applications are cloud-based
- Site-to-site traffic is limited
- The network is straightforward
- Central monitoring already meets your needs
The technology should match the problem.
A complex SD-WAN platform can create unnecessary cost when the organisation needs only better broadband, firewalls and failover.
Site-to-site VPNs
A site-to-site Virtual Private Network creates an encrypted connection between networks at different locations.
It may allow employees to access:
- Shared servers
- Business applications
- Printers
- Telephone systems
- Network services
- Data-centre resources
A VPN can use ordinary business internet connections.
Its performance depends on:
- Internet quality
- Firewall capability
- Encryption overhead
- Routing
- Distance
- Provider networks
- Application design
A VPN that disconnects regularly may be affected by the internet service, firewall, configuration or changing IP addresses.
The complete path should be reviewed.
Private circuits
Private circuits connect specific business locations without sending general traffic through the public internet.
They may be appropriate when:
- Large amounts of data move between sites
- Applications are hosted centrally
- Consistent performance is required
- Security or contractual requirements favour private connectivity
- Sites depend heavily on one another
- Data-centre access is important
A private circuit may not include ordinary internet access.
Sites may still need separate internet connections.
Local internet breakout
Local internet breakout allows each site to access cloud and internet services directly.
Without local breakout, traffic may travel from a branch office to the head office before reaching the internet.
This can create:
- Longer routes
- Additional delay
- Dependence on the head office
- Pressure on central bandwidth
- Poor cloud performance
Local breakout can improve access to:
- Microsoft 365
- Teams
- Cloud applications
- Web services
- Software updates
It should be protected by suitable local or cloud-managed security.
Centralised internet access
Some organisations route all internet traffic through a central location.
This may provide:
- Central security controls
- Consistent internet filtering
- Easier logging
- Fewer public internet points
- Centralised management
It may also create:
- A central point of failure
- Additional delay
- High bandwidth requirements
- Poor cloud application performance
- Dependence on the data centre or head office
The design should reflect where applications now live.
Routing cloud traffic through a distant office may no longer provide the best performance or resilience.
Multi-site connectivity and key business services
Multi-site connectivity and cloud services
Many organisations no longer host their main systems in one office.
Employees may use:
- Microsoft 365
- Cloud finance systems
- CRM platforms
- Housing-management systems
- Cloud document storage
- Hosted Voice
- Cloud contact centres
- Online backup
- Software-as-a-Service applications
This changes network design.
Each site may need reliable direct access to cloud services rather than a permanent dependency on the head office.
The network should consider:
- Application location
- User location
- Internet performance
- Security controls
- Identity
- Resilience
- Monitoring
Multi-site connectivity and Microsoft 365
Microsoft 365 is designed as a cloud service.
Employees may access:
- Outlook
- Teams
- SharePoint
- OneDrive
- Business applications
- Security services
Performance can be affected when traffic is:
- Routed through distant offices
- Sent through overloaded firewalls
- Forced through old private networks
- Affected by poor local broadband
- Dependent on weak Wi-Fi
A modern multi-site design should give each office suitable access while maintaining security and management.
Multi-site connectivity and Microsoft Teams
Teams requires stable internet and network performance.
The design should consider:
- Local internet access
- Upload capacity
- Packet loss
- Delay
- Firewalls
- Wi-Fi
- Video meeting volumes
- Teams Phone
- Remote users
- Backup connectivity
Routing a Teams call from a branch office through the head office can add delay and create unnecessary dependency.
Where appropriate, each site should have a direct and properly secured route to Microsoft services.
Multi-site connectivity and Hosted Voice
Hosted Voice can support one communications platform across several locations.
Employees may use:
- Shared company numbers
- Internal extension calling
- Reception services
- Call queues
- Mobile applications
- Desktop calling
- Multi-site call routing
The network needs to support:
- Stable internet
- Low packet loss
- Suitable upload capacity
- Firewall configuration
- Backup connectivity
- Call continuity
A phone platform may be cloud-based, but the quality of each site's connection still matters.
Multi-site connectivity and contact centres
A multi-site contact centre may involve:
- Agents in several offices
- Remote employees
- Central call queues
- Cloud CRM
- Call recording
- Analytics
- Web chat
- Customer systems
The network design should avoid creating one fragile dependency.
Possible continuity options include:
- Agents working from another site
- Remote working
- Provider-level call rerouting
- Backup internet
- Multiple cloud access paths
- Distributed teams
Multi-site connectivity and key business systems
Multi-site connectivity and shared servers
Some organisations still host servers at a head office or data centre.
Branch sites may depend on the WAN to access:
- Files
- Databases
- Specialist applications
- Printing
- Authentication
- Remote desktops
The design should consider:
- Bandwidth
- Delay
- File size
- Application sensitivity
- Server location
- Backup
- Site resilience
- Cloud migration plans
An application designed for a local network may perform poorly across a slow or high-latency connection.
The answer may involve improving the connection, redesigning the application delivery or moving the system closer to users.
Connecting offices to a data centre
A data centre may host:
- Servers
- Backups
- Private cloud systems
- Security services
- Telephony
- Business applications
Connectivity options may include:
- Private circuits
- Site-to-site VPNs
- SD-WAN
- Cloud connections
- Dedicated internet
- Diverse routes
The service should reflect:
- Application criticality
- Data volume
- Recovery objectives
- Security
- Data-centre provider options
- Site resilience
Connecting sites directly to cloud platforms
Some organisations need dedicated or controlled connections to cloud environments.
This may support:
- Predictable performance
- Private access
- Large data transfers
- Security policies
- Hybrid cloud systems
- Business continuity
The design may involve:
- Cloud gateways
- Provider interconnects
- VPNs
- Dedicated cloud access
- SD-WAN
- Data-centre connectivity
Not every business needs a dedicated cloud circuit.
Many organisations can use properly managed internet connections securely and effectively.
Multi-site security and management
Multi-site firewalls
Each location may need a firewall to protect local internet and network access.
A managed multi-site firewall approach can provide:
- Consistent security policies
- Central administration
- Site-to-site VPNs
- Web filtering
- Network segmentation
- Application controls
- Remote access
- Logging
- Failover
- Firmware management
Using different firewall brands and configurations at every site can increase support complexity.
Standardisation can make changes, updates and troubleshooting easier.
Multi-site cybersecurity
A multi-site network increases the number of internet connections, devices and access points that need protection.
Security should include:
- Managed firewalls
- Network segmentation
- Multi-factor authentication
- Secure remote access
- Supported firmware
- Central logging
- DNS filtering
- Web filtering
- Endpoint protection
- Supplier access controls
- Incident response
- Backup connectivity
- Physical security
A small branch should not become an easy route into the wider organisation.
Security standards should apply consistently across locations.
Multi-site monitoring
Central monitoring can provide visibility of:
- Connection status
- Router health
- Firewall status
- Bandwidth use
- Packet loss
- Delay
- VPN status
- Failover
- Mobile-data use
- Wi-Fi
- Device availability
This can help identify:
- A complete site outage
- Repeated short disconnections
- Capacity pressure
- Failing equipment
- Backup activation
- Unusual traffic
- Persistent provider problems
Monitoring should be supported by an agreed response process.
Network documentation
A multi-site network should be documented clearly.
Records may include:
- Site name
- Address
- Primary connection
- Backup connection
- Provider
- Account number
- Circuit reference
- Contract date
- Router
- Firewall
- Static IPs
- VPNs
- Network ranges
- Wi-Fi
- Support contacts
- Critical applications
- Escalation process
Without documentation, routine faults and changes take longer.
Information should be updated when sites, suppliers or equipment change.
Multi-site connectivity and internet failover
Every important site should have a documented response to connectivity failure.
Possible backup services include:
- A second fixed broadband connection
- 4G
- 5G
- A second leased line
- Another provider
- A wireless service
- Another office
- Remote working
The correct design depends on:
- Site importance
- Number of users
- Voice dependence
- Customer impact
- Mobile coverage
- Required applications
- Budget
A small branch may use 5G failover.
A contact centre may require two fixed services with stronger diversity.
Multi-site network operations and management
Network segmentation across several sites
Segmentation separates users and devices according to their function.
Networks may be created for:
- Employees
- Guests
- Business phones
- CCTV
- Building systems
- Servers
- Printers
- Payment devices
- Contractors
- Connected devices
Consistent segmentation across sites can improve security and support.
The design should still reflect local needs.
A warehouse, office and customer-service centre may require different network structures.
Multi-site Wi-Fi
Employees expect a consistent wireless experience across offices.
A managed Wi-Fi design may provide:
- Common network names
- Consistent authentication
- Guest access
- Central management
- Roaming
- Usage visibility
- Security policies
- Remote configuration
Employees should be able to visit another office and connect without asking for a different password or using an unapproved network.
Coverage still needs to be designed for each building.
Centralised management
Central management can make it easier to:
- Update firewall policies
- Configure VPNs
- Add new sites
- Apply security settings
- Monitor connectivity
- Change Wi-Fi
- Review performance
- Manage failover
- Remove closed locations
- Standardise documentation
It can also reduce the need for local employees or contractors to make technical changes.
Contract and supplier management
Multi-site organisations may have many connectivity contracts.
Common problems include:
- Different renewal dates
- Automatic extensions
- Unknown notice periods
- Charges for closed sites
- Duplicate services
- Old routers
- Unused mobile connections
- Provider details held by former employees
A central contract register can help record:
- Service
- Site
- Provider
- Start date
- End date
- Notice period
- Monthly cost
- Installation charges
- Support level
- Owner
- Replacement plan
Consolidation may simplify support.
It should not remove useful network diversity without careful review.
Multi-site connectivity resilience
Automatic failover between connections
A managed router, firewall or SD-WAN device can move traffic to another connection when the primary service fails.
Failover should consider:
- Detection time
- Switch-over time
- Which traffic is allowed
- Backup capacity
- Static IP changes
- Active calls
- VPN reconnection
- Return to the primary connection
- Monitoring
- User communication
Failover should be tested at every relevant site.
A backup service that has never been tested may not work when the primary connection fails.
Different providers and network diversity
Using different providers may improve resilience.
It does not guarantee physical separation.
Two services may still share:
- The same underground duct
- The same exchange
- The same building entry
- The same local infrastructure
- The same power
- The same router
- The same firewall
For critical sites, the design may consider:
- Different carriers
- Different technologies
- Separate entry routes
- Fixed and mobile connectivity
- Separate routers
- Separate power protection
True diversity should be confirmed rather than assumed.
Multi-site business continuity
A connectivity failure should not automatically stop the entire organisation.
Continuity options may include:
- Backup internet
- Alternative offices
- Cloud applications
- Remote working
- Mobile applications
- Call redirection
- Secondary data centres
- Local offline procedures
- Emergency contact methods
The plan should identify:
- Critical sites
- Critical applications
- Maximum acceptable downtime
- Minimum backup capacity
- Who declares an incident
- Who communicates with employees
- How services are restored
- How the incident is reviewed
Connecting remote and temporary sites
Temporary or remote locations may not have suitable fixed connectivity.
They may use:
- 4G routers
- 5G routers
- Multi-network SIMs
- External antennas
- Temporary Wi-Fi
- Satellite or specialist services
- Secure VPNs
- SD-WAN appliances
Possible locations include:
- Construction sites
- Project offices
- Community locations
- Events
- Temporary accommodation
- Emergency workspaces
- Pop-up branches
The solution should consider:
- Signal
- Data usage
- Power
- Security
- Number of users
- Voice and video
- Equipment protection
- Deployment time
- Removal process
New-site connectivity
A new site should not be connected as an isolated project.
The design should follow the organisation's wider standards.
The process may include:
- Availability checks
- Primary connection
- Backup service
- Router
- Firewall
- Wi-Fi
- Structured cabling
- Network segmentation
- Site-to-site access
- Cloud access
- Hosted Voice
- Monitoring
- Documentation
- Support handover
Connectivity should be ordered early.
Leased lines and building permissions may take several months.
Temporary services may be required.
Office moves and closures
Moving or closing a site affects more than the internet circuit.
The project should consider:
- Existing contracts
- New-service installation
- Number migration
- Firewalls
- VPNs
- Static IPs
- Wi-Fi
- Business phones
- Connected devices
- Supplier access
- Equipment recovery
- Data deletion
- Service cancellation
A closed site should not continue generating charges or maintain access to the business network.
Third-party and supplier access
External suppliers may need access to:
- Building systems
- CCTV
- Specialist applications
- Servers
- Customer systems
- Network equipment
Access should be:
- Approved
- Restricted
- Logged
- Time-limited where appropriate
- Protected by strong authentication
- Removed when no longer required
- Limited to the necessary systems
A supplier maintaining one device should not receive unrestricted access to the whole multi-site network.
Multi-site connectivity for different sectors
Accountancy firms
Accountancy firms may use several offices to support clients across different regions.
They may require:
- Consistent Microsoft 365 access
- Cloud accounting systems
- Hosted Voice
- Video conferencing
- Secure file access
- Shared reception services
- Remote working
- Reliable client meetings
A centralised network should not force every cloud connection through the head office unnecessarily.
Client confidentiality and resilience should guide the design.
Housing associations
Housing associations may operate across head offices, local offices, customer-service centres, community facilities, housing developments, concierge locations and remote sites.
Connectivity may support:
- Housing-management systems
- Repairs services
- Tenant contact
- CCTV
- Door entry
- Hosted Voice
- Microsoft Teams
- Connected devices
- Contractor access
A customer-service centre may need a leased line with strong failover.
A small local office may use business broadband and mobile backup.
Charities
Charities may operate from offices, community buildings and shared premises.
They may need to connect employees, volunteers, trustees, service-delivery locations, temporary projects and remote workers.
The design should balance:
- Cost
- Security
- Reliability
- Landlord responsibility
- Site lifespan
- Cloud application use
- Support
Temporary or grant-funded locations should not be tied unnecessarily into long contracts.
Professional services firms
Professional services organisations may need:
- Shared client systems
- Microsoft 365
- Video meetings
- Hosted Voice
- Secure remote access
- Multi-office reception
- Central security
- File sharing
- Business continuity
The network should provide a consistent experience without making every office dependent on one central building.
Construction and engineering
Construction and engineering organisations may need connectivity across permanent offices, project sites, temporary buildings, warehouses, remote facilities and vehicles.
Solutions may include:
- Leased lines
- Business broadband
- Mobile routers
- Multi-network SIMs
- Secure VPNs
- Temporary Wi-Fi
- SD-WAN
- Connected-device services
Sites may open, move and close frequently.
The service should be easy to deploy and remove while maintaining security and asset control.
Retail and customer locations
Retail and customer-facing sites may depend on connectivity for:
- Payments
- Booking systems
- Customer Wi-Fi
- CCTV
- Digital signage
- Cloud applications
- Hosted Voice
- Stock systems
- Staff devices
Even a small site may require strong backup when the connection supports payments or customer service.
Benefits of managed multi-site connectivity
Consistent user experience
Employees receive more reliable access across offices.
Central visibility
Connections, routers and faults can be monitored together.
Improved security
Firewalls, segmentation and policies can be applied consistently.
Better cloud performance
Sites can access cloud applications through more efficient routes.
Greater resilience
Primary and backup services can be designed around site importance.
Faster site deployment
Standard designs make new locations easier to connect.
Easier support
One team can coordinate providers, routers, firewalls and networks.
Better cost control
Unused services and unsuitable contracts can be identified.
Greater flexibility
Different connection types can be combined within one managed design.
What are the disadvantages of multi-site networking?
It can become complex
Several providers, circuits and technologies require clear management.
Different sites have different availability
The preferred service may not be available everywhere.
Resilience increases cost
Backup lines, routers and diverse routes require investment.
Legacy systems may need central connectivity
Older applications can limit modern network design.
Cloud and private traffic need different treatment
One routing model may not suit every application.
Supplier responsibilities can overlap
Fault ownership must be clearly defined.
Poor standardisation creates support problems
Too many device brands and configurations increase complexity.
Over-centralisation creates single points of failure
Routing everything through one office can reduce resilience.
Common multi-site connectivity mistakes
Giving every site the same connection
Different locations have different requirements.
Buying on speed alone
Support, upload performance, resilience and security also matter.
Routing all cloud traffic through the head office
This can reduce performance and create unnecessary dependency.
Installing backup without testing it
Failover should be proven before an incident.
Using two services that share the same route
They may fail together.
Allowing each site to choose its own router
Inconsistent equipment increases support and security problems.
Keeping undocumented VPNs
Unknown connections create operational and security risks.
Ignoring small branches
A small site can still provide access to the wider organisation.
Failing to remove closed sites
Old services, VPNs and accounts may remain active.
Choosing SD-WAN without a clear reason
Complex technology should solve a defined business problem.
Having no central contract register
Renewals and charges become difficult to control.
What should you look for in a multi-site connectivity provider?
Discovery and design
The provider should understand users, applications and site importance before proposing circuits.
Access to several connection types
They should consider broadband, leased lines, mobile services and private circuits.
SD-WAN and VPN knowledge
They should explain which approach fits your network.
Cloud understanding
The provider should understand Microsoft 365, Teams and cloud applications.
Security expertise
Firewalls, segmentation and supplier access should be part of the design.
Resilience planning
Backup services should reflect the impact of each site failing.
Central monitoring
You should have visibility across the full estate.
Installation management
The provider should coordinate carriers, landlords, engineers and local access.
Clear documentation
Every site, circuit and device should be recorded.
One support route
The provider should help coordinate the circuit, router, firewall and internal network.
Questions to ask before redesigning a multi-site network
- Which sites are business-critical?
- Where are our applications hosted?
- How much traffic moves between sites?
- Can cloud traffic access the internet locally?
- Do we still need private circuits?
- Would SD-WAN solve a clear problem?
- Which sites need leased lines?
- Which sites can use business broadband?
- What backup does each site need?
- Are backup services physically diverse?
- Which routers and firewalls are in use?
- Are security policies consistent?
- How are remote workers connected?
- Which suppliers have network access?
- What happens when the head office fails?
- How are new sites deployed?
- How are closed sites removed?
- Who monitors the network?
- Who owns carrier escalation?
- When do contracts renew?
Our multi-site connectivity process
1
Discovery
We begin by understanding:
- Number of sites
- Number of employees
- Site roles
- Critical locations
- Cloud applications
- On-premises systems
- Microsoft 365
- Hosted Voice
- Video conferencing
- Remote workers
- Security
- Business continuity
- Growth and closure plans
2
Existing network audit
We review:
- Internet connections
- Leased lines
- Private circuits
- Mobile services
- Providers
- Routers
- Firewalls
- VPNs
- SD-WAN
- Static IPs
- Wi-Fi
- Contracts
- Monitoring
- Support arrangements
- Documentation
3
Application and traffic review
We identify:
- Where applications are hosted
- Which sites use them
- Site-to-site traffic
- Cloud traffic
- Voice and video traffic
- Backup traffic
- Critical systems
- Performance problems
- Security requirements
4
Site classification
Sites may be grouped by importance and need.
For example:
- Critical hub site
- Large office
- Standard branch
- Small branch
- Temporary site
- Remote operational site
- Customer-facing location
Each type can have an agreed connectivity and resilience standard.
5
Solution design
We recommend the appropriate combination of:
- Leased lines
- Business broadband
- Full Fibre
- Mobile connectivity
- SD-WAN
- Site-to-site VPNs
- Private circuits
- Managed routers
- Managed firewalls
- Backup connections
- Local internet breakout
- Cloud access
- Monitoring
We explain the reason for each component.
6
Security design
We define:
- Firewall standards
- Network segmentation
- Site-to-site access
- Remote access
- Supplier access
- Guest Wi-Fi
- Logging
- DNS filtering
- Device management
- Administrative access
7
Migration planning
The migration plan may include:
- New circuit orders
- Router replacement
- Firewall changes
- VPN migration
- SD-WAN deployment
- Static IP changes
- DNS updates
- Cloud allow lists
- User communication
- Temporary connectivity
- Rollback arrangements
8
Installation and configuration
We coordinate:
- Carrier installation
- Building access
- Router deployment
- Firewall configuration
- Network changes
- VPNs
- SD-WAN policies
- Failover
- Monitoring
- Site documentation
9
Testing
Testing may include:
- Internet performance
- Site-to-site access
- Cloud applications
- Microsoft Teams
- Hosted Voice
- Video conferencing
- VPNs
- Firewall rules
- Backup connectivity
- Automatic failover
- Remote support
- Monitoring alerts
10
Ongoing support and review
Stratiis can continue to support:
- Circuit faults
- Carrier escalation
- Routers
- Firewalls
- VPNs
- SD-WAN
- Wi-Fi
- Performance
- Failover
- New sites
- Office moves
- Site closures
- Contract reviews
- Capacity planning
- Security changes
Frequently asked questions
What is multi-site connectivity?
Multi-site connectivity is the network infrastructure used to connect several offices, branches, remote locations and cloud services.
What is a WAN?
A Wide Area Network connects local networks across different locations.
What is SD-WAN?
SD-WAN uses centrally managed software policies to control how traffic moves across several internet or network connections.
Do we need SD-WAN?
Not necessarily.
It may be useful for organisations with several locations, mixed connections, cloud applications and resilience requirements.
A simpler VPN design may be enough for smaller networks.
What is a site-to-site VPN?
A site-to-site VPN creates an encrypted connection between the networks at two or more locations.
Is a VPN the same as a leased line?
No.
A VPN is an encrypted connection that may run across ordinary internet services.
A leased line is a dedicated physical or logical connectivity service.
Do all sites need leased lines?
No.
A leased line may be appropriate for larger or critical sites.
Smaller locations may use Full Fibre business broadband with suitable backup.
Can different sites use different providers?
Yes.
Different providers may improve choice and resilience.
The services should still be managed through a consistent design.
Can we connect sites using ordinary broadband?
Yes.
Business broadband combined with managed firewalls, VPNs or SD-WAN can support many multi-site networks.
What is local internet breakout?
Local internet breakout allows each site to connect directly to internet and cloud services rather than routing through a central office.
Is local internet breakout secure?
It can be secure when protected by properly managed firewalls, cloud security and network policies.
Why does Microsoft Teams work poorly at one office?
Possible causes include:
- Broadband quality
- Upload limitations
- Wi-Fi
- Firewalls
- Packet loss
- Inefficient routing
- Local network equipment
The site needs to be assessed end to end.
What happens if the head office connection fails?
That depends on the design.
Cloud-based sites with local internet access may continue working.
Sites dependent on head-office servers or central internet routing may be affected.
Can each site have backup internet?
Yes.
Backup may use a second fixed connection, 4G, 5G or another provider.
The design should reflect the site's importance.
Does using two providers guarantee resilience?
No.
The services may still share ducts, exchanges or building entry points.
Physical and network diversity should be checked.
Can failover happen automatically?
Yes.
Managed routers, firewalls and SD-WAN devices can switch to a backup connection automatically.
Can employees work from any office?
They can when identity, applications, Wi-Fi and network access are designed consistently.
Some specialist systems may still have location restrictions.
Can Stratiis manage routers and firewalls at every site?
Yes.
Stratiis can provide and support centrally managed routers, firewalls, connectivity and monitoring.
Can you help open a new office?
Yes.
We can coordinate connectivity, firewalls, Wi-Fi, structured cabling, business phones and wider IT requirements.
Can you help close a site?
Yes.
We can help remove network access, recover equipment, cancel services and update documentation.
How much does multi-site connectivity cost?
The cost depends on:
- Number of sites
- Connection types
- Bandwidth
- Leased lines
- Mobile services
- Routers
- Firewalls
- SD-WAN
- Private circuits
- Backup connectivity
- Installation
- Monitoring
- Support
A review of each location is normally required before accurate pricing can be provided.
Can Stratiis support several telecoms providers?
Yes.
Stratiis can coordinate multiple carriers where this provides better availability, pricing or resilience.
Connect every site without losing control of the wider network
A multi-site network should make it easier for employees to work together.
It should not leave every office with different equipment, different suppliers and different levels of reliability.
The right design may include leased lines at critical sites, Full Fibre at branches, mobile connectivity for temporary locations and managed failover across the estate.
What matters is that every connection forms part of one documented, secure and supportable strategy.
Stratiis can help you understand the network you have today, identify where risk and unnecessary cost exist, and build a clearer model for future sites.
Let's connect your offices, cloud services and remote teams through one managed network strategy.
