Wednesday, 20 September 2017

New name for Skype for Business Online/Teams?

Hello Readers.  Hope you're well.

A really quick one today.

I was having a look around the Azure AD portal in my Office 365 tenant and found a section for Enterprise Applications and Microsoft Teams was listed.  In there, I found Provisioning and a provisioning mode which has a drop down list with a single option of Manual.

The interesting thing is the nomenclature they use for the product.  Something I haven't seen before.  But given the recent slip up that told the world that Skype was being replaced by Teams, I am not surprised.

Here's a screenshot of the page.

As you can see, they refer to the product as Skype Team Services.  Is this the new name for the mashup of Skype for Business Online and Teams in Office 365?  I guess we'll find out in the next few days.

If you have seen this or similar in Office 365, leave a comment and feel free to reach out.

That's all folks.


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.  

Tuesday, 19 September 2017

How to change the display name of a guest in Microsoft Teams

Hello Readers.  Hope you're well.

Another quick post.

Microsoft has enabled external Guest access in Teams.  And I know you've all been frantically adding guests to your teams.  

I'm a guest in a couple of teams of like-minded individuals.  One of the biggest complaints is the display name.  When you add a guest to a team in Teams, the display name is the alias of the User Principal Name (UPN) by default.  

I explain in a previous blog post that it is possible to specify the display name before the invite goes out.  In this post I'll go through the ways you can change the display name of your guests after the invite goes out and they've already accessed your team.

There are two ways to do this.  I'll start with the quickest and easiest.  PowerShell.

First, you need the pre-requisites for connecting to Azure AD in PowerShell.

1. You need the Microsoft Online Services Sign-In Assistant for IT Professionals RTW.  Download the version you want and install.

2. Next, you need the Azure Active Directory PowerShell Module.  Download the .msi file, and click Run to run the installer package.

Change the display name of a guest using PowerShell

1. First, open PowerShell as an Administrator

2. Now type Connect-MsolService and enter your admin credentials when prompted.

3. Now enter Get-MsolUser -All | where {$_.UserType -eq "Guest"} to see a list of your guests.

If you know the UPN of the guest you want to display you can do a search:
Get-MsolUser -SearchString "randy.chapman"

4. To change the display name you can simply copy the UserPrincipalName from the results above and run the following command: 
Set-MsolUser -UserPrincipalName -DisplayName "First Last (Company)"
You also have a some more options here to make it a little easier.

You can assign a variable to use in the Set-MsolUser command.
$guest = Get-MsolUser -SearchString "randy.chapman" | select -expandproperty UserPrincipalName

Then you can insert the variable to make the change.
Set-MsolUser -UserPrincipalName $guest -DisplayName "Randy Changed"

Now if you look up the user you changed, you'll see the new display name is shown.

In addition to the Display Name, you can also set loads of other parameters such as FirstName, LastName, Title, PhoneNumber and various address fields.  All good, but your users won't see that info in Teams anyway.  

Remove or disable a guest in PowerShell

You can also use PowerShell to remove a guest or disable them without removing them.

To remove, enter: 
Remove-MsolUser -UserPrincipalName
To disable without removing, enter: 
Set-MsolUser -UserPrincipalName -BlockCredential $True
This is the PowerShell Equivalent of the Block Sign In, in the Azure AD admin portal.

As I said at the beginning of the post, there is another way to do this and that is in the Azure AD admin portal.

Change the display name of a guest in the Azure AD Admin portal

1. First, Sign in to Office 365 Admin portal at

2. Click on the Admin Tile

3. Scroll Down and expand Admin Centres and click on Azure AD

4. Now click on Users and Groups -> All Users -> click on the user you want to edit 

5. Click on Profile 

6. Enter the new Display Name in the Name field and click Save

You can change multiple settings and even set a photo.  Again, none of this will be visible in Teams, so I wouldn't bother.

Some important notes

I discovered that if you set a First Name and Last name, that is displayed in Teams rather than the DisplayName.

You won't see the guest user display name changes until you completely log out of Teams and then log back in.  Switching teams isn't enough.

That's all folks.


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.

How to specify the display name for a Guest member in Microsoft Teams

Hello Readers.  Hope you're well.

A very quick post this time.  

As you know by now, Microsoft has enabled external Guest access in Teams.  I have a big post here.  Like you, I have been doing a lot of testing with this feature.  It's been live for a week or so and the initial bugs have seemingly been ironed out.  

There seems to be mixed feelings among members of the community about how it works and some thinks about the experience and I'm sure Microsoft is listening.

