Professional Documents
Culture Documents
Then along came unified communications (UC), a blurring of the boundaries, a move to have telephony
merged with instant messaging and other IT platforms. Many “UC” providers hailed from traditional
telephony backgrounds including Mitel, Avaya, Unify and Alcatel. Voice was very much at the core of UC.
Even new entrants to the UC market, such as Microsoft, positioned their Lync then Skype for Business
offerings as a specialist, dedicated telephony solution with some added extras such as presence, and
document sharing. But it remained a little detached from other IT business tools.
So where are we now? While unified communications remains current, collaboration is the new king.
True enterprise collaboration finally brings the worlds of voice, video, messaging, document sharing and
business application integration together into a single IT platform. What’s more, it’s cloud based and
offered on a subscription basis for ease of access and scalability.
This White Paper explores some of the issues at hand, and offers some
answers, with a specific focus on how enterprises can get collaboration
right by moving to Microsoft Teams, the application that has quickly emerged as the dominant enterprise
collaboration platform.
Microsoft Teams brings a fully integrated window to an organisation’s communication needs sitting
alongside their files and folders that can been worked on collaboratively with team members.
This has largely been achievable through Microsoft SharePoint, which is fundamentally the way that
files and folders are managed in Microsoft Teams. Each time you create a Teams Channel, it is in fact
created in SharePoint, when you add files to that Teams Channel they are uploaded to SharePoint.
Microsoft Teams doesn’t actually hold the data or information, in its simplest form it’s a gateway or
portal to all of the Online Services Microsoft offers to its customers in one place.
For enterprises considering migration to Microsoft Teams, the same principles apply as they did when
an organisation moved from legacy PBXs to Skype for Business. Interestingly it’s still important to follow
the same processes if moving from Skype for Business Server (on-premises) to Microsoft Teams. Every
enterprise must carefully evaluate and plan its users’ migration accordingly.
Additionally, the good news is that a migration can be done gradually. AudioCodes can provide the
necessary tools for the migration journey or indeed complete the migration for you with our Live for
Microsoft Teams managed service. The purpose of this White Paper is to provide some practical guidance
on how AudioCodes Live for Microsoft Teams enables such a migration.
This first stage in the process is to listen. We will run through a high-level set of questions so that we
can understand more about your business challenges, your existing technology, how you use it and any
other compliance, regulatory or 3rd party integrations that need to be considered. We will also help
you and your organisation understand the solutions we offer for Microsoft Teams and answer any
questions that you may have. Once we have completed the call, our consultant will fill out a CDQ with
all the information that you discussed.
1. What is the size of your organisation? The number of staff that your organisation has, the
number of offices/locations and any other remote office that requires inclusion.
2. Do you have a current UC solution in place, such as Microsoft Skype for Business or any other
UC solution or combination of products that you consider to be your UC solution?
3. What telephony solutions are you currently using across your sites? In our experience there
may be some unknowns, as most telephony solutions have grown organically, so whatever
information you can provide is massively helpful.
4. Do you have a Microsoft Office 365 account? Is your Active Directory replicated to Office 365?
Do you currently use Microsoft Exchange for your email solution? Is it part of your Office 365
environment?
As stated, these are just sample questions that our UC consultant will ask to ascertain what you currently
have and indeed if Microsoft Teams will fulfil your organisation’s requirements and expectations. You
will be provided a copy of the CDQ along with an initial proposal for the solution that our UC consultant
recommends for your organisation.
As an example, if after receiving a copy of the Customer Discovery Questionnaire, and you feel that an
important element has been excluded, we will run through the process again to ensure that we include
as much as possible that will have an impact or bearing on the outcome of the solution. Only then will
we move forward into the next phase.
• Network and Microsoft environments • Project Plans (Technical Delivery, • Training Delivery
• Site Audits / Surveys Communications & Training) • Number porting & User Migration
• Stakeholder Interviews • Test & Acceptance Plans • Floorwalking
• Champion building • Handover to Service
Organisational Readiness
By conducting an organisational awareness as part of the Discovery and Planning Workshops, we will
immediately identify any weaknesses within your organisation and where special attention needs to
be given. As part of this process AudioCodes will arrange interviews with stakeholders. Stakeholders
will also provide feedback about information and challenges that were previously unknown, which can
now be documented to ensure that nothing is missed or overlooked.
• Identify the key departments and service areas across the organisation
• Gain context around the role each department and service area play within the organisation
• Identify primary methods of communication that are used today
• Identify common interactions between departments (both internally and externally)
• Understand some of the key challenges that each area faces today
The information that is gained will be used in the Discovery & Planning Document, which highlights
areas that need special attention and further consideration. It also identifies roles and responsibilities
to ensure a successful project delivery.
Stakeholder Interviews
Stakeholder Interviews are an extremely effective series of workshops with the business stakeholders.
The purpose of the workshops is to understand the business unit and their objectives and associated
needs. It’s also an ideal opportunity to introduce the solution to a broader selection of users through
the business stakeholders.
This gives the opportunity for them to voice the pain points that they experience trying to conduct
their day-to-day jobs. In addition to the usual answers of phone, email, face-to-face meetings etc. it
will also uncover the wide use of “Shadow IT”, i.e. unauthorised applications, ranging from files being
shared using Google Apps, Dropbox, and Instant messaging using Messenger, WhatsApp etc.
This very simple step suddenly makes the workforce feel engaged and part of the process and that their
opinions help towards the end solution. Additionally, it feeds information back to the leadership team
on the organisation’s readiness to implement a Microsoft Teams solution.
It will also identify any additional training that will need to be delivered to ensure that all employees
are able to complete their tasks without being hindered.
User personas identify where someone works, how someone works, and what they need to communicate
effectively ensuring they have the right tools to complete their tasks.
Endpoint Selection
In addition to creating a list of user personas, AudioCodes will run a “Device Bar” – this in its simplest
form is a desk with a variety of devices which will be made available to employees once Microsoft
Teams is implemented. It’s also advisable to select a couple of devices per user persona.
Most organisations that transition to Microsoft Teams try to encourage their employees to use a headset,
but this can be a false economy over the lifetime of a solution. It is estimated that an organisation will
need 3 headsets per person over the lifetime of a solution, and a good quality headset can cost as
much as a midrange desk phone.
Headsets are seen as a personal device. For health reasons it’s not advisable to share headsets, whereas
desk phones can be reused if an employee leaves or is absent. Equally it’s impractical to take a desk
phone home each day in contrast to a USB headset.
A reputable USB headset will be bullet-proof in terms of reliability and can be plugged into most good
quality desk phones. Bluetooth devices are more expensive. They do typically have much more features
but if you have a large office they can cause significant congestion as they all transmit on the same
frequency. They are ideal though for a field-based worker, but here again their life expectancy is quite
low with a typical worker requiring a replacement device every 12 months.
After the completion of the workshop, you will be provided with two outputs.
Firstly, an executive summary, designed to explain the business challenges, how we can help address
those challenges with an outline project timeline and budget. This document is for the leadership team.
Secondly, the detailed discovery and planning workshop summary document, which provides all of
the detail and design elements as discussed at the workshop. This forms a plan of record for the IT /
technical team who have participated in the workshop.
Statement of Works
Providing that you are happy with the information that we’ve collated and the solution that we are
recommending, we will move forward to create a Statement of Works (SOW). The end of this phase
is a key “milestone”. A “Statement of Works” is created with the technical detail that’s required to
implement the solution. It contains information such as IP address ranges, phone number ranges etc..
Why should you consider a proof of concept for a product that is a part of the Office
365 suite? The answer lies in Microsoft Teams’ versatility. Running a proof of concept
allows you to explore those capabilities before you try and incorporate Microsoft Teams
into your organisation’s broader business workflows. It will also test any compliance,
regulatory or 3rd party integrations. Quite often a POC will uncover areas that had
not previously been considered and give time to rectify without disrupting the entire
business.
During the POC phase, your IT teams will also have time to consider some of the governance and
security controls which need to be established prior to full roll out.
Microsoft Teams is designed for quick, but persistent collaboration that puts the power in the hands of
your users to create teams, invite others (even those outside your organisation), add channels, apps,
data sources etc. The ease of use is one of its strengths, but it also means IT teams must walk a fine
line between leveraging the full capabilities of the platform and having the necessary governance and
controls in place.
As we provide Microsoft Teams voice solutions to our customers, quality assurance is critical in achieving
our goal of delivering “right first time”. Testing against all client’s requirements and driving the delivery
of high-quality code helps us to reduce User Acceptance Testing (UAT) effort and rework. Through the
scoping and planning phases, we ascertain the level and depth of quality assurance necessary and
tailor our QA efforts accordingly. During the project build phase, we focus solely on functional system
testing of the solutions developed.
As this is the last “milestone” it is essential that the UAT is successful. Once we have delivered the
solution and either handed over to the internal IT team or started up the managed service, the day-to-
day user assistance and system maintenance starts.
Summary
Enterprises are seeking to move away from separate AudioCodes Live for Microsoft Teams
telephony solutions to true collaboration platforms. provides a managed service to seamlessly
Microsoft Teams has rapidly emerged as the leading and fully voice-enable Teams.
platform for this given Microsoft’s dominance of the
business application arena.
For enterprises with a Microsoft Teams strategy, AudioCodes Live for Microsoft Teams provides
a managed service to seamlessly and fully voice-enable Teams. The core service includes Teams
Direct Routing connectivity, Microsoft tenant management, user lifecycle management, moves/add/
changes/deletes (MACD), plus integration with on-premises IT and legacy voice communications (PBX)
equipment to ensure a seamless migration. It can be deployed as a cloud, on-premises or hybrid model
depending on your preferred IT strategy. Per-user-per-month predictable pricing is ideal for budget
planning, and additional devices such as conference phones, IP phones, and analogue ports may be
added on a per-device-per-month pricing basis. AudioCodes Live for Microsoft Teams is the easy way
to bring productivity and collaboration to your enterprise.
To learn more about AudioCodes Live for Microsoft Teams and talk to a UC consultant, please visit this webpage:
https://liveteams.audiocodes.com/
International Headquarters AudioCodes Inc. Contact us: www.audiocodes.com/contact ©2022 AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP,
HD VoIP Sounds Better, IPmedia, Mediant, MediaPack, What’s Inside
1 Hayarden Street, 200 Cottontail Lane, Website: www.audiocodes.com Matters, OSN, SmartTAP, User Management Pack, VMAS, VoIPerfect,
Airport City Suite A101E, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One
Voice, AudioCodes Meeting Insights, AudioCodes Room Experience
Lod 7019900, Israel Somerset NJ 08873 and CloudBond are trademarks or registered trademarks of Audio-
Tel: +972-3-976-4000 Tel:+1-732-469-0880 Codes Limited. All other products or trademarks are property of their
Fax: +972-3-976-4040 Fax:+1-732-469-2298 respective owners. Product specifications are subject to change without
notice.