Category: Skype for Business

December 5th, 2019 by Kenneth ML
At a customer site I discovered patterns of unexpected network traffic to various Google and Apple sites. The policy doesn't allow for unmanaged devices (BOYD mobile phones etc. til access the WiFi network, and this traffic pattern looks like mobile devices, but there weren't any mobile devices associated on the wifi.

What actually happened is that dual radio Windows 10 devices are able to have a Mobile Hotspot where mobile phones connects on 5GHz while maintaining a WiFi connection on 2.4GHz. This allows unmanaged devices to access the corporate network.

To prevent this "feature", we decided to disable Mobile Hotspot sharing on the Windows 10 devices. Using Intune device configuration we used this setting:

Setting this entry: ./Vendor/MSFT/Policy/Config/WiFi/AllowInternetSharing to 0 disables the Mobile Hotspot button on Windows 10 devices.

Posted in Skype for Business

December 5th, 2019 by SharePoint Maven

Remember when Apple® released iPods, the most popular question for celebrities and politicians was – “What kind of music do you have stored on your iPod?” Now, I am no a celebrity or politician (I am too politically incorrect), I am just a SharePoint guy who craves for everything that has to do with SharePoint and Office 365. So I will admit, on my phone, I have no music. Instead, as a true SharePoint geek, I have mobile apps that help me be productive with Office 365 and SharePoint. So with this post, I would like to share the ten apps I have on my iPhone® and explain briefly what each one does.

Office 365 mobile apps

A screenshot of Office 365 Mobile Apps on my iPhone®

OneDrive

I do not think I need to explain much this one. If you need to access files and folders stored on your OneDrive for Business or any SharePoint site, this is an app you want to have. OneDrive app is just about files and folders if you need to get a hold of them on the road.

Office 365 mobile apps

OneDrive Mobile App

SharePoint

If you need to access more than files and folders (i.e., other content like links, news, lists that are part of your SharePoint sites), then you would need a SharePoint mobile app. In addition to documents, it allows you to access whole SharePoint sites and other types of content on a site. By the way, for the more detailed overview and comparison of SharePoint and OneDrive apps, check out this post.

Office 365 mobile apps

SharePoint Mobile App

Stream

If you store company videos in Microsoft Stream, you will need the Stream mobile app. Essentially it is just like YouTube® app – allows you to access videos and watch in a friendly manner on your phone or iPad.

Office 365 mobile apps

Microsoft Stream Mobile App

Planner

If you are managing tasks on various projects (Plans) in Planner, you will need a Planner mobile app. It will allow you to complete the tasks on the go for the multiple plans/projects you are part of.

Planner Mobile App

To Do

To Do is a new kid on the block and is essentially a personal task list. The beauty about To Do is that it rolls up tasks from multiple plans you are part of in Planner as well as Outlook. A mobile app is a great addition that allows you to access personal tasks on a mobile device.

To Do Mobile App

Teams

Don’t worry, I did not forget about Teams. Teams mobile app allows you to chat with your team from your mobile device. Just like in the desktop version, you can access various channels (conversations), files, and tabs.

Teams Mobile App

Power Automate (formerly Flow)

A Flow mobile app allows you to start and stop flows from your mobile device. You also can tweak/edit workflows from within an App as well, but honestly, I doubt it will be a great user experience on a tiny phone screen.

Flow Mobile App

Power Apps

PowerApps mobile app, of course, allows users to access all the mobile apps you have developed in PowerApps.

PowerApps Mobile App

Outlook

Though Teams is becoming increasingly popular, you still need access to Outlook when you are on the go. Outlook app allows you to send and receive emails and access the personal calendar.

Outlook Mobile App

Yammer

If your organization is using Yammer, and you can’t miss that critical update from your CEO, then Yammer mobile app is for you.

Yammer Mobile App

The post 10 Office 365 mobile apps you must have on your phone appeared first on SharePoint Maven.

Posted in Skype for Business

December 4th, 2019 by johnacook

A new mandatory parameter, SourcePfPrimaryMailboxGuid , is being added to the New-MigrationBatch command for public folder migrations from – 1047343
— Read on techcommunity.microsoft.com/t5/Exchange-Team-Blog/Upcoming-change-in-the-way-migration-batches-for-public-folders/ba-p/1047343

Posted in Skype for Business

December 4th, 2019 by UC Now Skype/Teams News Feed

Howdy folks,

 

