Microsoft 365의 기능은 사용자가 구독, 계정 설정, 청구 정보를 관리할 수 있도록 돕습니다.
Please note that this is the Korean (ko‑kr) forum. I kindly recommend posting your question in Korean so that more community members can assist you effectively. If you prefer using English, you are welcome to post in the English forum instead. I sincerely appreciate your understanding and cooperation.
Hello RyuSaera,
Please note that this is a user‑to‑user community forum. I’m only a moderator here, so I don’t have access to backend systems and I’m not able to manage tenants, perform deletions, or escalate account removal requests on your behalf.
Based on my research and experience, in situations like this, the account is normally managed by the organization’s IT administrator. Since your university IT has already confirmed that they do not manage this unmanaged (viral) tenant and have declined ownership, you technically can leave the tenant as is. In most cases it won’t cause immediate issues, although it may lead to identity confusion later.
The remaining option is to contact Microsoft directly and request their assistance. You can reach Microsoft Support here: https://support.microsoft.com/en-us/home/contact?SourceApp=smc2&ContactUsExperienceEntryPointAssetId=S.HP.SMC-HOME
On that page, type “Delete unmanaged tenant” and press Enter, then choose Contact support. On the Contact support page:
- Product and services: Microsoft 365 and Office
- Category: Technical support
When a Microsoft Support agent reaches out, please explain the following:
- You want to close an unmanaged (viral) tenant that was created using your university email address
- Your university IT administrator has confirmed they do not manage this tenant and has refused ownership
- You are requesting manual account cleanup or deletion by Microsoft
I hope this information is helpful and hopefully Microsoft Support can review the case and assist further.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.