Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:m365_graphapi_calendars_read [2025/06/16 17:46]
admin [Configuration of Microsoft 365 for Calendars access]
en:m365_graphapi_calendars_read [2025/06/16 18:03] (current)
admin [Next Steps]
Line 28: Line 28:
  
 ===== 2. Registering the App ===== ===== 2. Registering the App =====
-  - **Name**: Enter `zebrix signage calendars connector`+  - **Name**: Enter `zebrix signage calendars connector` ​(you are free to choose the name you want)
   - **Supported account types**: Choose **"​Accounts in this organizational directory only"​** (default).   - **Supported account types**: Choose **"​Accounts in this organizational directory only"​** (default).
   - Leave the **Redirect URI** empty.   - Leave the **Redirect URI** empty.
Line 35: Line 35:
 {{:​en:​m365_calendars_app_registration_02.png?​nolink&​1000|}} {{:​en:​m365_calendars_app_registration_02.png?​nolink&​1000|}}
  
-===== 3. Creating ​a Client Secret ===== +===== 3. Save details and create ​a Client Secret ===== 
-  - In the app overview, select **"​Certificates & secrets"​**. +  - Save the details that need to be provided to zebrix'​s technical team: 
-  Under **Client secrets**, click **"​New ​client ​secret"​**. +    - **Application (client) ID** 
-  Add a description,​ for example `zebrix connector secret`. +    **Directory ​(tenantID** 
-  - Set an expiration ​(recommended:​ 6 or 12 months). +  - Click on **Add a certificate or secret**.
-  - Click **"Add"** and copy the generated value immediately**You will not be able to retrieve it again.**+
  
 {{:​en:​m365_calendars_app_registration_03.png?​nolink&​1000|}} {{:​en:​m365_calendars_app_registration_03.png?​nolink&​1000|}}
 +
 +  - Add a description,​ for example `zebrix connector secret`.
 +  - Set an appropriate expiration (24 months is recommended).
 +
 +<WRAP center round important 60%>
 +When the secret will expire, zebrix will not have access to your calendars anymore and display their details on screen. You'll have to create a new secret and provide it to zebrix. We invite you to create an event in your personal calendar at the end of the validity period of the secret.
 +</​WRAP>​
  
 {{:​en:​m365_calendars_app_registration_04.png?​nolink&​1000|}} {{:​en:​m365_calendars_app_registration_04.png?​nolink&​1000|}}
 +
 +  - Click **"​Add"​** and copy the generated value and save it immediately. **You will not be able to retrieve it again.**
  
 {{:​en:​m365_calendars_app_registration_05.png?​nolink&​1000|}} {{:​en:​m365_calendars_app_registration_05.png?​nolink&​1000|}}
Line 62: Line 70:
 {{:​en:​m365_calendars_app_registration_07.png?​nolink&​1000|}} {{:​en:​m365_calendars_app_registration_07.png?​nolink&​1000|}}
  
-===== 5. Summary ​===== +===== 5. Provide details to zebrix'​s technical team and get your UUID ===== 
-You now have: + 
-  - Registered an application named **"zebrix ​signage calendars connector"​**. +  - Please provide to zebrix's technical team the following details: 
-  - Generated ​client secret ​to authenticate your backend app+    ​Application (client) ID 
-  - Granted **Calendars.Read** application-level permission ​to access calendars ​in your organization.+    ​Directory (tenant) ID 
 +    * Secret value 
 + 
 +  - We recommend using secured channel ​to provide these details to our team
 +  - A UUID will be returned to you by the zebrix'​s technical teamThese UUID has to remain secret as it will give full access ​to all your resources and users calendars ​details. 
 + 
 +===== 6. Configure the widget ===== 
 + 
 +  - Go to https://​widgets.zebrix.net 
 +  - Choose the Microsoft 365 calendar widget that suits your needs 
 +  - Copy / Paste your UUID in the field 
 +  - Set the resource or user UPN (usually, the email address) 
 +  - Customize other options of the widgets 
 +  - Copy the generated URL and paster it in a web zone in the page editor. 
  
-===== Next Steps ===== 
-Use the **Application (client) ID**, **Directory (tenant) ID**, and **Client secret** in your integration code to authenticate using the OAuth 2.0 client credentials flow.