Today, we have yet another piece of Ignite news to share. Office 365 groups expiration policy now includes auto-renewal based on activity! About a year ago, we shipped expiration capability for Office 365 groups, which allows you to retire unused groups. 

 

That was a great first step, but we knew we could make the experience even better. So today, I’m announcing that the following actions will lead to automatic renewal of the groups, which are configured with the expiration policy:

 

  • SharePoint—View, Edit, Download, Move, Share, and Upload Files.
  • Outlook—Join group, Read/write group message, and Like a message.
  • Microsoft Teams—Visit a Teams channel.

If you have already configured the Office 365 expiration policy for groups, you’ll notice this change applied immediately to those groups.

 

If you haven’t adopted the expiration policy for Office 365 groups and want to take advantage of this capability, you can learn how to configure the expiration policy for Office 365 groups.

 

Let us know what you think! We would love to hear your feedback! If you have any suggestions for us, questions, or issues to report, please leave a comment below.

 

Best regards,

Alex Simons (@Alex_A_Simons )

Corporate VP of Program Management

Microsoft Identity Division

Posted in Skype for Business

December 4th, 2019 by Tom

I’m slowly wading through Microsoft Ignite 2019 content, and pulling out what I think are interesting announcements. As much as I can do, I’m trying to highlight things which may not have been widely picked up, but which impacts Microsoft Teams developers.

This comes up quite a lot, and although it doesn’t directly affect developers, being able to answer questions like this can really help unblock conversations, or help developers understand what is happening. Also, as you’ll see below, Microsoft Teams makes use of a number of standard Azure resources which are available for anyone to use, so it’s a bit of a showcase of what’s possible using Azure.

Courtesy of a Microsoft Ignite 2019 session, Microsoft Teams Architecture Update, presented by Platform Architect and Teams founding member Bill Bliss, here are the key locations where data is stored at rest.

As you can see, Microsoft Teams leans heavily of Azure resources to deliver its functionality at scale. In fact, Azure is really at the core of the Microsoft Teams architecture:

But what about geographical location?

Knowing what Azure resource types are being used to store your data is useful, but often more important to organisation is where their data will be located:

If your Teams tenant is in Australia, Canada, the European Union, India, Japan, the UK or the US then the following data will be stored at rest within that geographic area:

  • Microsoft Teams Chats
  • Microsoft Teams Conversations
  • Images
  • Voicemail
  • Contacts
  • SharePoint Online site content and the files stored within that site
  • files uploaded to OneDrive for Business

Where are Conversations Stored?

As above, we can see that conversations are stored in Azure table storage (soon Cosmos DB), but there is some more detail on that in this slide:

Where are Files stored?

It depends on how those files are uploaded:

If this all sounds interesting, and you’d like to dig into more detail about the architecture of Microsoft Teams, then I highly recommend Bill’s session. Bill covers a number of different areas of Teams and talks candidly about how they are architected, and why the team made the decisions they did. You can watch the session video below:

Posted in Skype for Business

December 4th, 2019 by johnacook

Skype for Business Server 2019 Cumulative Update 2 (CU2) – Tom Talks
— Read on tomtalks.blog/2019/12/skype-for-business-server-2019-cumulative-update-2-cu2/

Posted in Skype for Business

December 4th, 2019 by Tom Arbuthnot

image

Latest Cumulative Update for Skype for Business Server 2019

Download here

Knowledge Base: KB4470124

Posted in Skype for Business

December 4th, 2019 by Brent Middleton
Need help understanding the ins and outs of Office 365 Groups? Click here for an accessible guide in the form of a Groups cookbook!

Posted in Skype for Business

