EUCHorizon Cloud Services Advanced Integrations (For Self Paced Learning in the VLP) Day 4Federating AZURE with Workspace ONE Access and Microsoft 365

Federating AZURE with Workspace ONE Access and Microsoft 365

Part 1: Setting Up a Developer Account for Microsoft 365

The purpose of this session is to put in place Office 365 services to demonstrate new integrations VMware now supports with Workspace ONE ACCESS

Failure to complete this section will result in not being able to do the next lab

In this section we will walk through and setup the required developer subscription that allows you a 90 day free trial.

An Important NOTE! 

  • Be sure to to take notes and document your configurations immediately. 
  • Be 100% clear from your document what your assigned domain name is.
  • To be successful with this lab Microsoft require the following:
    • An email account to register that is not associated with any other Microsoft Azure instance.
      • You might have to have created a dummy gmail account
      • If you create a dummy outlook account. The steps in your lab could be marginally different
    • A valid telephone number that is not associated with another Azure Instance
Part 1: Setting Up a Developer Account for Microsoft 365
  1. On your ControlCenter server
    • Open a new Chrome browser session
    • Navigate to the following URL:
      •  https://developer.microsoft.com/en-us/microsoft-365/dev-program
        • Do not select JOIN NOW.
  1. On your Chrome Browser
    • To the right of the page
      • select Sign In

  1. On Microsoft Sign in Page
    • Next to:
      • No account? select Create one!
  1. Under Create account
    • Enter an email address
      • This email cannot be associated with an existing AZURE account
    • Select Next
  1. Under Create a password
    • Enter your password
      • Ensure this documented carefully
    • Select Next
  1. In the Create account window
    • Under Country / region
      • Select United States
    • Under Birthdate
      • Select a birthdate
    • Select Next
  1. In the Verify email window
    • Note you have to enter a code
    • Switch to your email to get the CODE
    • Enter the CODE
    • Select Next
  1. On the Create account page
    • Select Next
  1. On the Create account page
    • Select Whatever YOUR interface asks you to
    • When done you will be switched back to the Microsoft 365 developer page
  1. On the Developer Page
    • In the top right corner
      • Select the account icon
      • Select Add your name
  1. Under Edit name
    • Enter your
      • First name
      • Last name
      • Captcha
    • Select Save
  1. On your ControlCenter
    • Using your Google Chrome Browser
      • Open a New Incognito session
  1. In your Google Chrome browser
    • Enter https://developer.microsoft.com/en-us/office/dev-program URL
  1. In the Microsoft 365 Developer page
    • In the top right corner
      • Select Sign in
  1. In the Microsoft Sign in page
    • Enter  custom email address
    • Select Next
  1. In the Enter password window
    • Enter your custom password
      • select Sign in
    • In the Stay signed in? page
      • Select Yes
  1. Join Office 365 Developer program today page
    • Select Join now >
  1. On the Microsoft 365 Developer Program Signup page
    • Under  Country/Region 
      • Select United States
    • Under  Company*
      • Enter CorpXXX.euc-livefire.com
        • Where XXX is your assigned Corp domain identifier
    • select the two checkboxes for terms and conditions and information
    • Select NEXT
  1. On the What is your primary focus as a developer? * (Choose only one)
    • Next to Personal projects
      • Select the radio button
    • Select Next
  1. In the What areas of Microsoft 365 development are you interested in? page
    • Select several checkboxes
    • Select Save
  1. Set up your Microsoft 365 E5 sandbox page
    • Accept the default
      • note you will have 90 days left
    • Select Next
  1. In the Set up your Microsoft 365 E5 Instant Sandbox page
    • Enter the following information
      • Under Country/region
        • select North America(United States - CA)
      • Under Admin username*
        • enter CloudadminXX
          • XX being your POD ID
      • Enter and confirm your Password
        • Note! This password has to be at lease 15 characters
          • possibly use VMware1!VMware1!
    • Select Continue
  1. In the Add phone number for security page
    • Enter YOUR Country code
    • Enter YOUR phone number
    • Select Send Code
  1. In the Image security page
    • Follow the instructions in your version
    • Select VERIFY
  1. In the Add phone number for security window
    • Under Enter the code
      • Enter the number you received via text message from Microsoft
    • Select Set up
  • Very important
    • Take a note of your Domain name
    • Take a note of your Administrator account
  • Save this information to your Lab Notes document
  1. In the Microsoft 365 Developer Program window
    • Note you have a 90 day developer trial of Microsoft 365
    • Select Go to subscription
  1. On Microsoft sign-in page
    • Note the full fqdn of your admin account
    • Under Enter password
      • type your password
    • Select Sign in

 

  1. On Microsoft sign-in page
    • Select Skip for now ( 14 days until this is required)
  1. On Microsoft sign-in page
    • Select Yes
  1. In the Office page
    • This is the final step in the process of setting up your developer account
    • Take a few moments to validate all your account information and ensure you have saved this properly

