Microsoft Teams

Microsoft Teams handles chat, meetings, calls and file collaboration. LIMA can help you deploy it deliberately, govern it so it stays usable, and move your telephony onto Teams Phone so you are not paying for a separate phone system.

Rapid adoption, slow optimisation

Teams arrived in most organisations at speed and governance came as an afterthought. A team for every project and department. Each one created a supporting structure in SharePoint, and deleting the team does not clear that structure away.

The result is sprawl. Hundreds of teams with unclear ownership, maze-like file structures, and permissions that haven’t been regularly reviewed. Many organisations are also still paying for a redundant phone system while running every meeting through Teams.

Teams governance, applied deliberately

Teams sits on top of SharePoint and Microsoft 365 identity, which means a Teams deployment is really a data and access project wearing a friendly interface. We treat it that way. Naming conventions, ownership, lifecycle and expiry policies, guest access rules, retention and external sharing controls all get set deliberately, so the environment stays manageable as it grows.

Where sprawl has already taken hold, we can find the orphaned teams and the SharePoint structure sitting behind them, and archive or remove what is no longer needed without disrupting the people still working.

Teams Phone and cloud telephony

Teams Phone can replace a traditional PBX outright, putting your business number on the same app your people already use for meetings and chat. There are three routes to the public telephone network.

Which one fits depends on your existing contracts, your call volumes and how many sites you are covering. LIMA can help you make the most efficient choice, port your existing numbers across, and manage it afterwards.

 Microsoft is your carrier. Numbers and minutes come from Microsoft and everything is managed in the Teams admin centre. The quickest to set up.

You choose a Microsoft-certified carrier who provides the numbers and runs the infrastructure. No session border controller to buy or maintain, and the carrier owns the pricing and SLAs.

You bring your own carrier and SIP trunk through a session border controller. The most flexible option, and usually the answer where legacy PBX systems, analogue devices or specific call routing are involved.

The benefits

Governance

Naming, ownership, lifecycle and expiry policies applied from the start, so the environment stays usable rather than becoming something people work around.

Teams sprawl cleared up

We identify orphaned teams and the SharePoint structure sitting behind them, then archive or remove what is not needed.

One phone system, not two

Teams Phone replaces a traditional PBX, with the right connectivity route chosen for your contracts, your call volumes and your sites.

Calls from anywhere

A business number that works on a laptop at home, a mobile on the move or a desk phone in the office, with the same call handling wherever your people are.

Why choose LIMA for Microsoft Teams

Teams touches identity, data, security and telephony at the same time. We cover all four, so the decisions get made together rather than by four different suppliers.

Trusted by

See our latest customer stories

Take the first step on your journey with us