December 4th, 2019 by Eric Marsi
With Exchange Unified Messaging being removed from Exchange Online at the end of February 2020 and being already removed from Exchange Server 2019, organizations have to be actively planning a replacement for all Exchange UM Auto Attendants that is currently in use. This guide will explain what is required, how to configure Cloud Auto Attendants and Cloud Call Queues, and how to validate the newly created Cloud Auto Attendant(s) and/or Cloud Call Queue(s). NOTE: This guide pertains primarily to organizations that are using Skype for Business Server on-premises with Exchange UM, not cloud-only customers. This guide will be broken down into four main sections: Planning & Prerequisites Setup Process Testing & Validation Clean Up Planning & Prerequisites What is happening? Exchange Online UM is to be turned off in February 2020 and after that, all Auto-Attendants will no longer work. Voicemail services that are currently provided by Exchange UM will be automatically migrated to the new Cloud Voicemail service, however, Auto Attendants need to be manually migrated. The goal of publishing this guide is to make users aware of Exchange Online UM's impending doom and to push for the need of migrating to the new cloud services to prevent down-time for one's organization. This guide will take an existing Exchange UM Auto Attendant, remove it from the environment and provide the steps to use a modern Cloud Auto Attendant. In regards to Cloud Call Queues, there is no major need to migrate to the service if you are wanting to keep all existing users on-premises with Response Groups. Where they become extremely useful is for migrating users to Microsoft Teams as Cloud Call Queues can be used to dial both Microsoft Teams Users and Skype for Business Server/Online users. Benefits of Cloud Auto Attendants and Cloud Call Queues This is a cloud built application that works with both on-premises and cloud-based users Useful for organizations not moving to Microsoft Teams over-night and need to retain interop with both on-premises and cloud-based users No need to convert audio files to a single-channel WAV format • Audio sounds a lot more crisp due to this If Teams Direct Routing is used, they are free as long as a single Phone System license is added to a Microsoft 365 Tenant. Which features no longer exist? A few features no longer exist in Cloud Auto Attendants/Cloud Call Queues that used to exist in Exchange UM Auto Attendants Direct Dialing of E.164 phone numbers (Coming Soon) Direct Dialing of Extensions (Coming Soon) NOTE: Many other Exchange UM features no longer exist such as Subscriber Access, Fax, and more. These features do not pertain to Auto Attendants but pertain to Exchange UM. Prerequisites A few prerequisites need to be addressed before the resource accounts can be created. • Skype for Business Server Software Version Skype for Business Server 2015 - CU8 or Higher (Current Version is CU10 HF1) Skype for Business Server 2019 - Any version (Current Version is CU1 HF1) • Must have hybrid connectivity to Skype for Business Online Includes Azure AD Connect • Licensing Requirements At least one Phone System license purchased (Included with a E5) Once at least one Phone System license is purchased, free Phone System - Virtual User licenses can be obtained Users must have a Small Business License with Business Voice, Enterprise E1 or E3 with an additional Phone System license, or E5 IF they are cloud based. If on-premises, no additional licensing is required • Must have Microsoft Teams Direct Routing configured or a Cloud Calling Plan Refer to my Deploying Direct Routing for Microsoft Teams guide! - CLICK HERE NOTE: Not Required if staying with Skype for Business Server!!! SFB Server holds the user object and will be the first point of contact when dialing the user. Setup Process Step 1: Create an on-premises resource account On a Skype for business Front-End Server or a Trusted Application Server, run the following PowerShell cmdlet but with using different variables. The Display Name is How the Auto Attendant or Cloud Call Queue will appear within the Skype for Business Client, the SIP Address is the SIP Address, and the OU is where the account is to be created. Make sure that this created in an OU that is part of the Azure AD Connect Sync Group. New-CsHybridApplicationEndpoint -DisplayName OH1_RA_AA1 -SipAddress sip:OH1_RA_AA1@msftnettest.co -OU "ou=Resource Accounts,ou=MSFTNET Test,dc=msftnettest,dc=co" Step 2: Assign a phone number to the resource account Use the below cmdlet to set the Line URI for this account IF Microsoft Teams Direct Routing is being used. Note that this is not needed if this auto-attendant is a nested auto-attendant in either scenario. Additionally, if the cmdlet prompts and states that the phone number is not unique, the Exchange UM Contact or the response group will need to be deleted or another user account has that phone number assigned. Follow the steps at the end of this guide to remove the ExUmContact. Set-CsHybridApplicationEndpoint -Identity OH1_RA_AA1@msftnettest.co -LineURI tel:+13305768835 Step 3: Force sync the account to Azure AD (Optional) To speed up the process of generating the online application instance and not wait up to 30 minutes, the newly created account can be force-synced to Azure AD. On the server that runs Azure AD Connect run the following two PowerShell cmdlets: Import-Module ADSync Start-ADSyncSyncCycle -PolicyType Delta Step 4: Assign a Virtual Phone System License to the Resource Account Now that the account exists in the cloud, a Phone System - Virtual User license needs to be assigned to the resource account. 1. Login to the Microsoft 365 Admin Center as a Global Administrator at https://portal.office.com 2. Click "Admin", then "Users", and then select the newly created Resource Account 3. Click on the "Licenses & Apps" tab, select the Phone System - Virtual User license and then click "Save Changes" Step 5: Connecting to Skype for Business Online At the time of writing, on-premises phone numbers cannot be assigned to resource accounts via the Microsoft Teams Admin Center. If a Calling Plan will be used for the AA or CQ, do not use the following steps. This is potentially an upcoming feature, but I am not sure if this will ever come to the admin center. To begin, a connection to Skype for Business Online PowerShell is needed. Follow the below steps setup the necessary prerequisites to connect to SFBO: 1. Install the Microsoft Online Services Sign-in Assistant Bit.ly/1TugAlN (lowercase L) 2. Install the Skype for Business Online PowerShell Module Bit.ly/1BOlaX2 (Capital i) 3. Enable script support on the local computer by running the below PowerShell command as a local administrator. Set-ExecutionPolicy RemoteSigned Now that the prerequisites are now satisfied, it is time to connect to Skype for Business Online. There are differences in this process depending on how a global administrator account is configured. Run the commands below that option that matches how authentication is setup for the account: Option 1: The Account does not have Multi-Factor Authentication Configured Import-Module SkypeOnlineConnector $userCredential = Get-Credential $sfbSession = New-CsOnlineSession –Credential $userCredential Import-PSSession $sfbSession Option 2: The Account has Multi-Factor Authentication Configured Import-Module SkypeOnlineConnector $sfbSession – New-CsOnline Session Import-PSSession $ sfbSession Step 6: Assign a Teams Direct Routing or hybrid number to the Resource Account If an on-premises phone number is being used for the newly created account, run the following PowerShell cmdlet to assign the on-premises phone number: Set-CsOnlineApplicationInstance -Identity OH1_RA_AA1@msftnettest.co -OnpremPhoneNumber +13305768835 NOTE: The Application Instance can take up to 24 hours to be created! Use the Get-CsOnlineApplicationInstance cmdlet to see if Microsoft 365 has created the instance or not. Step 7: Create a Cloud Auto-Attendant or Cloud Call Queue Now that things are good to go from a resource account perspective, an auto-attendant or cloud call queue can be created. This guide will not cover the specifics of each, but when creating each, select the newly created resource account as show below: Testing & Validation With the Cloud Auto-Attendant(s) or Cloud Call Queue(s) created, functionality can be tested. Call into each Auto Attendant and verify that: Any custom greeting(s)/automated messages play Voice commands work (If enabled) All menu options are pronounced correctly and can be reached Business hours work (If applicable) Call into each Call Queue and verify that: Any custom greeting(s)/automated messages play The selected routing method works correctly All members on-premises and in the cloud are able to be reached Business hours work (If applicable) Clean Up - Exchange UM This section really only applies to organizations that have Skype for Business Server and have just created a replacement for their Exchange UM Auto-Attendant. The following steps need to be taken to remove the Exchange UM Contact in Skype for Business Server and remove the former AA from Exchange Server. This step has to be completed first if the same phone number is being reused or last if a new phone number is being used. Step 1: Remove the Exchange UM Contact On a Skype for business Front-End Server or a Trusted Application Server, run the following PowerShell cmdlets but by using different variables. First we need to identify the SIP address of the Exchange UM Contact that we wish to remove by using Get-CsExUmContact cmdlet. Once the SIP address has been identified, fill that in on the below cmdlet Remove-CsExUmContact -Identity sip:OldExchangeUMAddress@msftnettest.co Step 2: Remove the Auto Attendant from Exchange Online In the Exchange Online Admin Center, click Unified Messaging > The UM Dial Plan > Single Click the AA you wish to remove > Click the Trash Can > Confirm the Removal. Note that this step is optional Clean Up - Response Groups This section only applies to organizations that moved from a Response Group to a Cloud Call Queue. Remove the RGS Workflow, the Queue, and the Group from the Skype or Business CSCP Control Panel. This step has to be completed first if the same phone number is being reused or last if a new phone number is being used. Special Thank You! I want to give a special thank you to anynode for giving me a license to use their SBC for this guide. Be sure to check out their amazing product at https://www.anynode.de/ Feel free to reach out by commenting below if you have any questions!

Posted in Skype for Business

December 4th, 2019 by UC Now Skype/Teams News Feed

Onboarding is a painful experience at many organizations. Managers are busy, and welcoming a new hire can fall through the cracks. Thinking about onboarding communication as a business solution means workflows, updates, and notifications galore. But the good news is that you can swoop to the rescue with a smart use of Flow.

Posted in Skype for Business