Microsoft Teams Mobile - Dark Theme

If you are a cool kid you have an iPhone X, or at least an iPhone, and if you are trying to be really cool of course you play Pokemon GO like I do. When doing so battery life is a problem. Unlike my good old Nokia 8210 which could go on for days on one charge you will find yourself constantly changing and always carrying a large extra battery pack.

Now, there are some tricks to get more battery life out of your iPhone, such as not using it, killing background activity and notifications, etc., but a so called "dark mode" can be a major power saver: How to squeeze more battery life out of iPhone X

Therefore it is really exciting that Microsoft Teams on iOS now supports a Dark Theme, since version 1.0.66.

Version 1.0.66 where the darkness begins...

 
So, how do you turn it on?

1. Click the three bars in the top left of the application to expose your profile and click Settings.

2. Click General.

3. Flip the switch to turn on "Dark Theme" and close the application.

4. Next time you start your Teams client it will look much cooler (and preserve battery life)

If you want to use the dark theme even on your desktop you find a nice guide here.

I would also like to point out that this is an idea coming from users of the Microsoft Teams mobile app through Uservoice. Please continue to send in new ideas and vote on Uservoice to make Microsoft Teams even better in the future.

Ignite 2018 - BRK3000 - Strategies for building effective, optimal and future proof connectivity to Office 365 that will delight your users

Presented by Konstantin Ryvkin

A very good session explaining Office 365 networking in depth at an understandable level. Please watch it and send this presentation to your network and security team!

 

This session and slide deck can be downloaded here.

Office 365 is a big cloud, and some customers have issues with connectivity and performance while others do not - what is the difference?

There are 3 major types of clouds

• IaaS - Infrastructure as a Service (Azure virtual machines / virtual network)
• PaaS - Platform as a Service (Azure SQL or blob storage)
• SaaS - Software as a Service (Office 365)

The preferred connectivity method to these different clouds differ. (Azure is regional, Office 365 is global)

SaaS disrupts traditional connectivity models

For decades Enterprises have been evolving their networks to protect themselves from the Internet, this means that they now have a lot of security measures in place that might interfere with Office 365 connectivity. The connectivity was not made to be simple, it was made to protect the users from the Internet.

Often a user will get better connectivity "from home"
(if not forced to VPN back to the Enterprise network and go through all the security)

Some of the trends or changes that SaaS networking is binging are that security controls move from the local network into cloud applications, and the Internet path to the Cloud becomes shorter.

Latency becomes a problem - do not backhaul distances and check the ISP and its peering with the Microsoft Global Network.

To measure the latency from an Outlook user to Office 365 PsPing can be used:

psping -n 5 outlook.office365.com:443

(We are using psping to avoid using ICMP, but rather test https transactions.)

The picture above is showing network latency for customers in Australia and shows that customers in the same metro area, same geographical region and with the same Office 365 service, can have very different experiences. Most importantly - it is possible to get great Office 365 latency experience (even from Australia.)

Office 365 comes closer and closer to end users

The Microsoft Global Network (AS8075) with its global reach
and the Distributed Service Front Door infrastructure, makes it close to users anywhere.

On https://aka.ms/o365ip you will find the full list of all Office 365 endpoints. An endpoint is an IP:port combination that clients are connecting to (40.97.143.130:443) The comments received on this list is that it is long, it changes and security guys will not like it. That is why Microsoft have shortened the list from thousands of entries to hundreds and categorized the endpoints into Optimize, Allow and Default endpoints.

The list of "optimize" endpoints will change less than once a year, so it is quite stable. On https://aka.ms/ipurlws there is a REST API available for customers and partners to automate the updating of network devices according to this list.

A hub-and-spoke model have traditionally been used to backhaul traffic into a central location, this works well when users are connecting to services located at the hub, i.e. it does not work as well for Office 365 traffic. Try to evolve away from hub-and-spoke and go for a full mesh when it comes to Office 365 traffic. Consider this for external DNS requests as well.

Office 365 will overtime move some of the data closer to the location where you enter the Microsoft network, e.g. your mailbox, to further decrease latency of getting data. Such moves will only happen within your compliance boundary.

Man-in-the-middle SSL inspection, aka break and inspect, works well for simple web browsing. However, Office 365 traffic is not web traffic, what would the "inspector" do with encrypted audio or video?

Follow these simple principles to delight your users!

Resources

• https://aka.ms/pnc - Office 365 Network Connectivity Principles
• Usingthird-party network devices or solutions on Office 365 traffic

Svenska UC klubben is back!

Post in Swedish about a meeting in our local UC user group in Sweden.

I går var det äntligen dags för Svenska UC klubben att återuppstå!

Det var nog 4 år sedan sist vi hade ett möte, men nu hoppas vi att klubben kommer igång på riktigt igen.

