Teams Migration and Implementation

VIA UC Platform – Using Microsoft Teams for Calling




Microsoft Teams is now available as an endpoint on the VIA UC Platform. This means that you will have the option to use Teams for your calling instead of Skype for Business. VIA began rollout shortly after our Teams Launch Event in May. The migration of organisations to Teams will be subject to the availability of resource within the relevant teams at VIA on a first come, first served basis. Please inform your account manager of your intention to migrate to Teams and your desired time frame, as early in this process as possible.


Choosing the best endpoint for your organisation


VIA is working to enhance the native feature set found within Microsoft Teams with our sophisticated call routing and contact centre offering. To assist with choosing the best endpoint for your organisation, we have written a feature comparison which is available at the link below. Please ensure you have read and understood the differences between the two available options before proceeding to migrate to teams. We're always available to help, please contact your account manager if you'd like to discuss this further.



Please click here to see a feature comparison between VIA UC Skype for Business, VIA UC Teams, and MS Teams Online.


There are a number of other considerations in your decision-making process which are outlined below:

  1. Understanding and acceptance of feature list
  2. Any user who will require a phone number with VIA will need a ‘Phone System’ License in 365. This is payable directly to Microsoft as part of your 365 licensing terms.
  3. Any user who will need ‘Phone System’ (required for integration with VIA UC Platform) will require an E1, E3 or E5 license in 365; lesser licenses will not function.
  4. A new domain will be created within your 365 environment {}
  5. VIA will require one permanent user to be licensed in 365 in order for integration to function. The monthly cost of this is around £12 (subject to change by Microsoft). None of this cost comes to VIA, this is an additional Microsoft cost. teamsdrenablement@{}
  6. Should either point 4 or 5 be removed or unlicensed in the future, VIA integration will cease to function with immediate effect.
  7. Support is only provided for PSTN calling elements and VIA UC Portal elements. i.e installation of, logging into, and other features within Teams are not supported by VIA; only external calls, and features of VIA UC Portal.
  8. Split deployment of Skype for Business and Teams is supported in the following circumstances only:
    • Skype for Business & Teams operate in “ISLANDS” mode
      • There is no interoperability
    • Calls, once answered, cannot be transferred between Teams/ Skype for Business clients
    • Teams and Skype for Business clients can be mixed in Ring Groups and Call Queues, however, above transfer limitation still apply
    • External federation (ability to communicate with other domains) is performed by a single solution (either Skype for Business or Teams), not both.
    • Split environments are recommended for testing and migrations only. Unexpected system limitations discovered in a live environment may not be resolved.
  9. In order to setup VIA UC Platform integration with Teams, we require global admin credentials to your Office 365 Tenant.
    • This will be captured online in an application built by VIA. Credentials will be hashed and at no point seen by any individual humans at VIA.
    • Use of the domain admin credentials will be for scripting the integration piece between the two systems and in order to make ongoing necessary changes such as phone number assignments.
    • Once the initial setup is complete, we will maintain administrative privileges to your 365 tenant for the administration of dial policies, but the account which is setup as global administrator can be downgraded to a phone system admin.
    • Should you not wish to provide this level of access, you may either:
      • Wait until Microsoft finish plans to give partners the ability to have administrative access by module, and grant us access to create domains, users, and configure Teams and Phone System.
      • Work with us to enter credentials at appropriate points during the onboarding process and every future change. This will remove our ability to script the steps required and mean this has to be achieved manually. Where this is the case, professional services charges will need to be quoted in addition to any other costs already agreed, as well as mutually convenient times scheduled for the work to go ahead manually.
  1. You must not have any Skype for Business attributes synced to Office 365 (msRTCSIP).
    • These would only be implemented if you have previously had your own Skype for Business On-Premises server at a time in the past (customers using VIA UC Platform or Skype for Business online are unaffected).


Migration Plan


Below, we list the draft migration plan for a customer currently using Skype for Business on VIA UC Platform:

  1. Ensure the customer is aware of the functionality that will be lost.
    • Make sure users who will have "Phone System" have E1, E3 or E5 licenses.
  2. Ensure the customer is aware of any downtime
    • To be confirmed in the final migration plan
  3. Customer to navigate to VIA Teams migration portal and input credentials for Office 365 domain admin.
  4. Run Stage 1 migration scripts.
  5. Complete tasks in Office 365 portal.
    • Click "Complete Setup".
  6. Wait 24 hours.
  7. Run Stage 2.
  8. Wait 24 hours.
  9. User will see completion is successful in the VIA Teams portal, as below:


  1. From this point, any changes are service affecting.
  2. Upgrade a test user and customer to test.
  3. Add "Phone System" license to each user and ensure each user has E1, E3 or E5.
  4. Run Stage 3
  5. OOH: Change DNS, change VIA Portal Licenses.





Changes in costs associated with VIA licensing and additional costs from Microsoft can be discussed with your account manager at the start of this process.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request