Startup configuration for Authentication and Authorization

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
>I am unable to replicate this sample with an android application communicating with other end points that are not Microsoft Graph. I am successfully authenticating and generating both an id_token with the correct scope captured in the scp claim and an access token as well being used as a bearer token. I keep getting a 401 error both on my android app and postman. I am suspecting that it has to do with how I have setup the authentication and authorization in my startup file. Please provide some guidance with the scenario where my web application which users logon directly through AD B2C and also has end points which can been accessed by the android application after a user logons on and generates a bearer token based on the same logic documented here

### Any log messages given by the failure
>

### Expected/desired behavior
>

### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

### Versions
>

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

El issue menciona la configuración de startup, un cliente Android, Postman, AD B2C, tokens bearer y una respuesta 401. Empieza comparando el flujo de autenticación documentado del ejemplo con el escenario solicitado sin Graph API; se considera hecho cuando se hayan añadido instrucciones claras de configuración para la aplicación web y los endpoints a los que accede Android.

Escrito por el modelo de indexación a partir del texto del issue.