Det var ca 25 personer på plats hos Uclarity i Stockholm och kvällen sändes även med Microsoft Teams live events till ett 20 tal personer runt om landet.

Det hela började med Plantronics som presenterade en del nya produkter. Ca 70% av dagens kontorsarbetare sitter i så kallade "öppna landskap", p.g.a. kontorsyta och samarbete, men 94% tror att man skulle få mer gjort i en lugnare miljö. Ett problem på våra moderna arbetsplatser är helt enkelt oljud. För att råda bot på detta har Plantronics ett rumssystem kallat Habitat för bakgrundsljud som är mer avancerat än att enbart spela vitt brus, det kan spela t.ex. vattenfallsljud istället.

Sedan fick vi se Elara 60 en docka för mobiltelefon med knappsats och headset som även funkar med Microsoft Teams och sist men inte minst Polycom studio som verkar vara en trevlig enhet för mindre rum.

Mårten och Linus presenterade det de kallade "Resan från Skype till Teams". Även om Teams och Skype for business har vissa överlappande kommunikationsfunktioner så är rådet är att inte jämföra äpplen med päron, eller äpplen med hela fruktkorgen. Teams är mycket mer än bara kommunikationen som man får i och med Skype for business.

Sedan diskuterades de olika lägena som finns när man flyttar från Skype for business till Teams. Planera för vilket läge (mode), ni vill hamna i och nyttja innan ni startar igång med Teams. "Island Mode" som är default innebär att man kör systemen "bredvid varandra" med alla funktioner aktiva. Teams only - ger enbart Teams och då blir Skype for business avaktiverat. Det ända sättet att få federerade meddelanden att hamna i Teams är att aktivera Teams only läget.

Frågan man bör ställa sig är: Klarar vår organisation att ha två system samtidigt? eller ska vi försöka ta oss till Teams only så fort som möjligt?

Sen följde en genomgång av chat i Teams, mellan olika lägen, var lagras chattar, var lagras filer man delar.

Telefoni i Teams - Direct Routing - är en koppling mellan telenätet (PSTN) och Microsoft Teams i Office 365 som görs genom en Session Border Controller som är testad för att fungera med Teams. Det är inte svårare än att man kan sätta igång det hela under en eftermiddag påpekade Mårten från Cellip. Det finns dessutom en mängd applikationer för telefonistfunktioner och callcenters.

Det finns en inofficiell Linux klient på Github - har någon provat den och kan berätta hur den fungerar? Hör gärna av dig till mig.

Även Uservoice nämndes där Teams användare kan gå in och lägga förslag på nya funktioner i Teams som produktgruppen som bygger Teams kommer att titta på när de planerar framtida iterationer av produkten.

Sedan kom en "special guest" från Amerika via Teams mötet, det var Skype for business och Teams-profilen Matt Landis som berättade en del om situationen i ett par flyktingläger han besökt under förra året. Kul att höra något som inte var helt väntat och lite utanför boxen för oss kommunikationsmänniskor. Tydligen finns det 6 gånger fler människor på flykt idag 2019 än det fanns i slutet av andra världskriget, så det är kris som bara växer. Matt berättade om hur läget var i läger i Bangladesh, Irak och på Lesbos precis vid Europas gräns.

Efter detta tog vi lite allmänna frågor, svar och synpunkter från deltagarna.

Stänger Teams only av autostarten av Skype for business klienten?
Ja, men om du startar den manuellt så kommer den börja autostarta igen. Det finns en poäng med att ha kvar klienten för att vara med i möten hostade i SfB även när man gått till Teams only läge.

Presence - eftersom Teams chatten är persistent, betyder inte presence samma sak eller lika mycket som det gjort i SfB. Ett meddelande kommer läsas av mottagaren nästa gång han öppnar klienten i datorn eller på mobilen. Meddelanden i Teams är ett slags mellanting mellan email och chatt.

När man har externa kontakter i Teams (via federation) så "poppar meddelanden upp på olika ställen" - varför är det så?
Island mode är inget bra läge att stanna någon längre tidsperiod i, försök komma till Teams only så fort som möjligt.

Det är möjligt att Svenska UC klubben kommer "hitta på något" under Ignite the tour som hålls 24-25 april i Älvsjö.

Håll koll på hemsidan, Linked in gruppen eller Twitter (@SUCK_klubben) för info om kommande träffar.

Ignite 2018 - BRK2190 - Delighting your End Users: Facilitating a smooth transition from Skype for Business to Teams

Presented by Sarah Goodwin and Debbie Arbeeny.

It is not rocket science to use this framework.

The customer ICA (from BRK3141) said
"We did not migrate any user, all our users choose to move".