One of the most annoying features is that when you add a guest to a team in Teams, the display name is the alias of the User Principal Name (UPN) by default.  This is especially annoying when the alias is first name only.  Your guest will be displayed by first name, and in lowercase!  e.g. luke (Guest) has been added.  Really helpful when you know a lot of people with the same first name.  Marginally better when the alias is first.last.  But then you get (in lowercase) luke.skywalker (Guest) has been added.  Worse still when the alias is some random combination of parts of first or last name.  e.g. lskywalker or lukesky.

That is, unless you change it.  There are a couple of ways to do this.  

One is after you send the invite.  You can change the display name in Azure AD in the Office 365 admin portal or in PowerShell (Post coming later).

Or, you can change it before the invite is sent!  Hooray!

Once you've enabled your tenant for Teams Guest access and all that, you can add a member as normal by typing in the email address of the guest.

Once the email address is verified by Teams to be a valid Office 365 Azure AD email address, it will be displayed below.  Click on it.

Now click the little pencil.

Now you can edit the guest information.  Change the display name to whatever you want and click on the tick to make the change.

Once you've accepted the change it will be displayed as you specified, with (Guest) at the end.

Now click Add to add the guest account.

And close to send the invite.

Now when you log into your team and view the members, you'll see the guest you just added has the display name you specified.

You will also see the display name in conversations with the guest.

That's it for now.  


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.  

Monday, 11 September 2017

How to enable external guest access in Microsoft Teams

Hello readers.  I hope you're well.

This is a quick post on a new feature added today to Microsoft Teams.  It is one of the most anticipated and popular features with (at time of writing) 5,999 votes on Uservoice.

The feature is External Guest access.  This first iteration of guest access allows team owners to add or, more precicely, invite external users with an Azure AD account as a member of a team.  This will send an email invitation to the guest inviting them to access the team.

