Node.js Added documentation and cross-link for Azure site extension

src/content/docs/apm/agents/nodejs-agent/getting-started/monitor-your-nodejs-app.mdx

@@ -51,6 +51,14 @@ We have a few paths to install the Node.js agent, depending on what you're monit
 
     If you have a preference for manual installation via the command line, we currently have the option for [Legacy instrumentation for Lambda monitoring](/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/enable-serverless-monitoring-aws-lambda-legacy/#node).
   </Collapser>
+
+  <Collapser
+      id="azure"
+      title="Azure web app on Windows"
+  >
+    If you'd like to instrument an Azure Web App (provided that it's on Windows and deployed as code), you can easily install and configure the New Relic Node Agent with the [Azure Node Agent Site Extension](/docs/agents/nodejs-agent/hosting-services/nodejs-agent-microsoft-azure).
+
+  </Collapser>
 </CollapserGroup>
 
 ## What's next? [#next]

src/content/docs/apm/agents/nodejs-agent/hosting-services/nodejs-agent-microsoft-azure.mdx

@@ -4,12 +4,59 @@ tags:
   - Agents
   - Nodejs agent
   - Hosting services
+  - Azure
+  - Azure Site Extension
 metaDescription: How to install APM for Node.js on Microsoft Azure Web Apps.
 redirects:
   - /docs/agents/nodejs-agent/hosting-services/nodejs-agent-microsoft-azure
+  - /docs/agents/nodejs-agent/installation-configuration/install-nodejs-agent-azure-site-extension
   - /docs/nodejs/nodejs-agent-on-microsoft-azure
+translate:
+  - jp
+  - kr
 freshnessValidatedDate: never
 ---
