Remove-MsolUser

Removes a user from Azure Active Directory.

Syntax

Copy
PowerShell
Remove-MsolUser [-Force] -ObjectId <Guid> [-RemoveFromRecycleBin] [-TenantId <Guid>] [<CommonParameters>]
Copy
PowerShell
Remove-MsolUser [-Force] [-RemoveFromRecycleBin] [-TenantId <Guid>] -UserPrincipalName <String>
 [<CommonParameters>]

Description

The Remove-MsolUser cmdlet is used to remove a user from Azure Active Directory. This cmdlet deletes the user, their licenses, and any other associated data.

Examples

Example 1: Remove a user
Copy
PowerShell
Remove-MsolUser -UserPrincipalName "davidchew@contoso.com"
This command removes the user davidchew@contoso.com from Azure Active Directory. If the user has any licenses, the cmdlet removes these. The command prompts you to confirm the operation.
Example 2: Remove a user without confirmation
Copy
PowerShell
Remove-MsolUser -UserPrincipalName "davidchew@contoso.com" -Force
This command removes davidchew@contoso.com from Azure Active Directory. If the user has any licenses, the cmdlet removes these.
Example 3: Remove a user from the Recycle Bin
Copy
PowerShell
Remove-MsolUser -UserPrincipalName "davidchew@contoso.com" -RemoveFromRecycleBin
This command removes davidchew@contoso.com from the Azure Active Directory recycle bin. The command prompts you to confirm the operation. This command permanently removes the user.

Parameters

-Force
Indicates that this cmdlet does not prompt you for confirmation.

Type:SwitchParameter
Required:False
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
-ObjectId
Specifies the unique object ID of the user to remove.

Type:Guid
Required:True
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-RemoveFromRecycleBin
Indicates that this cmdlet permanently removes a deleted user from the recycle bin. This operation which can be applied only to deleted users. When this operation has been completed, you will not be able to recover the user by using the Restore-MsolUser cmdlet.

Type:SwitchParameter
Required:False
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-TenantId
Specifies the unique ID of the tenant on which to perform the operation. The default value is the tenant of the current user. This parameter applies only to partner users.

Type:Guid
Required:False
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False
-UserPrincipalName
Specifies the user principal name of the user to remove.


Type:String
Required:True
Position:Named
Default value:None
Accept pipeline input:True (ByPropertyName)
Accept wildcard characters:False

Commenti

Posta un commento

Post popolari in questo blog

Come e quando smantellare i server Exchange in una distribuzione ibrida

Immagine
Articolo tratto da technet di microsoft . Una delle opzioni più interessanti per ottenere una società a Exchange Online è quello di utilizzare l'approccio distribuzione ibrida descritto nel  Piano di una distribuzione ibrida di Exchange Online in Office 365  . Questa è l'unica opzione che permette di facilmente a bordo e caselle di posta off-board (tutte le altre opzioni native sono sul bordo). Oltre alla capacità di off-board, una configurazione ibrida ha le seguenti opzioni principali: Questo argomento vi aiuterà a capire le opzioni per lo smantellamento di cambio ibrido, e quando ognuno di queste opzioni dovrebbe essere attuato. Ci sono molte variazioni a quando e come disattivare i server ibridi di Exchange. Prendendo il tempo di comprendere le implicazioni e pianificare correttamente la disattivazione totale o parziale dei server locali è importante. Disponibilità tra sedi  . Questo ti permette di vedere / informazioni sulla di...
Continua a leggere

Manage Room Mailbox by using PowerShell

In the current article, we will review how to use PowerShell commands for managing Room mailbox in Exchange Online environment. Resource Mailbox is a special type or a Mailbox that uses for the management of meeting Rooms and Equipment. The Resource Mailbox doesn’t require a license. Management of Resource Mailbox could be implemented by using one of the following options: Self-management – the Resource Mailbox will be configured for automation of accepting meeting requests (or decline meeting request if a former meeting request was already set). Resource Mailbox delegate – The delegate is the person that will accept the meeting requests and approve or decline the meeting requests. The term “resource Mailbox” includes two types of Mailboxes – Room Mailbox and Equipment Mailbox. There is a small difference between the two types of the resource mailbox but the use, and the purpose are quite similar (most of the examples will relate to room Mailbox). A Little confession: ...
Continua a leggere

How to reset an Office 365 install to the initial activation/install state

Immagine
1.   Remove Office 365 license for Subscription based installs (not Shared Computer Licensing scenarios): To remove the Office 365 license, you must run two cscript command lines. The command lines are:         A. Run  C:\program files <x86>\Microsoft office\office15>cscript ospp.vbs /dstatus The above command line will generate a report of the currently installed/activated license.  (See Below) NOTE: You might see multiple licenses in the /dstatus report.         B. Make note of value for “ Last 5 characters of installed product key”         C.  Run  C:\program files <x86>\Microsoft office\office15>cscript ospp.vbs /unpkey:“Last 5 of installed product key”   For example:   C:\program files <x86>\Microsoft office\office15>cscript ospp.vbs /unpkey:WB222  (See Below) Repeat the st...
Continua a leggere