Deployment Process

Interested in the deployment process? You're in the right place 📍

Prerequisites ✅

The prerequisites can be found in the Technical Product Description. We encourage you to look through the entire description, but here's an excerpt for your convenience:

As a true SaaS application, there are no requirements for customers to host or install any part of the service. The only requirement for the customer is to consent to the edison365 Azure AD application so that the application has the required access to the Microsoft 365 Graph API services for your Microsoft 365 tenant. The API permissions edison365 requires for full functionality are listed below, these are the Delegated permission Type:

Admin consent required:

  • Read all groups
  • Read all user's full profiles
If you've got questions about anything please reach out!

Security Review 🔐

Need to cross some Is and dot some Ts? We get it. Please review the rest of our Technical Docs to answer any burning questions. If you need some further documentation or we're missing an area of interest, please let us know.

Deployment Form 📑

When you've got your prerequisites finished up, fill out this form to confirm the details and schedule a deployment date. the first half of the deployment form

Deployment 🛫

Once we have all your pre-requisites, it's our turn

Typical Next Steps:

  • We will confirm receipt of your prerequisites and ask any necessary follow-ups
  • Our product team will spin up the new tenant with the details requested
  • On or before the Requested Install Date we will send you the new details of the instance and request that you do some initial testing

Initial Testing ⌨🖱

Once deployed, it's important to kick the tires and make sure everything is working properly. 

Some things to test:

  •  Make sure the admin (specified in the deployment form) can access and add users
    • Add a secondary admin as a backup
    • If you'd like a designated service account for edison365 this can be requested
      • useful for troubleshooting or access issues
    • If you have procured implementation services, make sure to invite your consultant to your Azure AD
      • consultants help to configure your new instance to your specifications for a set period of effort
  • Your Azure AD Admin will need to accept the tenant-level permissions
    • If your edison365 admin is also an Azure AD Admin, they can do this when prompted in the application
    • If not, you'll need to ask your Azure AD Admin to find the edison365 application in the Azure Enterprise Applications and accept the permissions there
  • Check to see the default configuration looks appropriate
    • There should be
      • 108 Default and System Fields
      • 11 Default Tables
      • 1 Default Project Form
      • 1 Default Project Card
      • 1 Basic Project Workflow
      • A Basic Project Template
      • 3 Default News Items
      • 1 Default Calendar (M-F)

Tip: Don't worry, you don't have to count by hand, check the bottom right for the total.