Problem deploying Microsoft 365 DSC configuration
Hello all! I have been workin on a little demo on Microsoft 365 DSC and i have been running into the same problem while trying to deploy a configuration. So basically i want to make a new 365 Group with code, (see below) and this is the error i always get. (2 pictures) I think i am connected toConnect-MgGraph, is says it also. The configuration code: Configuration CreateO365Group { param( [Parameter(Mandatory = $true)] [PSCredential] $Credential ) if ($null -eq $Credential) { <# Credentials #> $Credscredential = Get-Credential -Message "Credentials" } else { $CredsCredential = $Credential } $OrganizationName = $CredsCredential.UserName.Split('@')[1] Import-DscResource -ModuleName Microsoft365DSC -ModuleVersion '1.24.626.1' Node localhost { O365Group '1234' { Credential = $Credscredential DisplayName = "Tesztelt feltoltes12" MailNickName = "EmployeesHello1234" Description = "Feltoltes1234" ManagedBy = @("enokgabor@$OrganizationName") Members = @() Ensure = "Present" } } } CreateO365Group -ConfigurationData C:\demoUse\ConfigurationData.psd1 -Credential $Credscredential The Powershell messages:Join the New Adobe and Microsoft Partnership Group on LinkedIn
On behalf of the Adobe and Microsoft partnership team, I'd like to invite you to join our Adobe and Microsoft partnership LinkedIn group: Expand possible, together - Adobe & Microsoft. Adobe and Microsoft have partnered to deliver the solutions businesses need with our secure, trusted technology and productivity platforms that empower millions of users around the world. Our mutual expertise in helping businesses organize their data to activate their audiences and delivering a modern customer experience is what makes this partnership so special. Our community aims to provide meaningful and educational content that helps you meet your business goals. Here are some of the things you can expect to find in this LinkedIn group: • Updates on the latest Adobe and Microsoft partnership developments • ‘Better together’ stories that give insight into the business benefits / opportunities the partnership brings. • Exclusive insights direct from Adobe and Microsoft leaders. Please join us today. Stay tuned for updates, and we look forward to engaging with you this year!
WOPI integration for Co-Authoring
Hello Everyone, I have implemented WOPI MS OFFICE integration on our systems and everything is working fine for a single user but Co-Authoring is not working for me, I am not able to see the other user on the same document, I have tried everything but I am not able to figure out the Co-Authoring part. Additionally, I don't have CSPP Plus, do we need CSPP Plus for Co-Authoring on the web to work? I have implemented Locks and everything following thislink ,it would be a great help if anyone can help with this Thanks
unable to install Multi User Office after configuring with Office Deployment Tool
Our agency used the Office Deployment Tools to generate the files and configuration.xml needed for installing Office 365 as a MultiUser license. I start it in an elevated command prompt and run the command of setup.exe /configure configuration.xml. I get the initial splash screen and then follow up splash screen with progress bar, but it doesn't progress past about 2% of the install. I even left it overnight and it never went any further. Network doesn't appear to be blocking it. Another note I saw said TLS 1.2 is needed and I have checked that selection in the internet options. Any other thoughts on what might be stopping this installation?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.Mobile Application Management for Windows (NEW)
This newly released product is now available in Public Preview, and I'm excited to share my initial impressions. MAM enables users to stay productive on any device while ensuring the security of our data. Mobile Application Management for Windows enables us to; Apply policies to corporate applications on personal devices. No enrollment required, just an Azure AD (or MEID) registration. Place restrictions suchas cut/copy/print and blocking incoming or outgoing data. Integration with the Mobile Threat Defense connector to detect local health threats. Block access or wipe corporate data based on specific conditions. In this blog post, I provide a first look at the configuration and user experience of MAM for Windows. First look at Mobile Application Management for Windows - Myron Helgering's BlogM365 licences - Shared Accounts and terms of service
Hi guys, I have come across a client that is using shared M365 licenced accounts, e.g. 1 licenced account, used by 5 "real" people. I can strongly assume this is against terms of service, but I cannot find reference of this written anywhere. Can someone point me to the relevant information so I can reference it so I can resolve this matter with the client and ensure that they are fully compliant. Thanks,