Part 2: Preparing the Microsoft 365 environment to use a dedicated domain name

In this Part , we look at a requirement for Federation that being a dedicated namespace. Microsoft 365 relies on external providers to fulfill this requirement.

We will be using AWS Route 53. Each of you must ensure you know your assigned Domain name prior to starting this Part

Part 2: Preparing the Microsoft 365 environment to use a dedicated domain name
  1. In the top left-hand corner off Microsoft 365
    • Select the Select the 9 dotted square
    • Once the Apps pop out expands
      • Select Admin
  1. In the Help us protect your account page
    • Select Skip for now (14 days until this is required)
    • Select Next
  1. In the Microsoft 365 admin center window
    • Select Setup
  1. In the Microsoft 365 admin center window
    • Under Setup
      • Select Guided setup
  1. In the Microsoft 365 admin center window
    • In the Install Office area
      • Scroll down to the bottom of the page
      • Select Continue

NOTE: Before moving onto the next section, ensure that you are 100% clear what YOUR registered Domain will be.

In the course lab we will use a Domain naming convention based on the location we are delivering at.

We will use the convention corpXXX.euc-livefire.com

Where XXX is your assigned Domain Identifier

On the Microsoft 365 admin center  ensure the Connect a domain you already own radio button is selected and below type your registered Domain name (this example in the screenshot is only for demo purposes) select Next

  1. In the Microsoft 365 admin center window
    • In the Add domain area
      • Under Yes, add this domain now
        • enter corpXXX.euc-livefire.com
          • Where XXX is your assigned Domain identifier
      • At the bottom of the page
        • Select Use this domain
  1. In the Microsoft 365 admin center window
    • In the How do you want to verify your domain?
      • Ensure the radio button next to Add a TXT record to the domain's DNS records is enabled (default)
    • Select Continue
  1. In the Microsoft 365 admin center window
    • In the How do you want to verify your domain?
      • Below TXT value
        • Copy the MS= ms ......
          • In the following steps, we will have this value entered into your assigned Zone database in AWS Route 53 using vRealize automation

Do step 9: VRA automation on a separate browser profile.

If you were doing your Azure registration on the Site 1 profile then might be helpful to do the VRA on the Site 2 Profile and have both profiles open side by side.

 

  1. On your Controlcenter desktop,
    • On your Site 2 browser
      • Open a new Tab
    • In the Address bar 
      • enter https://vra.lab.livefire.dev/
    • Select GO TO LOGIN PAGE
  1. In the Workspace ONE Login
    • Under Select your domain
      • Ensure livefire.lab selected
    • select Next
  1. In the Workspace ONE login
    • Under username
      • Enter your assigned dwuser0XX account
        • XX will be your assigned Student Login ID
    • Under password
      • Enter your assigned password
    • Select Sign in
  1. In the vRealize Automation - Cloud Services Console
    • Under My Services
      • Select Service Broker
  1. In the My Resource Usage window
    • Under update TXT  Records
      • Select REQUEST
  1. In the New Request page
    • Update the following next to:
      • Sub Hosted Zone Prefix* enter your domain
      • TXT record value* Paste your TXT value (from step 7)
    • Select SUBMIT
  1. On your Microsoft 365 admin center page
    • When the vrealize automation is complete
    • Select Verify
  1. In the Microsoft 365 admin center window
    • In the Add users and assign licenses page
      • At the bottom of the page
        • Select Do this later
  1. In the Microsoft 365 admin center window
    • In the  Connect domain section
      • At the bottom of the page
        • Select Continue
  1. In the Microsoft 365 admin center window
    • In the  Connect domain section
      • If the MX record test failed do the following:-
        • Under Points to address or value and in line with Expected
          • Copy the output
  1. Switch back to your Service Broker session
    • Select the Catalog tab
  1. In the Catalog area
    • Under Update MX Records
      • select REQUEST
  1. In the Service Broker
    • New Request
      • Update MX Records page
      • Next to:
        • Sub Hosted Zone Prefix* enter corpXXX
          • Where XXX is your assigned Domain identifier
        • MX record value* paste your MX record
        • Manually add 0 in front of corp
    • Select SUBMIT
  1. On the Connect domain page
    • At the bottom
      • Select Continue
  1. In the Microsoft 365 admin center window
    • In the Setup is Complete  page
      • Offer a 5 star rating
    • Select Submit
  1. In the Microsoft 365 admin center window
    • In the Thank you for your feedback  page
      • At the bottom of the page
        • Select Go to admin center
  1. In the Microsoft 365 admin center window
    • In the left-hand pane Inventory
      • Select ... Show all
  1. In the Microsoft 365 admin center window
    • In the left-hand pane Inventory
      • Expand Settings
  1. In the Microsoft 365 admin center window
    • In the left-hand pane Inventory
      • Under Settings
        • Select Domains
  1. In the Domains area
    • Under Domain name
      • Next to your unique *.onmicrosoft.com domain
        • select the checkbox
      • Under Domains , in the Task area
        • Select Set as default
  1. In the Set this domain as default? window
    • Select Set as default

 

  1. In the Domains page
    • Validate your default configuration

