Microsoft Online Services Sign In Assistant
Hello team, we are looking to roll out office 365. we plan to deploy office 365 pro-plus eventually, but the company needs more proper analysis of the current application compatibility. The project team wants us to deploy exchange online ASAP for quick positive perception of the project, however all users still run on outlook 2010. My question is for outlook 2010 to work with office 365 properly, do we still need to deploy Microsoft online services sign in assistant (MOS-SIA) to all users client PC? what is the effect of this if we eventually upgrade everyone to office 365 proplus? Regards VictorProvision Windows devices from anywhere to support a mobile workforce
In this, our second chapter of the Enabling Remote Work for IT Pros web series, we focus on practical tips to help you effectively provision Windows devices from anywhere. We walk through a variety of strategies, from simple to complex, to help you better understand how to leverage Azure AD Join with Microsoft Intune, or Configuration Manager co-management and task sequences. We then present you with a clear list of the steps you can take now, start soon, or work on in the future. Learn more Here are links to the resources mentioned in this session: Automatic MDM enrollment Using Windows Hello for Business to Access On-Premises Resources Enable Kerberos Managing remote machines with cloud management gateway in Microsoft Endpoint Configuration Manager While not mentioned specifically in this session, here are some additional resources you might find helpful: Microsoft COVID-19 response site Enabling Remote Work Microsoft Endpoint Manager remote work blog Work remotely, stay secure 2 weeks in: what we’ve learned about remote work Frequently asked questions Q: For Hybrid Azure AD join, if we have a line of sight with the domain controller, is the Intune connector required? A: Yes, it’s what gathers an offline domain join blob from your domain controller. Q: Is there a way to define the complete computer name for devices provisioned via Windows Autopilot? A: For Azure AD Join devices, yes, there is a graph API. For Hybrid Azure AD devices, no, there is only the ability to prefix something onto the name. Q: Is there a list of supported VPN clients? A: We don’t have a supported list because we don’t support the configuration of third-party VPN clients. Customers will need to figure out if your VPN works in this scenario. The real question to ask is ‘does your VPN support pre-logon/start before logon auth?’ or some sort of AOVPN. If so, it will work. These are some of the VPN providers we expect to work: Cisco AnyConnect (Win32 client): “Start before Logon” Pulse Secure (Win32 client): “Credential Provider” GlobalProtect (Win32 client): “Pre-logon” Checkpoint (Win32 client): “Auto Connect/Always Connected” Citrix NetScaler (Win32 client): “Always on” SonicWall (Win32 client): “NetExtender on Startup” Note: We do not document or support how you configure your VPN as it is a third-party configuration. Q: Is there a way to get the device enrolled in Windows Autopilot remotely? A: The only way is if it’s currently managed through Intune. You can assign a Windows Autopilot profile with the “Convert devices to Autopilot” option enabled, and the hardware has will be automatically harvested at the next check in. Q: Are there any alternatives to enroll multiple devices, already deployed, besides Windows Autopilot and Bulk enroll using provisioning package files (PPKG)? A: All of the possibilities are documented here: https://docs.microsoft.com/en-us/mem/intune/enrollment/windows-enrollment-methods Q: Is there a way to use White Glove deployment with standard applications without pre-assigning the device to a particular user? A: If you target your applications to devices, then you don’t need to. If the apps are assigned to users, then you need to assign a user. Q: Are we able to deploy the provisioning package files through Intune? A: No, this is not currently supported. Feedback We hope you find this session useful. We'd love your feedback and ideas for future sessions so please fill out this short survey. Thank you!
Add further Office 365 apps to existing installation
Hello community, I would like to add further Office 365 apps (Teams and Visio) to my already existing Office 365 installation. The challenge is to do this without wiping my Word + Excel + Outlook settings / preferences. Which approach would you recommend? 1) Office 365 deployment tool with a customized config.xml? And if so, 1a) check-boxing only the missing apps, or 1b) check-boxing all apps incl. Word + Excel + etc.? 2) The Office 365 setup file that can be downloaded from the Office 365 admin website? 3) Something completely different? Thank you for your advice, and kind regards 🙂 Stefan
New Microsoft 365 Enterprise Foundation Infrastructure poster!
To help you deploy Microsoft 365 Enterprise in your organization, the Microsoft 365 Enterprise Deployment Guide splits its guidance into: The foundation infrastructure, which steps you through six phases to build out networking, identity, and security and your managed Windows 10 Enterprise devices with Office 365 ProPlus. The key productivity workloads and scenarios that build upon the foundation infrastructure and empower your users to creatively collaborate in a secure environment. Although the phases of the foundation infrastructure provide a roadmap with ordered steps and exit criteria, it’s still possible to get lost in the forest with all those trees around. To help you and your IT department see the forest that is each phase, a new Microsoft 365 Enterprise Foundation Infrastructure poster summarizes the overall deployment. For each phase, the poster describes: The ultimate goals for both admins and users The key services, features, and tools needed for deployment Key design decisions The configuration results How to on-board a new user How to monitor and update It’s a quick way to comprehend the important elements of a phase forest before diving into its trees. View it online or download and print it for the wall of your IT department. Enjoy! Joe Davies Technical Writer MicrosoftRemove services from O365 license: PowerShell
Hi Community, Sometimes we need to remove certain services from a license assigned to the users in M365. There're many ways to do it, ( also the Admin Center ), but today we'll see how to list and exclude the desired services using PowerShell. First of all, we need to connect to the cloud: Connect-MsolService And list our available licenses: Get-MsolAccountSku | Select AccountSkuId | Sort AccountSkuId The output should look something like this: Then we need to list the services included in our desired license: (Get-MsolAccountSku | where {$_.AccountSkuId -eq "Company:DEVELOPERPACK_E5"}).ServiceStatus The output looks like this: Finally, we only need to use the "New-MsolLicenseOptions" cmdlt in order to disable the service/s. We can run it for the license itself and apply to the whole Company or use a variable to assign that license with the disabled service to specific users: $LO = New-MsolLicenseOptions -AccountSkuId "Company:DEVELOPERPACK_E5" -DisabledPlans "POWERAPPS_O365_P3" Set-MsolUserLicense -UserPrincipalName email address removed for privacy reasons -LicenseOptions $LO
Get rid of Windows Hello Requirement for sign-in
Hi All, Our company has been testing the use of Intune for a little white and we've run into a weird issue. When we register our test devices in intune, we end up getting notifications saying that our company requires that Windows Hello is set up. Then, whenever we lock the screen, to sign back in we need to put in our PIN. This is annoying, as I want to get rid of the option for the PIN sign in entirely. I remember looking into this before and people said to follow a certain set of instructions to disable the PIN sign in and ONLY allow the password sign in, but this did not work. I want the option for the PIN sign in to be entirely disabled from the back-end (Within Azure/Intune) so that the setting applies to ALL PCs within the test group. Any suggestions? I would like to avoid going on the machine itself and disabling the PIN sign in locally. I want a solution that can be done entirely from within Azure/Intune so we can avoid having end users even seeing the PIN sign in option.
