< Back
Remove-GoogleDirectoryUserPhoto
Post
NAME Remove-GoogleDirectoryUserPhoto
SYNOPSIS
Deletes a GSuite user's photo.
SYNTAX
Remove-GoogleDirectoryUserPhoto [-UserId] <String> -BearerToken <String> [<CommonParameters>]
Remove-GoogleDirectoryUserPhoto [-UserId] <String> [-ProfileLocation <String>] [-Persist] [<CommonParameters>]
DESCRIPTION
This cmdlet deletes a user's photo. Once deleted, the user's photo is not shown.
Wherever a user's photo is required, a silhouette will be shown instead.
PARAMETERS
-UserId <String>
The Id of the user to delete the photo of. The UserId can be the user's primary email address, the unique user
id, or one of the user's alias email addresses.
Required? true
Position? 1
Default value
Accept pipeline input? false
Accept wildcard characters? false
-BearerToken <String>
The bearer token to use to authenticate the request.
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ProfileLocation <String>
The location where stored credentials are located. If this is not specified, the default location will be used.
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Persist [<SwitchParameter>]
Indicates that the newly retrieved token(s) or refreshed token and associated client data like client secret
are persisted to disk.
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
None
OUTPUTS
None
NOTES
AUTHOR: Michael Haken
LAST UPDATE: 2/12/2018
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>Remove-GoogleDirectoryUserPhoto -UserId liz@example.com -ClientId $Id -Persist
Deletes the photo for the user liz@example.com using stored client credentials and bypasses confirmation.
RELATED LINKS
SYNOPSIS
Deletes a GSuite user's photo.
SYNTAX
Remove-GoogleDirectoryUserPhoto [-UserId] <String> -BearerToken <String> [<CommonParameters>]
Remove-GoogleDirectoryUserPhoto [-UserId] <String> [-ProfileLocation <String>] [-Persist] [<CommonParameters>]
DESCRIPTION
This cmdlet deletes a user's photo. Once deleted, the user's photo is not shown.
Wherever a user's photo is required, a silhouette will be shown instead.
PARAMETERS
-UserId <String>
The Id of the user to delete the photo of. The UserId can be the user's primary email address, the unique user
id, or one of the user's alias email addresses.
Required? true
Position? 1
Default value
Accept pipeline input? false
Accept wildcard characters? false
-BearerToken <String>
The bearer token to use to authenticate the request.
Required? true
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ProfileLocation <String>
The location where stored credentials are located. If this is not specified, the default location will be used.
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Persist [<SwitchParameter>]
Indicates that the newly retrieved token(s) or refreshed token and associated client data like client secret
are persisted to disk.
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
None
OUTPUTS
None
NOTES
AUTHOR: Michael Haken
LAST UPDATE: 2/12/2018
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>Remove-GoogleDirectoryUserPhoto -UserId liz@example.com -ClientId $Id -Persist
Deletes the photo for the user liz@example.com using stored client credentials and bypasses confirmation.
RELATED LINKS