 Tony says, I plan to install a new local standalone server for manufacturing software that requires SQL Express. The server will not be connected a local domain and configured to not perform any typical server roles except remote app publishing. And remote access for manufacturing software support and admin for me. All client machines and users within the business are now enrolled at Microsoft 365 Business with some business premium with Intune, meaning we no longer have a local domain controller and AD is within Intune Azure. Here's my question. What is the best practice for standalone server setup? Do I install the new server operating system and straight sign in with an admin 365 account or use admin on Microsoft, thus enrolling straight into Microsoft 365? I'm confused. Yeah. It was easy. That wasn't as scary as I thought it was going to be. Yeah, before we started recording here, I believe Mike said this one was easy. It is. I even said it before you said the question, but listening to it again, I'm a little confused. So I just want to make sure, because this is one of those questions that we always talk about where we need Johnny 5, we need more input, right? A standalone server, piece of cake, right? You're just installing the new OS and if you are going to have this thing talking to Intune, which I see here that that is one of their objectives, is to sign in with a regular domain account. Don't use the on Microsoft account. You should really never be using the on Microsoft account, because what it is is that's a backdoor. That's what the original intent of on Microsoft, yourdomain.onmicrosoft.com, the reason why they created that is because, number one, for onboarding, but number two, it was a backdoor. So if you ever lost your domain, you can still get into your tenant. I just had to use that. That's such a good point because I just had to use that recently. Yeah, that's part of the reason why it was created. So there's really no reason when you're setting up something that's going to be in production, because you're talking about SQL Express and it won't be performed in typical server roles except, and then you have remote app publishing, which is a big server role, because it's like you're running Citrix, but you're actually running terminal services, and remote access for manufacturing support and admin for me. So you're setting up a server to access remotely, applications remotely. This server is going to be doing a lot of work. You make it, you know, not to make it sound like it's not doing any work, but it actually is. And this server needs to be connected to Intune in order to be managed by Intune. So install it with an OS, install it with a regular domain account in M365 and just install, you know, the role of the remote or the terminal services. They call it remote app now and, you know, make sure you have your proper licensing on it because you need extra SKUs in order to enable that. And that's it. You should be, you should be good to go. Local domain controller doesn't play into this if you have Intune integrated with AAD. So there's really no issue there. And it says the server will not be connected a local domain. If you're working with Intune, it shouldn't be connected to a local domain. It should be connected to AAD anyway. So that's about it. Simple. It's just that easy. And again, silence. It's again, silence. It's like, whenever I get an explanation talking about, you know, Azure, because I'm an Azure person. I'm not an office person. Christian always used to give me grief because everybody would sit there and go, hmm, is he really telling the truth here? Does he know what he's talking about? No, I will read. I will be the first to admit. We all love you, Mike. We all love you. What are you talking about? I mean, I'm not an office person. That's what you're there for. That's what all of you are. You are here for Azure number one, SharePoint number two, telephony number three. We all know that. Oh, wait. Teams comes before that. Teams comes before you.