- fixes #24: removes links to nodejs sample wiki

Author: baywet

README.md

@@ -26,7 +26,7 @@ extensions:
 
 ![.NET Core](https://github.com/microsoftgraph/aspnetcore-webhooks-sample/workflows/.NET%20Core/badge.svg?branch=master)
 
-Subscribe for [Microsoft Graph webhooks](https://docs.microsoft.com/graph/api/resources/webhooks) to be notified when your user's data changes, so you don't have to poll for changes.
+Subscribe for [Microsoft Graph change notifications](https://docs.microsoft.com/graph/api/resources/webhooks) to be notified when your user's data changes, so you don't have to poll for changes.
 
 This sample ASP.NET Core web application shows how to subscribe for change notifications as well as how to validate and decrypt change notifications with resource data (preview) when supported by the resource.
 
@@ -162,7 +162,7 @@ You can use the ngrok web interface (http://127.0.0.1:4040) to inspect the HTTP
 
 Keep the console open while testing. If you close it, the tunnel also closes and you'll need to generate a new URL and update the sample.
 
->See [Hosting without a tunnel](https://github.com/microsoftgraph/nodejs-webhooks-rest-sample/wiki/Hosting-the-sample-without-a-tunnel) and [Why do I have to use a tunnel?](https://github.com/microsoftgraph/nodejs-webhooks-rest-sample/wiki/Why-do-I-have-to-use-a-tunnel) for more information about using tunnels.
+>See [troubleshooting](./TROUBLESHOOTING.md) for more information about using tunnels.
 
 ## Configure and run the sample
 
@@ -299,7 +299,7 @@ You can suggest changes for Microsoft Graph on [UserVoice](https://microsoftgrap
 
 ## Additional resources
 
-- [Microsoft Graph Webhooks sample for Node.js](https://github.com/microsoftgraph/nodejs-webhooks-rest-sample) (Delegated permissions)
+- [Microsoft Graph Webhooks sample for Node.js](https://github.com/microsoftgraph/nodejs-webhooks-rest-sample)
 - [Microsoft Graph Webhooks sample for Java Spring](https://github.com/microsoftgraph/java-spring-webhooks-sample)
 - [Working with Webhooks in Microsoft Graph](https://docs.microsoft.com/graph/api/resources/webhooks)
 - [Subscription resource](https://docs.microsoft.com/graph/api/resources/subscription)

TROUBLESHOOTING.md

@@ -30,3 +30,21 @@ Make sure the local path where you placed the solution is not too long/deep. Mov
 **The resource cannot be found.* browser page.**
 
 Make sure that a CSHTML view file isn't the active tab when you run the app from Visual Studio.
+
+## Hosting the sample without a tunnel
+
+Microsoft Graph (or any other webhook provider) needs a notification URL that it can reach to deliver notifications. The sample uses localhost as the development server.
+
+Localhost just means this host. If any webhook provider would deliver a notification to localhost, it would be delivering it to itself. Not very useful.
+
+Microsoft Graph can't deliver notifications to localhost. For this reason, we need a tunnel that can forward requests from a URL on the Internet to our localhost.
+
+There are some alternatives that you can consider to try this sample without a tunnel.
+
+### Host the sample on a cloud service
+
+You can host the sample using a cloud service such as Microsoft Azure. Cloud services allow you to expose the notification URL to the Internet. Microsoft Graph can deliver notifications to the URL in the cloud.
+
+Note that in some cases, you'll be able to deploy the sample to a website hosted in the cloud. In other cases, you'll need to set up a virtual machine and install a development environment with the prerequisites listed in the [ReadMe](./README.md#prerequisites).
+
+See your cloud provider's documentation for details about how to host a web application or virtual machine using the cloud service.