For now, only users who have an email address corresponding to an Azure Active Directory or Office 365 work or school account can be added as a guest user.  Microsoft will be expanding this to users with MSO accounts (like or

Before your users can add guests, you need to enable guest access in the tenant admin.

To turn on guess access for Microsoft Teams

1. Sign in to Office 365 Admin portal at

2. Expand settings and click on Services & Add-ins.  

3. Now select Microsoft Teams to open the Microsoft Teams side bar.

4. Under Settings by User/license type, select the user type you want to configure click on the drop down list and choose Guest.

5. Now flip the toggle next to Turn Microsoft Teams on or off for your entire organization to the On position and then click Save at the bottom.

6. To enable the full Microsoft Teams guest access experience, Office 365 admins need to select On for the following settings:
How to invite external guests
Once everything is enabled, users will be able to add external contacts in the same way they currently add internal members.  The below Gif shows how.


Adding a guest is as easy as searching for the contact by email address.

1. Click on the menu (three dots) next to a team you want to manage, then add members.

2. Then type an email address of an account that has Azure AD (i.e. someone with an Office 365 account).  Doesn't matter if they've never used Teams, it will invite them to start.  More on that later,

3. If it finds a valid account, it will display below the search bar.  Click on that account.

4. Then click Add

5. Then click Close.

What happens now is that the guest account you've invited gets added as a guest account in your Azure AD.

From here, you can view and even edit their profile.  You can even block sign in directly from here.  

You can also view members and see what you can do.

Click on the invite
Once you enable and add a guest the user will receive a welcome email similar to those when you send a chat to users that haven't used Teams.  

The guest must redeem the invitation by clicking on the link in the email before they can get access to the team and the channels therein.

Open Teams
When the user clicks on the invite it takes the user to Teams on the web and (because I have the Teams app) asks whether to open Teams or to use the web app.

I used the Teams app.  Once you click on open the app, you'll get a popup in Teams asking if you want to switch accounts.

Switch accounts
This basically logs you out of Teams and then back in.  At this point it adds the additional tenant context so you can switch between your primary account and your guest account.

In order to do anything with the person that invited you, you need to switch from your primary/company account to the guest acccount.  You can't be in both accounts at the same time.  You are literally logging out of your tenant and in to the guest account you've been given on the Office 365 tenant of the person that invited you.  Switching accounts takes about 10 seconds.

I have only added a single account, but I assume, as you get invited to more teams, your account list will grow.

First time logging in as a guest
The first time you log in to the guest account you get a slide show.

Followed by a video which lasts about 2 minutes.

The video is a quick tour of Teams.  Click here to watch if you haven't seen it.

Once you're in you will see the team you've been invited to, any channels and tabs, conversation history, files.  Everything.

You'll also be able to communicate directly with the person that invited you.  This includes one to one chat, audio and video.

Calling and video only works between users logged into the full client.  I tried both directions and the call starts and ends a second later.  From the full client it just ends with no explanation.  From the web it displays a warning that the feature isn't yet available in the web and it invites you to download the app.

Calling from the app to the person logged into the web app generates a missed call notification.

The chat experience between clients is as you'd expect if you've chatted in Teams.  Calling and video is also very good as you'd expect.

Meetings with guests
The only thing you don't get is meetings between users and guests.  The meeting section is missing from the guest experience.  

I tried inviting a guest to a meeting and it allowed me to in Teams, but I got an NDR email.

The NDR says "Your message to couldn't be delivered. wasn't found at
So, 1. Teams doesn't really know how to invite a guest, and 2. Meetings are internal only, for now.  Shame it actually let me generate and send the invite.  If I were an uninitiated end user it would confuse me.

Capabilities of Guest Users in Teams
Guests have a subset of capabilities of internal users.  All in all, not a bad list.  Although I would question a couple of them.  Do guests need to be able to create a channel in someone else's team?  Maybe, but be wary.  And really they shouldn't be able to create policies or invite new guests, surely.  I'll let you decide.

Team Owners can also tweak some of the permissions.   

Click on the menu (3 dots) -> view team -> Settings ->@ expand Guest permissions.

It is possible to control guest access to Office 365 Groups (the backbone of Teams) using PowerShell.  Click Here.

Licensing required
No additional licenses are required.  Guest access is included in Office 365 Business Premium, Enterprise and Education subscriptions.  This is excellent news.  All three organisation types will surely have a requirement to add guests.

What do I think?
I'm glad you asked.  I am mindful that this is the first iteration of guest access.  I hope/assume it will get better.  It needs work, however.

The above paints a picture that the whole process is easy.  There are several things to change as an admin, but they are actually pretty straightforward.  Log in, tick some boxes and wait.  

My Real Experience
The invite was delivered within a few minutes (at most).  I clicked on the link and follwed the prompt to switch accounts.  The first time I did this it took me back to my primary account.  I couldn't see the your accounts section.  I logged out and back in and actually got a warning taht my account wasn't enabled by my admin.

I clicked try again several times and got teh same thing.  I tried to sign out and back in and the same.  At this point I restarted my PC and tried to log back in.  It was only at this point that I got prompted for my multi factor method and I was able to log in.  However, I still didn't have the dual accounts.

A couple of hours went by and nothing.  So I started a chat with the guest.  I was able to send chats, but they weren't received.  This was clearly because the guest wasn't in their guest account.  About 30 minutes after that I got an email saying that the person had sent a message in Teams.

I clicked on the link and it started the redemption process again.  Open the app or login to the web app.  I clicked on open the app and I got the Switch accounts popup.  At this point I had to log in again with my credentials, including MFA.

This time it logged me in to the guest account.  And I was able to switch back and forth between accounts.  

What could be better?

1. Failed first attempt - I don't know why it failed the first time I clicked on the invite and switch accounts, but it did.  It really has to not do that.  Especially for end users.  If it takes a bit of time on the back end to get things finalised, delay the sending of the invite until it is actually ready for it to work.

Update: this only happens in the desktop app.  The web first attempt is quick and painless.  Once you accept the invite, it adds the additional tenant guest context to your account even if you're already logged in.  And it switched immediately.

2. Meeting experience - If you can't invite a guest to a meeting, don't let the user find the guest in the invite list and press send and eventually get the NDR.  This is really poor.

3. Admin process - I've read that users also need to be Limited Admin to be able to send invites.  My user account in my tenant is the only user and is, of course, admin.  Something to be mindful of.  

The actual admin process I have above is pretty straightforward, but could all be on a single screen rather than 3 or more.  Just agregate all of the settings into a single screen with all of the tick boxes needed and a clear explanation of permissions.

4. Guest Accounts - At the moment guests have to have Azure AD, and soon Teams will allow anyone with a MSO account.  The former limits the possibility of working with anyone that doesn't have Office 365.  The latter is a little like Lync 2013 federation with Skype for Consumer.  At first, you could only send an invite to a hotmail (or similar) account and the user had to convert their Skype account to MSO.  If the guest account is being added as a new entry in Azure AD, why should it matter what type of account they have?  Surely, we should just be able to add a guest account with an email address.  If Teams needs a user to authenticate, then it should set up an AD guest account with a username and password.  

What this says to me is that you can only work with people (customers, suppliers, contractors) in Office 365.  It will get a little better with MSO.  A lot more people have MSO accounts than Office 365 accounts.  And as Microsoft says, they can just set up one if they don't have one already.  I think it should have allowed MSO as well as Azure AD at launch.

5. Account switching - I can't believe I have to leave my own company context and go into another to interact.  While I'm in the guest account I am missing everything in my normal account.  I think you should be able to stay in your normal account and a new team should appear inline with all the other teams.  You should be able distinguish between internal teams and Guest teams and just move about as normal.

That's it for now.

Additional resources
Admin Guide on
The announcement by Lori Wright


I hope you found this useful.  Thank you for reading.

If this or any other post has been useful to you please take a moment to share.  Comments are welcome.