 says, I have a Microsoft 365 user without license. It's very James Bond-ish user without license. Anyone know how do I redirect email inside or outside in which him is the recipient to other mailbox? I've created an exchange rule where if recipient address has some words, this email will be forwarded to me, but I receive a non-exist error email. Can anyone translate that? What I read was blah, blah, blah, blah, blah, blah. No license. When he sets up an Outlook rule and he tries to do something to a unlicensed mailbox, it's like, sorry buddy, you're cut off. Because there's no license? Yeah. Again, do we need an alias or fork out the five bucks a month for their license? They need the license to do anything I would think. It's just going to have to, regardless of the rule. It's like if it sees particular words forwarded to over here, but that's got to be a licensed account. I wonder if it's like, you see people, they have employees that leave and then they want to use their incoming email because it's already set up with things, or people are already sending things to them, and they're like, why do I want to pay for the user because they're not there anymore, but I want to use their inbox and guys, like that's just not a thing. Either pay for the license and deprecate the user step and update all your materials, or pay for the license and do like a forever forward and just deal with it. Or could it again be an alias? Maybe. Depends because it sounds like you study it to mailboxes to work together, but not. An alias would work because there's still a license to use or behind that. You can have multiple aliases. Yeah. They need to be synchronized thing. Yeah. For new emails, not for the old emails, they'd have to make the old emails still. I wonder if you could hack it by putting an alias on an Office 365 group mailbox. I don't think you can create an alias. There's also some rules for creating. I don't think you can do that, but I also know you can't create an alias unless the mailbox is gone because like that name is owned. You'd have to essentially get rid of that for like, it would have to be completely deleted first to even create the alias to begin with. Because doesn't it hold it in kind of hostage state for a certain period of time? What is it like 90 days or something before it's pushed out there? You can go run a PowerShell, you can purge it, but the otherwise it's 90 days. How did you have? Were you saying something? Did you have a good idea? No. He's like, no. No, that's pretty much it. Yeah. Well, the one other thing about that, and of course it doesn't sound like he's got any involvement at all. But if he's attempting to use exchange the forward outside of its own domain, it won't do that unless you go in the administrative tools and set it up that way. Because that's to prevent email loops it will not forward outside of the domain. Without authorization and you actually thrown a switch, I should say any automatic response is not permissible. That's basically what he's doing with the rule is an automatic response. Those simply aren't permitted unless unless you've specifically told exchange that you won't do that.