Deploy, test, and extend

This is step 4 of the process to migrate apps.

  1. Test throughly

    Once you've updated your app, test it thoroughly to verify that it works as expected and that you haven't introduced any regressions.

    Be sure to use multiple environments, data sets, and end-user personas, e.g. credentials with different roles, rights, and responsibilities. Go through the entire lifecycle, by having a new test user acquire the app for the first time, as well as an existing user (who already consented) trying to use the app again.

  2. Deploy staged updates

    Consider deploying your updates in stages. A limited roll-out to a small set of friendly users can help identify glitches and other potentially-embarrassing issues. This also gives you a chance to monitor initial reception and feedback.

    If the initial roll-out goes well, monitor progress as you deploy to larger audiences.

  3. Explore new value

    Now you've made the switch to Microsoft Graph, it's never been easier for you to unlock many more datasets and features that are now at your fingertips. Microsoft Graph supports many new Azure AD datasets and features that are not available in Azure AD Graph, including:

    Microsoft Graph offers access to many more services than just Azure Active Directory. It's the API gateway to Microsoft 365 services too. Check for new datasets and capabilities regularly.

    • Take a look at what you can do with Microsoft Graph
    • Explore the Microsoft Graph blog for the latest news about Microsoft Graph and some great learning series.
    • The changelog summarizes service and document updates. Following these updates will help you track new APIs introduced to /beta (preview) and those promoted to v1.0 (GA). These new APIs can provide new ways for you to add more value and new experiences to your apps.

See also

If you run into problems or need help during the migration process, you can:

Next Steps