# Connect with Microsoft 365 Scope

> The Microsoft 365 activities establish an authenticated connection to a Microsoft 365 application through the [Microsoft 365 Scope](https://docs.uipath.com/activities/other/latest/productivity/microsoft-office-365-scope) activity.

The Microsoft 365 activities establish an authenticated connection to a Microsoft 365 application through the [Microsoft 365 Scope](https://docs.uipath.com/activities/other/latest/productivity/microsoft-office-365-scope) activity.

Inside the scope activity, you can use both classic activities, as well as Connection activities, which use Integration Service connections. When using Connection activities inside **Microsoft 365 Scope**, they inherit the authentication from the scope. In addition, you can also check [How to use Microsoft 365 activities without Integration Service connections](https://docs.uipath.com/activities/other/latest/productivity/how-to-use-microsoft-activities-integration-service).

There are multiple authentication types available in **Microsoft 365 Scope**:

* [Interactive token](https://docs.uipath.com/activities/other/latest/productivity/interactive-token#interactive-token)
* [Integrated Windows Authentication (IWA)](https://docs.uipath.com/activities/other/latest/productivity/integrated-windows-authentication-iwa#integrated-windows-authentication-(iwa))
* [Username and Password](https://docs.uipath.com/activities/other/latest/productivity/username-and-password#username-and-password)
* [Application ID and Secret](https://docs.uipath.com/activities/other/latest/productivity/application-id-and-secret#application-id-and-secret)
* [Application ID and Certificate](https://docs.uipath.com/activities/other/latest/productivity/application-id-and-certificate#application-id-and-certificate)

 <colgroup>
  <col/>
  <col/>
  <col/>
  <col/>
  <col/>
 </colgroup>
 
  
    Microsoft Authentication flow 
    Microsoft 365 Scope - Authentication type 
    Robot type - Attended 
    Robot type - Unattended 
    API permission type 
  
 
 
  
     OAuth 2.0 authorization code flow  
     Interactive Token  - public app  
    ✅ 
    &nbsp; 
     Delegated permissions  
  
  
     Interactive Token  - BYOA 
    ✅ 
    &nbsp; 
    Delegated permissions 
  
  
     Integrated Windows authentication (IWA)  
     Integrated Windows Authentication  
    &nbsp; 
    ✅ 
     Delegated permissions  
  
  
     Username and password  
     Username and password  
    &nbsp; 
    ✅ 
     Delegated permissions  
  
  
     OAuth 2.0 client credentials flow  
     Application ID and secret  
    ✅ 
    ✅ 
     Application permissions  
  
  
     Application ID and certificate  
    ✅ 
    ✅ 
     Application permissions  
  
 

Integration Service keeps the connection token alive by refreshing the token. After a certain period of time, you must manually refresh the connection by re-authentication.