title: What is the difference between a Native Application & Server Application when talking about ADFS Application Groups?
body: <p>I'm new to Federation Services and I'm trying to understand how ADFS works as a whole and I've started to get down into the details. I followed along with creating an app using OIDC to authenticate a user, however, within the tutorial, they specified using a "Server Application" when setting up an Application Group.  This ended up not working for me so I tried setting up a "Native Application" application group for kicks and was able to successfully login.</p>
  
  <p>The thing that threw me off is, I ended up hosting ADFS on a server outside of the domain in which I had my application running, so I'm confused as to how that is "native" in terms of ADFS.</p>
  
  <p>I went looking for this answer within microsoft's documentation but I didn't find the information very clear.</p>
  
  <p><strong>Native Application:</strong></p>
  
  <p>"Sometimes called a public client, this is intended to be a client app that runs on a pc or device and with which the user interacts."</p>
  
  <p><strong>Server Application:</strong></p>
  
  <p>"A web application that runs on a server and is generally accessible to users via a browser. Because it is capable of maintaining its own client 'secret' or credential, it is sometimes called a confidential client."</p>
  
  <p>This may seem simple to some, but I'm trying to really get a grip on what would be used when.  To me it sounds like a native application is used when you're running the application natively on a pc in which the user is also using the same pc, and the server application is run remotely in which the user would not be using the same machine. Is it really that simple or am I misunderstanding?</p>