Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 886
Reply with quote  #1 
The latest version of Azure AD Powershell module supports MFA so now all global admin accounts can have MFA - yeah.
Latest version

You need to remove the previous version with add/remove programs.

One command to find the version used is 

Code:

# get the current version of msonline service
(Get-item C:\Windows\System32\WindowsPowerShell\v1.0\Modules\MSOnline\Microsoft.Online.Administration.Automation.PSModule.dll).VersionInfo.FileVersion


The new version is stored in a new location

Code:

# Find new version
get-Module msonline | Select-Object Name,Version,Path

PS C:\Windows\system32> get-Module msonline | Select-Object Name,Version,Path

Name Version Path
---- ------- ----
MSOnline 1.1.183.8 C:\Program Files\WindowsPowerShell\Modules\MSOnline\1.1.183.8\MSOnline.psd1



To install the latest version, once you remove the old version

Code:

# install next version
Install-Module MSOnline
# or if you get an error
Install-Module MSOnline -force




Nice to see its all really really really really consistent!

No wonder I'm going mad!

Heavily edited in case your on RSS and think you've gone mad!


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
lady_mcse

Avatar / Picture

Senior Member
Registered:
Posts: 103
Reply with quote  #2 

I would really love to have back the number of hours I wasted trying to figure out why I couldn't get into SharePoint online with powershell because mfa was active on my admin account ... but I guess that's water under the bridge now, as I'm finally back to working with MFA on.

Talking about consistency, it has always driven me mad how they seem oblivious to mismatches between GUI and powershell experiences. Examples:
In SharePoint 2010, you would "Retract" a solution in the Admin Center, but with Uninstall-SPSolution. 
In SharePoint 2010, a timer job that appears as "Content Type Subscriber" is called MetadataSubscriberTimerJob if you want to work with it in Powershell. 

In O365 even the security roles are completely crazy. What Microsoft calls them in documentation is different from what you'll find in the Powershell work, and even within the powershell assignments they aren't consistent, like some have an extra "service" thrown in, one has an extra word "support" thrown in, and "Password Administrator" is about as far as you can get from "Helpdesk Administrator." Here's my translator guide on that stuff ...
https://support.office.com/en-us/article/about-office-365-admin-roles-da585eea-f576-4f55-a1e0-87090b6aaa9d

What it says in the support doc ... and what the "display name" is for Powershell work.
Global Administrator = Company Administrator
Billing Administrator = Billing Administrator
Exchange Administrator = Exchange Service Administrator
SharePoint Administrator = SharePoint Service Administrator
Password Administrator = Helpdesk Administrator
Skype for Business Administrator = Lync Service Administrator
Service Administrator = Service Support Administrator
User Management Administrator = User Account Administrator
Reports Reader = Reports Reader
Power BI Administrator = Power BI Service Administrator
Message Center Reader = Message Center Reader

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.