`Microsoft.PowerPlatform.Administration.UserManagement` - how to use Multi-Factor authentication?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, powershell
- Domain
- authentication, documentation
Research direction
Review the scripts under powershell/UserManagement/Microsoft.PowerPlatform.Administration.UserManagement and the referenced Connect-AzureAD documentation first. Determine whether the sample supports MFA and document the supported authentication path or limitation, with completion marked by clear usage guidance for organizations requiring MFA.
Written by the indexing model from the issue text.
Description
How to use multi-factor authentication using the Microsoft.PowerPlatform.Administration.UserManagement powershell scripts? Many organizations mandate the use of Multi-Factor auth, especially for priviliged roles (such as what this script requires)
The documentation for the Connect-AzureAD module states that MFA can't be used with the Connect-AzureAD method been used in the script
PS C:\> Connect-AzureAD -Credential $Credential
The first command gets the user credentials, and then stores them in the $Credential variable.
The second command connects the current PowerShell session using the credentials in $Credential.
This account authenticates with Azure Active Directory using organizational ID credentials. You cannot use multi-factor authentication or Microsoft account credentials to run Azure Active Directory cmdlets with this account.```
- Dominant language
- C#
- Stars
- 2k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-Samples
-
PowerShell
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/PowerApps-Samples#797 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/PowerApps-Samples#817 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/PowerApps-Samples#815 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/PowerApps-Samples#812 ·
-
Support issue
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/PowerApps-Samples#796 ·
All issues in microsoft/PowerApps-Samples
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·