Among the first words we learn are "no" and "why" - that is why we have the concept of "shadow IT" in larger organizations today. No user will go get their own system for email, but for collaboration there are many tools out there making "shadow IT" grow bigger and bigger. The "deploy it and they will come approach" will not work - look at Access, many people have Access deployed - few use it.

"You never get a second chance to make a first impression." - Classic quote that is so true.

Change is not a one-size-fits-all every organization are made up of innovators, laggards and everyone in between. In a general organization there are about 25% early adopters and 25% laggards.

A "pilot" is not only to test the application, also the training, help desk, etc, must be tested.

Poll: How long time does it take a person to change behavior and create a new habit?
Studies used to say 21 days for a small change, but now we are estimating more like 2 months for a small change and 6-12 months for something major. I.e. "deploy it and they will come" will not work.

Be mindful about implementing too much change at once. People react to change differently. We all listen, learn and retain information differently.

Never tell users

• "We are moving to Teams because it will save us x amount of money"
  (You are taking away tools I use?)
• "We are implementing this to improve your productivity"
  (I already work 12-hours a day, and it is not enough?)

Resources

• Skype-to-Teams Upgrade Site (https://aka.ms/SkypeToTeams)
• Live, Online Training (https://aka.ms/TeamsLiveTraining)
• Upgrade Success Kit (https://aka.ms/UpgradeSuccessKit)
• Success with Teams (https://www.successwithteams.com)

Ignite 2018 - THR1165 - Building a community of champions to drive adoption of Microsoft Teams

Presented by Sara Bush and Pouneh Kaufman

Microsoft Teams…

• Meets modern workplace needs
• Is a customizable hub for teamwork
• Simplifies the communication experience

Microsoft internally will migrate 225,000 users by year end, no more Skype for business for them.

The champions were found on Yammer (answering questions and helping people) in pilot groups and by recommendations by other users.

The adoption program had four pillars.

The Champions program had to be global and make Champions visible to the end users. Moreover, Champions had to be asked to do something (Gives) and to get some value for themselves (Gets.) A lot of Teamwork toolkit digital assets was created in this program and that is now available externally to all Microsoft Teams users.

All Champions added a special symbol to their profile picture to indicated that they are in the Champion program and to start conversations.

Did it work?
Yes, now over 55% of all internal chats are in Teams, some 5 months after start (even though everyone can still choose what to use at this time), 17% of all meetings are held in Teams and 99% of people keep using Teams every month. Next thing coming is gamification - let's make it even more fun to use Teams!

Let's play a nice round of Teams :-)

Ignite 2018 - BRK3141 - Designing your path from Skype for Business to Teams: Start Here!

Presented by Debbie Arbeeny and Scott Stubberfield (and Marvin Liljegren and Jacob Lindgren from ICA)

This is really part 1 in a 4-part series on how to move from Skype for business to Teams

Part 1: BRK3141 - Designing your path from Skype for Business to Teams: Start Here!
Part 2: BRK3142 - Planning a seamless migration from SfB to Teams for IT Admins
Part 3: BRK2190 - Delighting your End Users: A smooth transition from SfB to Teams
Part 4: BRK3124 - How Skype for Business on-premises customers can take advantage of Microsoft Teams meetings

Do not compare apples to pears by just comparing Skype for business with Teams. If were to just take all the features and move them from point A to B what would we have gained? Teams is much more than Skype for business.

In an environment with both Skype for business and Teams both clients will now be displaying coachmarks and icons to keep users informed about which client the other party is using. (Coachmarks are the little texts with an arrow pointing to some detail in the GUI to explain it.)

Teams is more than a technical migration

Before a migration make sure your users get to see Teams in action, use Teams and show others why to use Teams. It more successful to use "the carrot" over "the stick." Attach your Teams project to broader plans around digital transformation. Are parts of the business currently in digital transformation projects? Are groups moving offices? Revitalizing work spaces? Are groups changing how they do work?

Use product champions - why is this so important for Teams? Because it is a collaboration product - you do not use Teams alone as you could use Outlook, Visio or Solitaire. You get the benefit of Teams by working with others.

The customer ICA - the largest foodstore chain in Sweden where I am a customer - told about their journey to Microsoft Teams. ICA found themselves in a situation where their market was changing (to online), they switched offices and felt a need for better collaboration tools. Also, they went through a cultural change redrawing the entire organization scheme. Now the organizational chart looks more like a molecule with informal connections rather than a pyramid with formal manager / directs relationships.

A democratic peer-to-peer organization

In the Swedish society everyone walks around with a smartphone - full of processing power and apps much better than the ones used in a normal enterprise. We have all become digital producers thanks to Facebook and Instagram. This puts new demands on a hiring organization.

We're all digital producers

A no-email challenge was used at ICA - stop using email for 2 weeks (could you do it?), but no one were forced to use Teams. Teams communication is more informal than emails, and this is really the way the new generations communicate with each other. ICA used big room sessions, smaller sessions and even drop-by-during-lunch sessions to help the users with Teams. Some users were die-hard Slack fans, but after the pilot even some of them have been convinced to stop using Slack and even stop using Outlook.

Questions

Is there an end-of-life date communicated for Skype for business Online?
No, but Microsoft is currently doing all they can to make everyone want to be in Teams rather than in Skype for business. (Carrot, not Stick.)

How about federation in Teams?
Today it depends on the underlying Skype for business infrastructure, and the messages exchanged are called interoperability messages. Eventually there will be Peer-to-peer Teams to Teams federation.

What kind of support calls did ICA get during the rollout?
How do I create a group? What's happening in Teams? My meeting did start? My network is bad. Gradually users started helping each other with questions and answers right in Teams. Many "how do I..." questions get answered this way.

Ignite 2018 - BRK3142 - Planning a seamless migration from Skype for Business to Teams for IT Admins

75 minutes presented by Francois Doremieux and BJ Whalen

Why should you migrate to Teams?

• Features and capabilities
• User experiences
• Operational performance

Upgrade (or "Migration") Objectives

• Enable SfB (on-prem or Online) users to move to Teams
• Provide interop between users who have SfB and those with Teams

 

The "Teams-Only" mode sets the SfB client in a "meetings only" mode.

Scenario: Full Side by Side Approach
Run both clients at the same time and the user will have a choice for each interaction. Have both meeting "buttons" in Outlook. (Can be confusing for users.)

Scenario: Teams-Only Experience
The user will only run the Teams client, but a "disabled" Skype for business client will remain installed in order to join Skype for business meetings hosted at other organizations. Incoming chat messages will arrive in Teams.

Scenario: Meetings First
For on on-prem & hybrid organizations, that will move to Meetings First before going Teams Only. Meetings first is a configuration that allows organizations to use Skype for business for instant messaging and calling and Microsoft Teams for meetings. The user will run both clients, but with no overlap in functionality. The chat and calling tabs will be removed in Teams and even the "Teams and channels" tab can be removed. Users will then have all their meetings in Teams with all the benefits of the global infrastructure, recording, transcription, etc. The on-premises versions supported are Lync Server 2013, Skype for business 2015 or 2019. (Please see BRK3124 for more information.)

Interoperability: Teams uses https and Skype for business SIP. In the cloud there is a gateway that lets them communicate. However, this only works for Skype for business Online users and even the Teams users will get a Skype for business Online shadow account. The Skype for business user must be homed online and this can of course be accomplished with a hybrid configuration. Currently this interoperability is one-to-one only. In the future this will change so that a meeting will start and both users will automatically be added to the meeting giving them richer collaboration options. In Skype for business a yellow banner will show up indicating that this is conversation over the SfB - Teams gateway. (There is also an update post Ignite about presence in coexistence modes found here: Presence now respects a user's coexistence mode.)

It is possible to upgrade without overlapping functionality.

Interoperability and co-existence are managed in the Teams Admin center of via PowerShell. Some aspects of some modes are not yet fully implemented but should come in preview later this year.

A hybrid configuration is a requirement to upgrade Skype for business users to Teams. Users can start from scratch in Teams, but hybrid is required to move a SfB user to Teams. With Skype for business Server 2019 and/or CU8 for Skype for business Server 2015 there is a new –MoveToTeams switch in the Move-CsUser command.

Move-CsUser -Identity mattias@kressmark.com -Credential $cred -Target sipfed.online.lync.com -MoveToTeams -BypassAudioConferencingCheck -BypassEnterpriseVoiceCheck

An upgrade to teams can be "IT Admin-driven" or "Microsoft-driven automated" and the big difference is really how the migration is initiated.

Questions

Will these upgrade scenarios change in the future? (Will something "better" come?)
No, this is it. Teams will not become a Skype client and Skype will not become a Teams client.

Will there be upgrade from Skype for business on-prem to Skype for business Multi-Tenant?
No, nothing have been added/changed in the Skype for business Multi-Tenant version lately.

Is there a minimum on-prem server version of the hybrid to get Interoperability?
Yes, Lync 2013 (without Enterprise Voice) and Skype for business 2015 (with Enterprise Voice)

Will Skype for business Online meetings (recurring or not) be migrated to Teams?
No, only on-prem meetings will be migrated.

Is there a way to trigger the contact import manually?
Not right now but this could change in the future.

Is there an end-of-life date communicated for Skype for business Online?
No.

What will happen to incoming PSTN calls in Islands mode?
Depends on how the connection to PSTN is made. With Calling plans the call would go to Skype for business, with direct routing it would go to Teams (most likely.)