Resource Accounts in Microsoft Teams and how they affect Auto Attendants and Call Queues (new, maybe?)

April 26, 2019 1 comment

This might be one of those classic “Adam” moments. Maybe this has been this way and I’m only waking up to it now. That said, I have found in life, that if I have a question or a view, I’m usually not the only one who has it. So here goes.

 

Had someone bring this link up to me recently (HT to Randy, he’ll know who he is): https://docs.microsoft.com/en-us/microsoftteams/manage-resource-accounts

 

This link is all about Managing Resource Accounts in Microsoft Teams. No big deal right? We use Resource Accounts regularly for things like Rooms in Exchange, etc. In Skype for Business (On-prem or Online) or Teams, we create Resource Accounts for Room accounts as well. Guess what else needs a Resource Account now? Your Auto Attendants and Call Queues!

 

In the past, if you had purchased Phone System licenses, you were able to request and assign a certain number of Service Numbers within your tenant. Those could be assigned to Auto Attendants and Call Queues. This has changed (or is changing) to require each Auto Attendant or Call Queue to have a Resource Account created for them and then the kicker, if you want a phone number assigned, you have to assign an E1, E3, or E5, with the Phone System license and use either Direct Routing or assign a Calling Plan!

 

If you don’t need to assign a phone number, you simply need to create the Resource Account. You do not need to license the Auto Attendant or Call Queue if they will not have a phone number.

 

For some people this is not a big deal. If you have lots of Auto Attendants or Call Queues that have phone numbers assigned, this could have an impact on the Microsoft licensing that you need going forward.

 

It’s important to properly plan your deployment and this is a perfect example. Since we can nest Auto Attendants and Call Queues, not every one of them needs a phone number. Utilize this whenever possible.

 

The ultimate reason for this, I would guess, is that this is how an Auto Attendant or Call Queue will be enabled to dial out (i.e. when you want your afterhours Help Desk to forward to someone’s mobile device).

 

I really feel like I should have seen/known about this one but I’ll be honest, it snuck up on me. My MVP friends will all be like “don’t you remember hearing about this?” or something and give me a hard time, but it’s public now and hopefully, if you’ve read this far, you’ve found it useful information.

Advertisements
Categories: Microsoft Teams, UC

Speaking at ConvergeOne 2019 Iowa Tech Summit

April 8, 2019 Leave a comment

I’ll be speaking at the ConvergeOne 2019 Iowa Tech Summit in Des Moines on April 17th. I’m going to be talking on Microsoft Teams and it’s impact on Digital Transformation. Here’s a quick snippet on the topic:

Microsoft Teams is impacting the way companies work. From the mindset of Cloud First, Mobile First, Microsoft has established Teams as the hub for Collaboration. In this presentation, we will look at five ways that Teams is enabling Digital Transformation and give some thoughts on how it could impact your organization.

If you are in the area and would like to come join, you can register here.

Categories: Uncategorized

Microsoft Teams Tip Tuesday – Give more context!

December 18, 2018 Leave a comment

This tip is somewhat based on last week’s tip. When posting a conversation into a Microsoft Teams channel, give as much context as possible. If you are posting a link, tell what the link is about, don’t just post the link. Also, tag people if you want them to see it specifically. Many times, we post things in a Channel and it ultimately just becomes a large “junk” drawer of content. There is a lot of valuable information in the channel but we can’t find it easily. By giving context and tagging people, it becomes easier to search for the information.

Here’s a quick example. In the first image, I’ve posted a link to the channel but given no context.

Teams has gone ahead and given us a quick preview of the site but that’s it. We have no idea why this link is here. The same could apply to a file dropped into the channel as well.

Here’s a second example where I’ve given more context to the post:

You can see that I added a subject and I tagged the Demo Team and told them why they should pay attention to this awesome website.

By doing these things, when new members get added to the Team, they can search for content and be able to better discover Microsoft Teams Tips now.

Categories: Microsoft Teams

Microsoft Teams Tip Tuesday – Add a Subject to a Conversation

December 11, 2018 Leave a comment

This is one that has become pretty common to many of the Teams that I am a part of and I have seen it documented by a few others but felt like it needs more publicizing.

If you are starting a new conversation, add a subject to make it more engaging. This really helps if you have multiple conversations going on in a Channel. This is super easy to do. Right below the “Start a new converstation” where you would type, there is an icon that has an “A” with a pencil on it:

Now you will be presented with the ability to edit the subject field:

Bonus tip: Another thing about this mode, you can free form enter text and even craft paragraphs. When you hit the “Enter” key, you will get a new paragraph versus posting the text to the Channel.

Hoping to bring more of these types of tips in the coming weeks!

Categories: Microsoft Teams

Meetings location in Microsoft Teams

December 4, 2018 Leave a comment

I’m sure some of my blog readers remember back when OCS or Lync came out we’d get a brand new CHM file that we would comb over looking for what was new or changed. Everything at the time had that new tech smell. It was awesome. I’ll be honest, learning something new about a technology never gets old for me. This blog post is a perfect example of why. I was doing a walk-through of a presentation I was going to help with and the speaker had a slide in there that caught my eye. I literally said “wait, stop, go back to the previous slide!”. As I read it, my eyes were opened to something I didn’t know and it took me back to those days of reading the CHM for something new.

 

What caught my eye was this: A Microsoft Teams conference is hosted by Office 365 cloud in the same region where the first participant joined. Why is that such a big revelation? Cause in the on-premises world, that would never happen. In the on-prem world, we always knew that the MCU was based on the meeting organizer.

 

Why is this so fascinating to me? Well, think about it from a global perspective. If I have 10 folks invited to a meeting and let’s say that some are in the US and Some are in Europe. If a person in Europe is the first person to join, then the MCU will be in Europe.

 