Part 3: Federating Office 365 with Workspace ONE Access.

In Part 3 of this lab session we will now federate our Office 365 Tenant with a Workspace ONE Access SAAS tenant.

Part 3: Section 1 - Setting the authentication status of Azure from Managed to Federated.
  1. On your ControlCenter server
    • Open a new browser tab
    • Enter your Workspace ONE Access tenant url
    • Log in with your Sysadmin credentials
      • To the right of the Intelligent Hub Console console
        • Select and right-click TA
        • Select Workspace ONE Access Console

 

  1. In the Workspace ONE Access Console
    • Select the Catalog tab dropdown
      • In the dropdown
        • Select Web Apps
  1. In the Workspace ONE Access console
    • In the right-hand side of the Web Apps area
      • Select SETTINGS
  1. In the Settings window
    • Select SAML Metadata
  1. In the SAML Metadata area
    • In the right-pane, scroll down until you find Signing Certificate
    • Below Signing Certificate
      • Select DOWNLOAD
      • In the bottom left-corner of your browser
        • When prompted to keep a potentially harmful file
          • Select Keep
  1. On your ControlCenter server
    • On the Desktop
      • Select the START button
        • From the Start Menu
          • select the Windows  Powershell ISE Shortcut
  1. In the Azure Powershell ISE module
    Enter the following:-
    • Install-Module -Name MSOnline
      • with your keyboard
        • select ENTER
      • When prompted : to install NUGET
        • select Yes
      • When prompted : Untrusted repository
        • Select Yes to All
  1. In the Azure Powershell ISE module
    • Enter the following:-
      • Connect-MsolService
        • with your keyboard
          • select ENTER
  1. In the Sign-in to your account window
    • Under Sign in
      • enter your Cloud Admin account
    • Select Next
  1. In the Sign in to your account window
    • Under Enter password
      • Enter your Cloud Admin Password
    • Select Sign in
  1. In the Sign in to your account window
    • Select Skip for now (14 days until this is required)
  1. In the Azure Powershell  ISE module
    • Enter the following:-
      • Get-MsolDomain
        • with your keyboard
          • select ENTER
  • Note that both your Domains are Authentication status are Managed
  • When we are done
    • our aim is to change the status of your custom domain to Federated
  • We will now proceed step-by-step to achieve this goal
  1. On your ControlCenter server
    • Copy and Paste the below commands into Notepad++
      • Where you have YOURACCESSHOST
        • Replace with your Workspace ONE Access Tenant Identifier
      • Where you have CorpXXX
        • Replace with your POD Identifier
      • $Cert = We will look at this later
        1. $Metadata = 'https://YOURACCESSHOST.vidmpreview.com/SAAS/auth/wsfed/services/mex'
        2. $Brand = 'CorpXXX'
        3. $Domain = 'corpXXX.euc-livefire.com'
        4. $ActiveSO = 'https://YOURACCESSHOST.vidmpreview.com/SAAS/auth/wsfed/active/logon'
        5. $PLUri = 'https://YOURACCESSHOST.vidmpreview.com/SAAS/API/1.0/POST/sso'
        6. $IssuerUri = 'YOURACCESSHOST'   (without vidmpreview.com behind)
        7. $Cert =

 

  1. On your ControlCenter server
    • Switch back to your Azure Powershell  ISE module
      • Copy your first variable from Notepad++
        • Paste into Powershell
          1. $Metadata = 'https://YOUR VERSION.vidmpreview.com/SAAS/auth/wsfed/services/mex'
            • With your Keyboard
              • select Enter`
  1. On your ControlCenter server
    • Copy your second variable from Notepad++
      • Paste into Powershell
        1. $Brand = 'corpXXX'
          • Where XXX is your assigned Domain Identifier
            • With your Keyboard
              • select Enter
  1. On your ControlCenter server
    • Copy your third variable from Notepad++
      • Paste into Powershell
        1. $Domain = 'corpXXX.euc-livefire.com'
          • Where XXX is your assigned domain identifier
            • With your Keyboard
              • select Enter
  1. On your ControlCenter server
    • Copy your Fourth variable from Notepad++
      • Paste into Powershell
        1. $ActiveSO = 'https://YOUR VERSION.vidmpreview.com/SAAS/auth/wsfed/active/logon'
          • With your Keyboard
            • select Enter
  1. On your ControlCenter server
    • Copy your Fifth variable from Notepad++
      • Paste into Powershell
        1. $PLUri = 'https://YOUR VERSION.vidmpreview.com/SAAS/API/1.0/POST/sso'
          • With your Keyboard
            • select Enter
  1. On your ControlCenter server
    • Copy your sixth variable from Notepad++
      • Paste into Powershell
        1. $IssuerUri = 'YOUR VERSION'
          • With your Keyboard
            • select Enter`
  1. On  your ControlCenter server
    • Open your DOWNLOADS folder
      • Select the signingCertificate.cer
        • right-click and select Edit with Notepad++

 

  1. In Notepad++
    • Remove the
      • -----BEGIN CERTIFICATE-----
        • and  
      • -----END CERTIFICATE-----
    • lines from the certificate.
  1. In Notepad++
    • We will now remove all carriage returns the document
      • Select ALL of the certificate portion of the file
      • Select ctrl + F
        • In the Find window
          • Select  the Replace tab
            • Next to Find what:
              • clear all entries (if necessary)
              • enter \n
            • Next to Replace with:
              • leave blank
        • At the bottom of the Replace window.
          • In the Search Mode area
            • Next to Extended.
              • select the radio button  
        • Select Replace All.  
  1. In Notepad++
    • Switch back to your sample scripts
      • Copy the following:    $Cert =
        • Switch back to the tab with your Signing Certificate
          • On your ControlCenter server In Notepad++
            • In front of your certificate with no carriage returns
              • Insert and Paste $Cert =
              • Insert brackets at the beginning and end of your certificate
            • In Notepad++
              • Select All (Ctrl + A ) and copy (Ctrl + C )
  1. On your ControlCenter server
    • Switch back your Powershell
      • Paste into Powershell
        • $Cert = 'XX' signing cert
          • Where XX is your cert string version
      • With your Keyboard
        • select Enter`
  1. In the Azure Powershell  ISE module window
    • Using the below code

Set-MsolDomainAuthentication –DomainName $Domain -Authentication Federated -FederationBrandName $brand -PassiveLogOnUri $PLUri -SigningCertificate $Cert -IssuerUri $IssuerUri -ActiveLogOnUri $ActiveSO -LogOffUri $PLUri -MetadataExchangeUri $metadata

  1. In the Azure Powershell  ISE module
    • Enter the following:-
      • Get-MsolDomain
  1. In the Azure Powershell  ISE module
    • Notice that your Custom Domain now Verified as Federated
Part 3: Section 2 - Setting up Workspace ONE Access for Azure Federation
  1. In your Workspace ONE Access SAAS Admin Console
    • Select the Catalog Tab in the Admin Console,
    • Under Catalog
      • Select NEW
  1. In the New SaaS Application window
    1. In the Definition area
      • Under Search
        • Enter Office
      • From the dropdown
        • Select Office365 with Provisioning
      • In the bottom right corner
        • Select NEXT
  1. In the New SaaS Application window
    1. Configuration area
      • Scroll down until you find Application Parameters
        • Under Name , you have two parameters
          • tenant
          • issuer
            • In line with tenant, under Value
              • enter your Azure domain name .
                • e.g. CorpXXX.euc-livefire.com
                  • where XXX is your assigned domain identifier
            • In line with issuer, under Value
              • enter your Workspace ONE Access name without vidmpreview.com
                • e.g. If your tenant name is aw-livefirernpod31.vidmpreview.com
                  • then your you will enter aw-livefirernpod31
            • Expand Advanced Properties
  1. In the New SaaS Application window
    • In the Configuration area
      • Scroll down to Custom Attribute Mapping
        • Under Name
          • In the with UPN row
            • Under the Value column
              • validate that the configuration is:-
                • ${user.userPrincipalName}
          • In the ImmutableID row
            • Under the Value column
              • Replace ${user.objectGUID}
                • with ${user.ExternalId}
      • Select NEXT
  1. In the New Saas Application window,
    • In the Access Policies section
      • Select NEXT
  1. In the New Saas Application window,
    • In the Summary section
      • Select SAVE & ASSIGN
  1. In the Assign window
    • Under Users / Groups
    • Under Deployment type
      • From the dropdowns
        • Ensure both Sales and Marketing are set to
          • Automatic
    • In the bottom right corner
      • Select SAVE
  1. In your Workspace ONE Access Console
    • Select the Identity & Access Management console
      • You will notice it takes you to the Directories area by default
  1. Under Directories
    • Under Directory Name
      • Select euc-livefire.com
  1. In the euc-livefire.com Directory
    • In the Directory Sync and Authentication area
      • Next to External ID*
        • Replace objectGUID
          • with mS-DS-ConsistencyGuid
            • Note this is case-sensitive
  1. In the euc-livefire.com Directory
    • In the Bind User Details area
      • Next to Bind User Password*
        • enter VMware1!
    • Select Save
  1. Under Directories
    • Under Directory Name
      • Select euc-livefire.com
  1. Under Directories
    • Under Sync
      • Select Sync Settings
  1. In the Sync settings window
    • Select Mapped Attributes
  1. In the Mapped Attributes window
    • Scroll down until you find sourceAnchor
    • To the right of sourceAnchor
      • Edit the existing value objectGUID
        • From the dropdown
          • select Enter Custom Input
        • In the Enter Custom Input area
          • enter  mS-DS-ConsistencyGuid
    • At the bottom of the Mapped Attributes area
      • select Save

Part 4. Configuring domain trust

We will now create a suffix to match our Azure Domain name

Part 4. Configuring domain trust
  1. On your ControlCenter server
    • In the bottom left corner
      • Select the Start button
    • In the Start Menu
      • Select Windows Administrative Tools
  1. In the Administration Tools menu
    • Select the Active Directory Domains and Trusts shortcut
  1. In  Active Directory Domains and Trusts
    • In the Inventory
      • Select and right click
        • Active Directory Domains and Trusts
          • Select Properties
  1. In the Active Directory Domains and Trusts window
    • Under Alternative UPN Suffixes
      • Enter the FQDN of your Azure Domain
        • e.g. CorpXXX.euc-livefire.com
          • where XXX is your assigned Domain Identifier
      • Select Add
  1. In the Administrative tools folder
    • Select Active Directory Users and Computers shortcut
      • Select open
  1. In the Active Directory Users and Computers Console
    • Expand the euc-livefire.com hierarchy
      • Select Corp OU and expand
        • Select Sales
  1. In the Active Directory Users and Computers Console
    • Select the Mark Debio user object
      • Select Properties
  1. In the Mark Debio properties
    • To the right and In line with Mark
      • From the Dropdown
        • Select your Alternate suffix eg. CorpXXX.euc-livefire.com
          • where XXX is your assigned Domain ID
    • To close Mark Debio Properties
      • Select OK
  1. In the Active Directory Users and Computers Console
    • Repeat the above mention steps for at least these accounts :
      • In the Sales OU :- Jill Vernio
      • In the Marketing OU: - Fernando Dusello
      • In the Marketing OU: - Tom Marios
      • In IT Support OU: - Kim Markez
  1. On your ControlCenter server
    • Switch to your Chrome Browser
    • Select your Workspace ONE Access session
      • If necessary login again as Sysadmin
    • In the Identity & Access Management area
      • Under Directories
        • Under Directory Name
          • Select euc-livefire.com
  1. In the EUC-LIvefire.com Directory
    • Next to Sync
      • Select the Dropdown
        • Select Sync without Safeguards

Part 5: Using Azure AD Connect for user provision to Azure AD

In this part we are going to install Azure AD Connect tool to provision users to azure from on premise Active Directory.

Please note: It is best practice to use Azure AD Connect tool but not a requirement. You can also provision users to Azure from Workspace ONE Access using Office365 with Provision application with Setup Provisioning ENABLED.

Part 5: Using Azure AD Connect for user provisioning to Azure
  1. On your ControlCenter server
    • Open the Software shortcut
      • Navigate to the Applications > Azurefiles >ADConnect folder.
    • Double- click the AzureADConnect.msi
      • On the Open File - Security Warning window
        • Select Run
  1. On the Welcome to Azure AD Connect window
    • Next to I agree to the license terms and privacy notice
      • Enable the check box
      • Select Continue
  1. In the Express Settings window
    • Select Use express settings
  1. On the Connect to Azure AD window,
    • Under USERNAME
      • Enter your documented Azure Cloud Admin account
    • Under PASSWORD
      • Enter your documented Azure Cloud Admin password
    • Select Next
  1. On the Connect to AD DS window,
    • Under USERNAME
      • Enter EUC-Livefire\administrator
    • Under PASSWORD
      • Enter VMware1!
    • Select Next
  1. On the Azure AD sign-in configuration page
    • Validate that your custom Azure Domain has been Verified
    • Next to Continue without matching all UPN suffixes to verified domains
      • Select the Check box
    • Select Next
  1. On the "Ready to configure" window
    • Next to Start the synchronization process when configuration completes
      • Enable the check box
    • Select Install.
      • Getting to the next step could take a few minutes.
  1. On the Configuration complete window
    • Select Exit

Part 6: In this part, we will now start testing the federation to see and ensure it it working properly

  1. In the first section of Part 6 we go into the Azure Admin console and we configure licensing
  2. In the second section of Part 6 we will use a test account to Test if this session works

 

Part 6: section 1: Configuring Microsoft 365 licensing
  1. On your ControlCenter server
    1. Using the following URL
      • https://admin.microsoft.com/Adminportal/Home?source=applauncher#/homepage
    2. Login back to your Microsoft 365 Tenant
      • With cloudadmin username
      • With your CloudAdmin password
  1. In the Microsoft 365 Admin center
    • In the left-hand pane under Home,
      • Select Users
        • Select Active users.
  1. In the Active Users area
    • Notice that you have Licensed and Unlicensed users
      • It appears that in addition to us syncing in our account Microsoft creates dummy accounts for use
      • The dummy user accounts have already been licensed and we only can have up to 25 licensed users
      • Ensure you select only DUMMY accounts with Microsoft 365 E5 Developer licensing
      • At the top of browser select Delete user
      • DO NOT Delete your Cloudadmin account
  1. In the Active Users area
    • Select the radio buttons next to
      • Fernando Dusello
      • Jill Verneo
      • Kevin Ikin
      • Kim Markez
      • Mark Debio
    • From the top menu options
      • At the top of the Active Users area, next to Refresh,
      • select Manage product licenses
  1. In the Manage Product licenses window
    • Next to Replace ,
      • Select the radio button
    • Next to Microsoft E5 Developer (without Windows and Audio Conferencing)
      • Select the Checkbox
      • Select Save Changes.
Part 6: section 2: Testing to see if the Federation works
  1. On your Control Center server
    • On your Chrome browser
      • Open up an Incognito session
      • In the address bar enter your Workspace ONE Access tenant url
  1. On the login window
    • Under select Your Domain
      • from the dropdown select , euc-livefire.com
    • Select Next
  1. On the login window
    • Under username
      • enter Jill
    • Under  password
      • enter VMware1!
    • select Sign in
  1. In the web Intelligent Hub
    • Select Apps
  1. In the web Intelligent Hub
    • Under Apps
      • Select Office 365 with Provisioning
  1. In the Help us protect your account window
    • Select , Skip for now (xx days until this is required)
      • xx represents whatever you see on your screen)
    • Select Next
  1. On the Stay signed in? page
    • Select Yes
  1. In the office.com window
    • Notice you have access to your Microsoft 365 applications
    • Using deep links, we are able to publish these applications individually to Workspace ONE Access

Acknowledgements

A BIG and wholehearted thank you to Sascha Warno  for his support and guidance.

Sascha is a Staff End User Computing Architect at VMware

About the Author

About the content author Reinhart Nel

https://www.livefire.solutions/meet-the-team/reinhartnel/

For any questions please email Reinhart at [email protected]

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.