+## Easy Install with the New Relic Azure Site Extension for Node [#site-extension-install]
+
+You can install the Node.js agent onto your Azure-managed web apps with the New Relic Azure Site Extension for Node. This doc walks you through compatibility, installation, and configuration to get your Azure web app data into New Relic.
+
+## Compatibility and requirements [#compatibility-requirements]
+
+Azure Site Extensions are only available for Windows-based App Service apps that are deployed as code. For applications running on Windows 32, full Code Level Metrics support (file path, line, column) is not available. Profiling falls back to function name only.
+
+## Install the Node.js agent with Azure Site Extension
+
+To install the New Relic Azure Site Extension, add the `NewRelic.Azure.WebSites.Extension.NodeAgent` site extension from the Azure home page. Follow these steps:
+
+1. From the Azure Home page, click the App Services tile, then select the target application in the displayed list.
+2. Scroll down to <DNT>**Extensions**</DNT> in the options listed on the left under the <DNT>**Development Tools**</DNT> category.
+3. Click on <DNT>**+ Add**</DNT> at the top of the page to toggle the extension drop down, then select <DNT>**New Relic Node Agent**</DNT>. Check the box for accepting the legal terms
+4. Click <DNT>**Add**</DNT> on the bottom of the page to start installing the extension.
+
+Once installed, the extension creates the following artifacts:
+
+- Folder: `C:\home\SiteExtensions\NewRelic.Azure.Websites.Extension.NodeAgent`
+- XDT: `applicationHost.xdt` that will add the necessary `NODE_OPTIONS` environment variable on application startup
+- The New Relic Node agent and dependencies will be installed into `C:\home\site\wwwroot\node_modules`
+
+If the New Relic agent has been installed successfully and logging has been enabled, the agent will append its logs to a file at `C:\home\site\wwwroot\newrelic_agent.log`. If the extension fails to install, a log file is created at `C:\home\SiteExtensions\NewRelic.Azure.Websites.Extension.NodeAgent\install.log`.
+
+## Configure the Node.js agent [#configure-agent]
+
+The New Relic Node agent is configured with the `newrelic.js` file, or via environment variables. [See our documentation for more detailed configuration](https://docs.newrelic.com/docs/apm/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration/).
+
+Once the site extension is installed, you'll need to manually enter one configuration item before restarting your application.
+  - On the options listed on the left, scroll down to "Environment variables" located under the "Settings" category and add the following:
+    - `NEW_RELIC_LICENSE_KEY` - Your New Relic license key value
+
+The Node agent automatically adds the `NODE_OPTIONS` environment variable with a value of `-r newrelic` which starts the agent.
+  - Note: Any previously defined `NODE_OPTIONS` will be removed and reset with `-r newrelic`.
+
+  <Callout variant="important">
+    We recommend installing or removing this Azure site extension while your web application is stopped.
+  </Callout>
+
+## Manual Installation
 
 Learn about special considerations for using Microsoft Azure Web Apps as a hosting service with New Relic's Node.js agent.
 

src/content/docs/apm/agents/nodejs-agent/installation-configuration/install-nodejs-agent-docker.mdx

@@ -29,7 +29,12 @@ With just a few additions your existing Dockerfile can be used with our Node.js
 
    Install a specific version, or use any of the other options provided by the [`package.json` format](https://docs.npmjs.com/files/package.json#dependencies). Check [the Node.js agent release notes](/docs/release-notes/agent-release-notes/nodejs-release-notes) for information about past agent versions.
 
-2. Depending on how your container is setup, you can edit the `ENTRYPOINT` to include `newrelic` module first with Node.js `-r`/`--require` flag by running `node -r newrelic YOUR_PROGRAM.js`. If you can't control how your program runs, you can load the `newrelic` module before any other module in your program by adding `require('newrelic')`.
+2. Depending on how your container is set up, you can edit the `ENTRYPOINT` to include `newrelic` module first with Node.js `-r`/`--require` flag by running ```node -r newrelic YOUR_PROGRAM.js```
+
+   or ```ENTRYPOINT ['node', '-r', 'newrelic', 'YOUR_PROGRAM.js']```
+
+   If you can't control how your program runs, you can load the `newrelic` module before any other module in your program by adding `require('newrelic')`.
+
 
    <Callout variant="tip">
      If you have an npm script to run your program such as `npm start`, you can programmatically modify this script by running `npm pkg set scripts.start="node -r newrelic your-program.js"`.
@@ -57,19 +62,25 @@ With just a few additions your existing Dockerfile can be used with our Node.js
   Don't include your license key in your Dockerfile or Docker image. For more information, see [our documentation on license key security](/docs/accounts/install-new-relic/account-setup/license-key#license-key-security).
 </Callout>
 
-In addition to setting your application name or license key, you can set [other configuration options](/docs/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration) by starting your container with the `-e` option. For example, to enable [distributed tracing](/docs/understand-dependencies/distributed-tracing/get-started/introduction-distributed-tracing), use:
+<Callout variant="tip">
+  If your Node.js agent is older than [v8.3.0](/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-8-3-0) and you want to use [distributed tracing](/docs/understand-dependencies/distributed-tracing/get-started/introduction-distributed-tracing), you'll need to enable it by setting the environment variable `NEW_RELIC_DISTRIBUTED_TRACING_ENABLED` to `true`.
+</Callout>
+
+
+In addition to setting your application name or license key, you can set [other configuration options](/docs/agents/nodejs-agent/installation-configuration/nodejs-agent-configuration) by starting your container with the `-e` option. For example, to enable a feature flag, use:
 
 ```bash
  docker run -e NEW_RELIC_LICENSE_KEY=YOUR_LICENSE_KEY \
         -e NEW_RELIC_APP_NAME="YOUR_APP_NAME" \
-        -e NEW_RELIC_DISTRIBUTED_TRACING_ENABLED=true \
+        -e NEW_RELIC_FF_ENABLED=true \
         YOUR_IMAGE_NAME:latest
 ```
+(You'll replace `FF` with the name of the feature flag you want to enable.)
 
 You can also set configuration options in your Dockerfile using `ENV` directives:
 
 ```dockerfile
-ENV NEW_RELIC_DISTRIBUTED_TRACING_ENABLED=true \
+ENV NEW_RELIC_FF_ENABLED=true \
     NEW_RELIC_LOG=stdout
     # etc.
 ```