Here’s a quick example:

 

 

This thought is why it is really important to plan your approach to Microsoft Teams appropriately. If you have centralized Internet or something that could delay a user getting on to the Microsoft network quickly, then it could have an impact on meeting quality. You can take a look here for the thoughts around preparing your network for Microsoft Teams: https://docs.microsoft.com/en-us/microsoftteams/prepare-network.

 

Something to note here, we are talking about the data in flight portion of the meeting only. The MCU is where all the media streams go to and get redistributed to the participants. We are not talking about the data at rest (i.e. meeting notes, attachments, etc.). That is all still kept safe and secure based on the meeting organizer’s location and tenant. This is important as we don’t want to cross security or governance boundaries.

 

If you want more info around the Meeting location, you can find the documentation to it here: https://docs.microsoft.com/en-us/microsoftteams/microsoft-teams-online-call-flows#principles. (HT to Bryan Nice for helping me find the specific link). Always stay learning my friends!

Categories: Microsoft Teams, UC

Comms vNext Thanks!

June 11, 2018 Leave a comment

By the time you read this, it will be Monday morning. I wanted to take just a moment to thank everyone who made Comms vNext 2018 possible.

First and foremost, I want to thank the community and everyone who showed up. Without the community and folks desiring an event like this, we would never have attempted it.

Second, I want to thank the speakers and the volunteers who worked tirelessly to make the day so special. In no particular order:

  • Jamie Stark
  • Doug Lawty
  • Jens Madsen
  • Alan Shen
  • Heidi Gloudemans
  • Kevin Peters
  • Brian Ricks
  • Anthony Caragol
  • Nick Smith
  • Laurie Pottmeyer
  • Allen Wat

I also want to thank Allison and Darphene at Microsoft who run the Denver office. They were amazing and so helpful for making sure we had what we needed for the event space.

Next, our sponsors. These folks stepped up to the plate and believed in what we were doing and helped bring the event to life. Many of them flew in straight from another conference and just kept going even though they were tired and worn-out. We never knew it because they brought a ton of energy and knowledge to the day.

Last and not least, my co-organizers. Josh, Pat, Jonathan, you guys were amazing. Everyone contributed and the creativity that flowed from all of you was fantastic. I believe all four of us were needed to pull this off. The way everyone helped and put forth ideas and made sure things got done while we all did our day jobs just showed what can be done as a Team.

Speaking of Teams, this entire event was planned via Microsoft Teams. Yes, you read that right. We met and discussed the event in Teams. There were probably 50+ iterations of the logo and shirts posted in threads. Teams made this event possible.

I thought the event was amazing. I hope if you attended, you do too. If you didn’t or couldn’t attend, please stay involved in the community and make sure your desire to see an event like this happen again is heard. We are listening and so is Microsoft.

If I forgot someone, please pardon me. So many people contributed. There was lots of advice given to us in the background and if I had to name everyone, it would be an endless list.

Thank you.

Categories: Uncategorized

The end of the road for Lync Phone Edition (LPE)

May 22, 2018 1 comment

Not sure if you noticed, but Microsoft made an announcement back around the Ignite time frame that they were going to disable TLS 1.0 and 1.1 in Office 365. Originally, they stated they were going to do this in March of 2018. Many of us wondered what impact this would have on Lync Phone Edition. Well, Microsoft thought about it, then decided to delay implementing the change until October 31st. When they moved the date, they confirmed that Lync Phone Edition would not be updated to support TLS 1.2 and that after that date, it would no longer work with Office 365.

Why would Microsoft do this? In the ever increasing world of threats, TLS 1.0 and 1.1 have known flaws. Many organizations (such as those in regulated industries such as securities) have policies stating that TLS 1.0 and 1.1 be disabled. Currently, Microsoft has said there are no known vulnerabilities in their implementation of TLS but it could be just a matter of time. Therefore, Microsoft is being proactive by disabling TLS 1.0 and 1.1 in Office 365. You can find out more about how to prepare for TLS 1.2 in Office 365 here: https://support.microsoft.com/en-gb/help/4057306/preparing-for-tls-1-2-in-office-365.

At this point, you may be wondering, does this affect me? You can ask yourself two questions:

  1. Do I have Lync Phone Edition devices?
  2. Do I use Office 365 (Such as Exchange Online or Skype for Business Online)?

If the answer to both of these questions is no, you are safe, for now. If you answered yes to the first question and no the second, you are ok unless your organization implements a similar strategy and disables TLS 1.0 and 1.1 and/or you need to call people from your Lync Phone Edition who utilize Skype for Business Online.

So, what can you do? Great question. You can upgrade your device to a Microsoft 3rd Party Interop Partner (3PIP) device. These devices are certified to work with Skype for Business and Skype for Business Online. Due to this certification, they will continue to work after Microsoft implements their change. Some of the partners are offering trade-ins.

My friends at AudioCodes are doing a “Trade-up” progam. You can find out more about at http://online.audiocodes.com/lpeupgradeprogram. I’ve been a big fan of the AudioCodes handsets. AudioCodes handsets have all the modern features such as Boss/Admin, resiliency, hot-desk support, and more. In addition, AudioCodes has their IP Phone Manager (IPPM) to manage the phones. IPPM gives you a lot more control over settings and firmware than we have in the native tools today.

As we look to the future, it’s good to know that the 3PIP certified phones will also continue to work after the change over to Microsoft Teams. These devices will be able to place calls and join Teams meetings.

Take the call to action and look for outdated devices on your network. I’ve been surprised at how many organizations I’ve spoken to recently that are still utilizing these devices. It’s awesome to know that they have had such a long life. Time to look to the future!

Categories: Uncategorized