How to permanently delete user account from deleted users without waiting 30 days in Office 365?

Have you encounter below errors after you have been deleted user account and recreated with the same UserPrincipalName in your office 365?

DirSync reports: Unable to restore user from a deleted state because of following error(s): Value 'user@yourdomain.com' for property 'UserPrincipalName' conflicts with another object in the directory.Value ‘user@yourdomain.com’ for property 'ProxyAddress' conflicts with another object in the directory.
Users can sign into https://portal.microsoftonline.com but not able to connect with a desktop client or mobile phone.
Multiple users show up in your Global Address List (GAL)
In Lync you see a the same user multiple times or you see deleted users

In Office 365 Web Portal Admin Center, there is no option to delete account from deleted users list and have to wait until 30days over to permanently delete those account.

So how? Will you wait to do this?

The answer is NO for me.

OK. Here is some tips to delete user account from deleted users list by using power shell.

For example, I'd like to permanently delete testuser1@ictformyanmar.com from deleted users list.

Below is how I am doing with powershell for this. Please modify in highlighted area as your requirement.

Syntax to see deleted users by listing UserPrincipleName and ObjectID
Get-MsolUser –ReturnDeletedUsers | select UserPrincipalName, ObjectId

Syntax to permanently delete user by using ObjectID
Remove-MsolUser -RemoveFromRecycleBin –ObjectId ObjectId

I've attached sample photo of permanently delete testuser1@ictformyanmar.com from deleted users list below.

That's it.

May you all be happy.
(Be knowledgeable,pass it on then)

Comments

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, S

ICT for Myanmar in English

Search This Blog