@itentialopensource/adapter-microsoft_graph 1.0.2 → 1.1.0

package/.eslintignore

@@ -1,4 +1,3 @@
-
 .nyc_output/*
 backup/*
 coverage/*

package/.jshintrc

@@ -0,0 +1,3 @@
+{
+  "esversion": 6
+}

package/AUTH.md

@@ -2,29 +2,33 @@
 
 This document will go through the steps for authenticating the Microsoft_graph adapter with Basic Authentication. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/authentication/" target="_blank">HERE</a>. 
 
-### Basic Authentication
-The Microsoft_graph adapter requires Basic Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
+### Request Token Authentication
+The Microsoft_graph adapter requires Token Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
 
 STEPS  
 1. Ensure you have access to a Microsoft_graph server and that it is running
 2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
 3. Use the properties below for the ```properties.authentication``` field
+4. Note that the token_URI_path has a variable which should be replaced with a valid tenant value
 ```json
 "authentication": {
-  "auth_method": "basic user_password",
-  "username": "<username>",
-  "password": "<password>",
-  "token": "",
-  "token_timeout": 1800000,
-  "token_cache": "local",
-  "invalid_token_error": 401,
-  "auth_field": "header.headers.Authorization",
-  "auth_field_format": "Basic {b64}{username}:{password}{/b64}",
-  "auth_logging": false,
-  "client_id": "",
-  "client_secret": "",
-  "grant_type": ""
-}
+      "auth_method": "request_token",
+      "username": "",
+      "password": "",
+      "token": "token",
+      "token_timeout": 600000,
+      "token_cache": "local",
+      "token_URI_path": "/{tenant}/oauth2/v2.0/token",
+      "invalid_token_error": 401,
+      "auth_field": "header.headers.Authorization",
+      "auth_field_format": "Bearer {token}",
+      "auth_logging": false,
+      "sso": {
+        "protocol": "",
+        "host": "",
+        "port": 0
+      }
+    }
 ```
 4. Restart the adapter. If your properties were set correctly, the adapter should go online. 
 

package/CALLS.md

@@ -19,7 +19,7 @@ These are adapter methods that IAP or you might use. There are some other method
   </tr>
   <tr>
     <td style="padding:15px">healthCheck(callback)</td>
-    <td style="padding:15px">This call ensures that the adapter can communicate with Microsoft_graph. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
+    <td style="padding:15px">This call ensures that the adapter can communicate with Adapter for ServiceNow. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
     <td style="padding:15px">No</td>
   </tr>
   <tr>
@@ -29,7 +29,7 @@ These are adapter methods that IAP or you might use. There are some other method
   </tr>
   <tr>
     <td style="padding:15px">encryptProperty(property, technique, callback)</td>
-    <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Microsoft_graph.</td>
+    <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Adapter for ServiceNow.</td>
     <td style="padding:15px">No</td>
   </tr>
   <tr>
@@ -37,11 +37,6 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations.</td>
     <td style="padding:15px">Yes</td>
   </tr>
-  <tr>
-    <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
-    <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
   <tr>
     <td style="padding:15px">iapSuspendAdapter(mode, callback)</td>
     <td style="padding:15px">This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed.</td>
@@ -57,12 +52,16 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call will return the requests that are waiting in the queue if throttling is enabled.</td>
     <td style="padding:15px">Yes</td>
   </tr>
+  <tr>
+    <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
+    <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
   <tr>
     <td style="padding:15px">iapTroubleshootAdapter(props, persistFlag, adapter, callback)</td>
     <td style="padding:15px">This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls.</td>
     <td style="padding:15px">Yes</td>
   </tr>
-
   <tr>
     <td style="padding:15px">iapRunAdapterHealthcheck(adapter, callback)</td>
     <td style="padding:15px">This call will return the results of a healthcheck.</td>
@@ -83,6 +82,21 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">This call will push the adapter configuration from the entities directory into the Adapter or IAP Database.</td>
     <td style="padding:15px">Yes</td>
   </tr>
+  <tr>
+    <td style="padding:15px">iapDeactivateTasks(tasks, callback)</td>
+    <td style="padding:15px">This call provides the ability to remove tasks from the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapActivateTasks(tasks, callback)</td>
+    <td style="padding:15px">This call provides the ability to add deactivated tasks back into the adapter.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapExpandedGenericAdapterRequest(metadata, uriPath, restMethod, pathVars, queryData, requestBody, addlHeaders, callback)</td>
+    <td style="padding:15px">This is an expanded Generic Call. The metadata object allows us to provide many new capabilities within the generic request.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
   <tr>
     <td style="padding:15px">genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
     <td style="padding:15px">This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet.</td>
@@ -94,23 +108,46 @@ These are adapter methods that IAP or you might use. There are some other method
     <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapHasAdapterEntity(entityType, entityId, callback)</td>
-    <td style="padding:15px">This call verifies the adapter has the specific entity.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapRunAdapterLint(callback)</td>
+    <td style="padding:15px">Runs lint on the addapter and provides the information back.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapVerifyAdapterCapability(entityType, actionType, entityId, callback)</td>
-    <td style="padding:15px">This call verifies the adapter can perform the provided action on the specific entity.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapRunAdapterTests(callback)</td>
+    <td style="padding:15px">Runs baseunit and unit tests on the adapter and provides the information back.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
   <tr>
-    <td style="padding:15px">iapUpdateAdapterEntityCache()</td>
-    <td style="padding:15px">This call will update the entity cache.</td>
-    <td style="padding:15px">No</td>
+    <td style="padding:15px">iapGetAdapterInventory(callback)</td>
+    <td style="padding:15px">This call provides some inventory related information about the adapter.</td>
+    <td style="padding:15px">Yes</td>
   </tr>
 </table>
 <br>
+  
+### Adapter Cache Calls
 
+These are adapter methods that are used for adapter caching. If configured, the adapter will cache based on the interval provided. However, you can force a population of the cache manually as well.
+
+<table border="1" class="bordered-table">
+  <tr>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
+    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapPopulateEntityCache(entityTypes, callback)</td>
+    <td style="padding:15px">This call populates the adapter cache.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+  <tr>
+    <td style="padding:15px">iapRetrieveEntitiesCache(entityType, options, callback)</td>
+    <td style="padding:15px">This call retrieves the specific items from the adapter cache.</td>
+    <td style="padding:15px">Yes</td>
+  </tr>
+</table>
+<br>
+  
 ### Adapter Broker Calls
 
 These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
@@ -129,32 +166,31 @@ These are adapter methods that are used to integrate to IAP Brokers. This adapte
   <tr>
     <td style="padding:15px">getDevice(deviceName, callback)</td>
     <td style="padding:15px">This call returns the details of the requested device.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">getDevicesFiltered(options, callback)</td>
     <td style="padding:15px">This call returns the list of devices that match the criteria provided in the options filter.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">isAlive(deviceName, callback)</td>
     <td style="padding:15px">This call returns whether the device status is active</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">getConfig(deviceName, format, callback)</td>
     <td style="padding:15px">This call returns the configuration for the selected device.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
   <tr>
     <td style="padding:15px">iapGetDeviceCount(callback)</td>
     <td style="padding:15px">This call returns the count of devices.</td>
-    <td style="padding:15px">Yes</td>
+    <td style="padding:15px">No</td>
   </tr>
 </table>
 <br>
 
-
 ### Specific Adapter Calls
 
 Specific adapter calls are built based on the API of the Microsoft_graph. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.
@@ -1134,7 +1170,7 @@ Specific adapter calls are built based on the API of the Microsoft_graph. The Ad
   </tr>
   <tr>
     <td style="padding:15px">inviteaguestuser(body, callback)</td>
-    <td style="padding:15px">Invite Azure AD B2B Guest User using Delegated Permission</td>
+    <td style="padding:15px">Invite a guest user</td>
     <td style="padding:15px">{base_path}/{version}/v1.0/invitations?{query}</td>
     <td style="padding:15px">Yes</td>
   </tr>
@@ -1284,13 +1320,13 @@ Specific adapter calls are built based on the API of the Microsoft_graph. The Ad
   </tr>
   <tr>
     <td style="padding:15px">creategroup(body, callback)</td>
-    <td style="padding:15px">Create group under the connection</td>
+    <td style="padding:15px">Create group</td>
     <td style="padding:15px">{base_path}/{version}/v1.0/external/connections/sampleConnectionId/groups?{query}</td>
     <td style="padding:15px">Yes</td>
   </tr>
   <tr>
     <td style="padding:15px">getgroup(callback)</td>
-    <td style="padding:15px">Get a previously created group under the connection.</td>
+    <td style="padding:15px">Get group</td>
     <td style="padding:15px">{base_path}/{version}/v1.0/external/connections/sampleConnectionId/groups/graphConnectorGroupId?{query}</td>
     <td style="padding:15px">Yes</td>
   </tr>
@@ -1362,8 +1398,7 @@ Specific adapter calls are built based on the API of the Microsoft_graph. The Ad
   </tr>
   <tr>
     <td style="padding:15px">subscriptionvalidation(validationToken, callback)</td>
-    <td style="padding:15px">Allows you to validate whether the notification endpoint you are building properly passed Microsoft Graph Subscription creation validation.
-The response content type should be text/plain, code 200 OK and the body the information passed by the validationToken query parameter</td>
+    <td style="padding:15px">Subscription validation</td>
     <td style="padding:15px">{base_path}/{version}/notification?{query}</td>
     <td style="padding:15px">Yes</td>
   </tr>

package/CHANGELOG.md

@@ -1,4 +1,12 @@
 
+## 1.1.0 [09-26-2023]
+
+* 2023 Adapter Migration
+
+See merge request itentialopensource/adapters/cloud/adapter-microsoft_graph!3
+
+---
+
 ## 1.0.2 [08-24-2023]
 
 * Update utils version to 5 and add oauth support

package/CONTRIBUTING.md

@@ -10,163 +10,4 @@ This project and everyone participating in it is governed by the Code of Conduct
 
 ## How to Contribute
 
-### Reporting Bugs
-
-This section guides you through submitting a bug report. Following these guidelines helps maintainers understand your report :pencil:, reproduce the behavior :computer: :left_right_arrow: :computer:, and find related reports :mag_right:.
-
-Before creating bug reports, please check before-submitting-a-bug-report, as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible. If you have an Itential support contract, please create an Itential Service Desk ticket. If you don't have an Itential support contract, please send an email of the issue to support@itential.com.
-
-#### Before Submitting A Bug Report
-
-* **Check the README.md.** You might be able to find the cause of the problem and fix things yourself. Most importantly, check if you can reproduce the problem __in the latest version__.
-* **Work through the troubleshooting process.** Troubleshooting will include changing the log level of Itential Automation Platform (IAP) and adapters and checking the logs to see what the issues are. These logs should be included in any ticket you open for this issue.
-* **Check for resolutions to the issue.** Check the <a href="https://itential.atlassian.net/servicedesk/customer/kb/view/286883841?applicationId=605994d2-2cb2-3174-af59-ed5b23ff5fd5&spaceKey=PKB&src=1187380921" target="_blank">Itential Knowledge Base</a> to see if there is a known resolution for the issue you are having.
-* **Ask around in chat if you are an Itential employee** to see if others are experiencing the same issue.
-
-#### How to Submit a (Good) Bug Report
-
-Bugs are tracked through the Itential Service Desk. Explain the problem and include additional details to help maintainers reproduce the problem:
-
-- **Use a clear and descriptive title** for the issue to identify the problem.
-- **Describe the exact steps which reproduce the problem** in as much detail as possible. For example, start by explaining how you configured the adapter (e.g., which properties you used and how they were set) or how you are using an artifact.
-- **Provide specific examples to demonstrate the steps**. Include logs, or copy/paste snippets, in your examples.
-- **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
-- **Explain which behavior you expected to see instead and why.**
-- **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use <a href="https://www.cockos.com/licecap/" target="_blank">this tool</a> to record GIFs on macOS and Windows. Use <a href="https://github.com/colinkeenan/silentcast" target="_blank">this tool</a> or <a href="https://github.com/rhcarvalho/byzanz-guiz" target="_blank">program</a> on Linux.
-- **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened and share more information using the guidelines below.
-
-Provide more context by answering these questions:
-
-- **Did the problem start happening recently** (e.g. after updating to a new version/tag) or was this always a problem?
-- If the problem started happening recently, **can you reproduce the problem in an older version/tag?** What's the most recent version in which the problem does not happen?
-- **Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
-
-Include details about your configuration and environment:
-
-- **Which version of the adapter/artifact are you using?** You can get the exact version by checking the project version in the package.json file.
-- **What's the name and version of the OS you're using**?
-- **Are you running or using IAP in a virtual machine?** If so, which VM software are you using and which operating systems and versions are used for the host and guest?
-- **Are there firewalls between IAP and any other system you are integrating with?** If so, have you tried running curl from the system IAP is on to the other system to verify you have connectivity between the systems?
-
-### Your First Code Contribution
-
-#### Local development
-
-This project can be developed locally on all operating systems. For instructions on how to do this, follow the steps highlighted in the README.md. The README.mdprovides many more details on cloning the repository for local development, how to lint and test your changes. 
-
-#### Development Process
-
-The following provides a local copy of the repository along with dependencies.
-
-```json
-go to the repository you are interested in working on
-click on the Clone button to get the link(s) you can use to clone the repository
-git clone <link to clone the project>
-npm install
-```
-
-Prior to making changes you should create a branch to work in. The branch should be named with the type of change (major, minor or patch) and then a Jira issue number or a description of the issue.
-
-```json
-git checkout -b <name_of_your_new_branch>
-```
-
-Make all of the desired changes.
-
-> **Note:** All code changes should be accompanied by additional Unit and Integration tests to minimize the likelihood that any changes will negatively impact the adapter/artifact as well as to ensure the desired functionality is achieved.
-
-
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Files</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Changes</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">.codeclimate.yml, .eslintignore, .eslintrc.js, .gitignore, .gitlab-ci.yml, .jshintrc, .npmignore</td>
-    <td style="padding:15px">These are foundational files that are used in linting and building of the adapter. Changes to these files are heavily scrutinized and may be implemented in a different manner so that the changes can be implemented across all adapters.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, README.md</td>
-    <td style="padding:15px">These are license and process files for the repository. Changes to these files may require legal review and may also be implemented in a different manner so that the changes can be implemented across all adapters.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">utils/*, adapterBase.js</td>
-    <td style="padding:15px">Changes to these files will rarely be accepted. These are process files that need to be changed through the builder process and migration.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">adapter.js</td>
-    <td style="padding:15px">Changes to this file are code changes. They should be accompanied by the appropriate unit and integration tests. If new methods are added, they should also be added to the pronghorn.json file, otherwise integration tests are likely to fail.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">error.json, propertiesSchema.json</td>
-    <td style="padding:15px">These files are utilized by the Itential Runtime libraries. You can make changes to these files, but the changes should be appending of new errors or properties. Removal of errors and properties can result in rejection of the changes.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">pacakge.json, package-lock.json</td>
-    <td style="padding:15px">The package-lock.json is automatically generated and should only be updated when the dependencies inside of the package.json are modified. You can make changes to the package.json to add additional scripts, add new dependencies, modify names, etc. However, changing the scripts or dependencies that are Itential specific will be overriden during the acceptance process.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">pronghorn.json</td>
-    <td style="padding:15px">Changes to this file are made for integration into IAP. The most common change here is adding new methods that shoud be exposed to the IAP Workflow.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">entities/*</td>
-    <td style="padding:15px">Changes to these files include adding new capabilities, updating existing capabilities, or removing deprecated capabilities in the adapter. Translation configuration can also be modified here.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">test/*</td>
-    <td style="padding:15px">Changes to these files include adding, updating, or removing unit and integration tests in the adapter. Tests should never be removed unless the methods that are being tested are removed also. Both the unit and integration test file should have a marker that identifies where modification can take place. Modifications above that marker are likely to be rejected or implemented in a different manner.</td>
-  </tr>
-</table>
-<br>
-
-> **Note:** It is a best practice to lint and test your code prior to committing changes into the repository. You can lint your code by running **npm run lint** and test it by running **node utils/testRunner.sh**. However, there are pre-commit hooks that will run these scripts when you commit your changes.
-
-Commit the changes to the repository.
-
-```json
-git commit -a -m "<descriptive message>" 
-```
-
-> **Note:** There are pre-commit hooks in place. If the pre-commit hooks fail, you will need to address those issues before moving forward.
-
-Push the changes into the repository. This should only be done after the commit has successfully completed.
-
-```json
-git push origin <name_of_your_new_branch>
-```
-
-Create a Merge Request.
-
-### Merge Requests
-
-- Fill out the provided merge request template.
-- Reference related issues and merge requests liberally.
-- Include screenshots and animated GIFs in your merge request whenever possible.
-- Follow the project Styleguide.
-- End all files with a newline.
-
-## Styleguide
-
-### Git Commit Messages
-
-- Use the present tense ("Add feature" not "Added feature")
-- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
-- Consider starting the commit message with an applicable emoji _(not required)_:
-  - :art: `:art:` When improving the format/structure of the code.
-  - :racehorse: `:racehorse:` When improving performance
-  - :non-potable_water: `:non-potable_water:` When plugging memory leaks.
-  - :memo: `:memo:` When writing documentation.
-  - :penguin: `:penguin:` When fixing something on Linux.
-  - :apple: `:apple:` When fixing something on macOS.
-  - :checkered_flag: `:checkered_flag:` When fixing something on Windows.
-  - :bug: `:bug:` When fixing a bug.
-  - :fire: `:fire:` When removing code or files.
-  - :green_heart: `:green_heart:` When fixing the CI build.
-  - :white_check_mark: `:white_check_mark:` When adding tests,
-  - :lock: `:lock:` When dealing with security.
-  - :arrow_up: `:arrow_up:` When upgrading dependencies.
-  - :arrow_down: `:arrow_down:` When downgrading dependencies.
-  - :shirt: `:shirt:` When removing linter warnings.
-
-__Avoid installing unnecessary packages.__ Do not install packages just because they might be "nice to have". Itential Opensource projects are supposed to be minimal, specific, and compact by design.
+Follow the contributing guide (here)[https://gitlab.com/itentialopensource/adapters/contributing-guide]

package/ENHANCE.md

@@ -18,7 +18,7 @@ npm run adapter:update
 
 If you do not have a Swagger or OpenAPI document, you can use a Postman Collection and convert that to an OpenAPI document using APIMatic and then follow the first process.
 
-If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a> on Dev Site.
+If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
 
 ```text
 Files to update
@@ -66,4 +66,4 @@ Files to update
 * test/integration/adapterTestIntegration.js: add better data for the create and update calls so that they will not fail.
 ```
 
-As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a> on Dev Site.
+As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.

package/README.md

@@ -14,6 +14,7 @@ Some of the page links in this document and links to other GitLab files do not w
   - [Testing](#testing)
 - [Configuration](./PROPERTIES.md)
 - [Using this Adapter](./CALLS.md)
+  - [Authentication](./AUTH.md)
 - [Additional Information](#additional-information)
   - [Enhancements](./ENHANCE.md)
   - [Contributing](./CONTRIBUTING.md)
@@ -47,17 +48,20 @@ These instructions will help you get a copy of the project on your local machine
 
 ### Helpful Background Information
 
-There is adapter documentation available on the Itential Developer Site <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">HERE</a>. This documentation includes information and examples that are helpful for:
+There is <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter documentation available on the Itential Documentation Site</a>. This documentation includes information and examples that are helpful for:
 
 ```text
 Authentication
-Properties
+IAP Service Instance Configuration
 Code Files
-Action Files
-Schema Files
-Mock Data Files
+Endpoint Configuration (Action & Schema)
+Mock Data
+Adapter Generic Methods
+Headers
+Security
 Linting and Testing
-Troubleshooting
+Build an Adapter
+Troubleshooting an Adapter
 ```
 
 Others will be added over time.
@@ -96,6 +100,10 @@ The following list of packages are required for Itential opensource adapters or
     <td style="padding:15px">commander</td>
     <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
   </tr>
+  <tr>
+    <td style="padding:15px">dns-lookup-promise</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
   <tr>
     <td style="padding:15px">fs-extra</td>
     <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
@@ -112,14 +120,14 @@ The following list of packages are required for Itential opensource adapters or
     <td style="padding:15px">mongodb</td>
     <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
   </tr>
-  <tr>
-    <td style="padding:15px">network-diagnostics</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
   <tr>
     <td style="padding:15px">nyc</td>
     <td style="padding:15px">Testing coverage library that is utilized by some of the node scripts that are included with the adapter.</td>
   </tr>
+  <tr>
+    <td style="padding:15px">ping</td>
+    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
+  </tr>
   <tr>
     <td style="padding:15px">readline-sync</td>
     <td style="padding:15px">Utilized by the node script that comes with the adapter;  helps to test unit and integration functionality.</td>
@@ -143,7 +151,6 @@ eslint
 eslint-config-airbnb-base
 eslint-plugin-import
 eslint-plugin-json
-package-json-validator
 testdouble
 ```
 
@@ -172,7 +179,9 @@ tar -xvf adapter-microsoft_graph.tar
 
 ```bash
 cd adapter-microsoft_graph
-npm run adapter:install
+npm install
+npm run lint:errors
+npm run test
 ```
 
 4. Restart IAP
@@ -181,17 +190,20 @@ npm run adapter:install
 systemctl restart pronghorn
 ```
 
-5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
+5. Create an adapter service instance configuration in IAP Admin Essentials GUI
+
+6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
+
+7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
 
-npm run adapter:install can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If this happens you can replace step 3-5 above with these:
+
+For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
 
 3. Install adapter dependencies and check the adapter.
 
 ```bash
 cd adapter-microsoft_graph
-npm run install
-npm run lint:errors
-npm run test
+npm run adapter:install
 ```
 
 4. Restart IAP
@@ -200,11 +212,8 @@ npm run test
 systemctl restart pronghorn
 ```
 
-5. Create an adapter service instance configuration in IAP Admin Essentials GUI
-
-6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
+5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
 
-7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
 
 ### Testing
 
@@ -268,7 +277,7 @@ Test should also be written to clean up after themselves. However, it is importa
 
 ### Helpful Links
 
-<a href="https://www.itential.com/automation-platform/integrations/adapters-resources/" target="_blank">Adapter Technical Resources</a>
+<a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
 
 ### Node Scripts
 

package/SUMMARY.md

@@ -1,8 +1,8 @@
 ## Overview
 
-This adapter is used to integrate the Itential Automation Platform (IAP) with the Microsoft_graph System. The API that was used to build the adapter for Microsoft_graph is usually available in the report directory of this adapter. The adapter utilizes the Microsoft_graph API to provide the integrations that are deemed pertinent to IAP. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
+This adapter is used to integrate the Itential Automation Platform (IAP) with the Microsoft Graph System. The API that was used to build the adapter for Microsoft Graph is usually available in the report directory of this adapter. The adapter utilizes the Microsoft Graph API to provide the integrations that are deemed pertinent to IAP. The ReadMe file is intended to provide information on this adapter it is generated from various other Markdown files.
 
->**Note**: It is possible that some integrations will be supported through the Microsoft_graph adapter while other integrations will not. If you need additional API calls, you can use the Update capabilities provided by the Adapter Builder or request Itential to add them if the Adapter is an Itential opensourced adapter.
+>**Note**: It is possible that some integrations will be supported through the Microsoft Graph adapter while other integrations will not. If you need additional API calls, you can use the Update capabilities provided by the Adapter Builder or request Itential to add them if the Adapter is an Itential opensourced adapter.
 
 Itential provides information on all of its product adapters in the Customer Knowledge Base. Information in the <a href="https://itential.atlassian.net/servicedesk/customer/portals" target="_blank">Customer Knowledge Base</a> is consistently maintained and goes through documentation reviews. As a result, it should be the first place to go for information.
 

package/SYSTEMINFO.md

@@ -1,11 +1,21 @@
 # Microsoft_graph
 
-Vendor: Microsoft_graph
-Homepage: https://Microsoft_graph.com/
+Vendor: Microsoft
+Homepage: https://www.microsoft.com/en-us/
 
-Product: Microsoft_graph
-Product Page: https://Microsoft_graph.com/
+Product: Microsoft Graph
+Product Page: https://learn.microsoft.com/en-us/graph/overview/
 
 ## Introduction
+We classify Microsoft Graph into the Cloud domain as Graph provides Cloud Services.
 
-## Additional Product Documentation
+"Microsoft Graph is the gateway to data and intelligence in Microsoft 365."
+"It provides a unified programmability model that you can use to access the tremendous amount of data in Microsoft 365, Windows, and Enterprise Mobility + Security."  
+
+## Why Integrate
+The Microsoft Graph adapter from Itential is used to integrate the Itential Automation Platform (IAP) with AMicrosoft Graph. With this adapter you have the ability to perform operations such as:
+
+- Build apps for organizations and consumers. 
+
+## Additional Product Documentation
+The [API documents for Microsoft Graph](https://learn.microsoft.com/en-us/graph/api/overview?view=graph-rest-1.0)