This year’s Microsoft Ignite 2019 takes place in Orlando, FL, US from 04.-08. November. Ignite is about innovative solutions, how you can built/implement/migrate and manage them.
However, it’s sold out, but you could view live streams, especially the keynotes. Other sessions and contents are usually also widely made available afterwards.
This year I’m glad to attend Ignite. It’s a great opportunity not just to learn about the greatest and latest in tech around the Microsoft products, services and best practices, no, it’s more than that, it’s also an amazing opportunity to socialize with others in your area of expertise and get other views/approaches and ideas.
If you’ll be onsite feel free to send me a pm via Twitter or LinkedIn.
Soon, I’ll get a chance to speak at the abtis IT Symposium in Pforzheim (11/10/2019). The event and speakers cover different topics about the “digital future readiness” (DE: “Bereit für die digitale Zukunft”).
I’ll talk about getting rid of legacy PBX infrastructure and legacy telephony services by embracing modern communication and collaboration with Microsoft Teams as an hub for modern teamwork. Telephony is just one of many features, although it’s very important for our daily business. My session “Vom Festnetztelefon zur integrierten Microsoft Telefonie” is about telephony with Microsoft Teams. I’ll describe which options you have to migrate your telephony workloads partially or completely to Teams and how it the user experience looks like.
I received a change notification via the Microsoft 365 Admin Center. It says that the Skype for Business Online external access settings are retired.
In other words external access will vanish in the SFBO Admin Center. So, the external access settings can only be managed within the Teams Admin Center or via PowerShell.
In the Teams Admin Center you find the external access settings as follows: Org-wide settings\External access”
Source: Microsoft Teams Admin Center
Conclusion, opinion and summary
I welcome this change because if you modify external access settings in SFBO or Teams Admin Center it’s reflected, so there’s no need to have two settings pages in different Admin Centers plus PowerShell.
In this post I like to inform you about and upcoming change regarding Office 365 client connectivity. Microsoft announced this already in the past and reminds admins via the Office 365 admin center about the upcoming change.
This might be subject to change anytime so please monitor your Office 365 message center to stay informed about this if it is relevant for your client infrastructure.
Based on the Office 365 ProPlus – Updates page (see link below)
Starting October 13, 2020, it will be necessary to have Office 365 ProPlus or Office perpetual in mainstream support to connect to Office 365 services.
I.e. Office 2013 client connections to Office 365 (SharePoint Online, Exchange Online, OneDrive for Business …) will run out of support and won’t be supported after 13. October 2020. Office 2016/2019 connections are supported till October 2023. That’s why you should plan and migrate towards Office 365 Pro Plus/Office 2016/Office 2019 to be able keep your Office client connectivity to Microsoft Office 365.
Conclusion, opinion and summary
I recommend to plan, test and execute your Office client upgrade journey to a support Microsoft Office before the above supportability deadline in case your clients run Office 2013.
[DE] In diesem Beitrag geht es um ein neues Features für Microsoft Teams, welches im September 2019 ausgerollt wird. Microsoft Teams erhält ab diesem Monat ein sehnsüchtig erwartetes Feature, den “Secondary Ringer”, oder “Sekundärer Rufton” (DE).
Der “Sekundäre Rufton” erlaubt das Klingeln bei einem Anruf auf zwei Geräten. Das ist sehr praktisch, wenn ich das Headset auf dem Schreibtisch liegen habe und mich jemand anruft. So kann ich einstellen, dass es sowohl auf meinem Headset und auf dem Lautsprecher meines PCs klingelt.
Bislang sehe ich bei abgesetztem Headset nur eine visuelle Benachrichtigung für eingehende Anrufe. Somit kommt mit dem “Sekundären Rufton” ein zweites auswählbares Ausgabegerät hinzu.
Quelle: Screenshot Teams Einstellungen \ Geräte \ Sekundärer RuftonSource: Microsoft Teams – Secondary Ringer [Microsoft 365 roadmap update item 51089]
In this post I describe where you can start to get more details (figures!) about the Microsoft (Office) 365 adoption at your company.
There are many different ways to gain insights. But if you rolled out different Office 365 services at your company there’s already quite a lot of valuable data. Where? Well, you know all the admin dashboards in the different Office 365 admin centers, right? So, these dashboards are good start to see what’s adopted but what about a more holistic view?
Of course you, could build a new dashboard in PowerBI by attaching different data sources, Graph API etc. But why not utilizing available tools? Is there any?
Microsoft 365 usage analytics
Yes, there is and it delivers you the following information:
Adoption overview report
Product usage report
Storage used report
Communication report
Collaboration report
Office activation report
Access from anywhere report
Individual service usage reports
Individual service user activity reports
What do have to do for this?
There is not much to do.
Enable Microsoft 365 usage analytics[see link at the bottom]
Navigate and utilize the reports in Microsoft 365 usage analytics[see link at the bottom]
Read the reports
Apply measures to drive adoption in the spaces where it is required
Review monthly
Go back to 3. [infinite loop / continuous [adoption] improvement process –> learning never ends ;-)]
Conclusion, opinion and summary
Before you start to build your own reports you might want to start with what’s available at your fingertips! I had the chance to test and it’s ready within minutes. So, you can view report data. What you finally need to do is to check what information you receive and conclude your next steps to drive adoption in weak areas by adequate measures, e.g. awareness campaign, training/education or other means of communications to drive adoption of Office 365 services within your company (as needed).
Microsoft announced that Yammer and Office profiles will be merged. Until today a user gets provisioned and logs into Yammer. This triggers the “creation” of its Yammer profile which is synced from the user’s Office profile. However, if a user changes values of his/her Yammer profile it is overwritten by the next Office profile sync to Yammer in case the Office profile was changed.
Well, it means that the users’ profiles become one and will based of the Office profile. The Office profile becomes the “master” and sole profile.
So, the profile button in Yammer will disappear soon and than every profile value is based on the Office profile. Single profile instead.
How can you manage the merged Yammer/Office profiles of users?
Due to the fact that there will be only one profile left you’ll need to manage only the users’ Office profiles. Either a user can manage this within set limits on the Office 365 Delve profile page or by contacting your Office 365 administrator and support.
Conclusion, opinion and summary
To sum it up, you’ll manage user attributes via Active Directory. Either in you onpremise AD which is synced via AAD Connect to Azure AD and Office 365. Or in case you are cloud-native user attributes from Azure AD are used.
Depending on how much “self-serving” you allow users could make changes to the profile by using the Delve profile (page).
