You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: copilot/employee-self-service/servicenow-hrsd-itsm.md
+85-3Lines changed: 85 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ Refer to the ESS Agent deployment guide for installation of the agent and subscr
73
73
|**Application Developer** (*minimum privileged role*) | User who can register an application | Create an App registration - *if using Microsoft Entra OAuth for ServiceNow connector*| Microsoft 365 Admin Center |
74
74
|**Environment Maker**| User who can customize ESS Agent | Configure & Customize ESS Agent | Microsoft Copilot Studio |
75
75
76
-
###ServiceNow configuration
76
+
## ServiceNow configuration
77
77
78
78
This section outlines the tasks required to be configured in ServiceNow by an administrator. ServiceNow integration supports three types of authentications as follows:
79
79
@@ -88,7 +88,86 @@ This section outlines the tasks required to be configured in ServiceNow by an ad
88
88
> [!TIP]
89
89
> Without elevating access, the new security objects can't be created. If **New** button in the top right of configuration pane is missing, then the role isn't elevated to "`security_admin`”.
90
90
91
-
#### Option 1: Using OAuth2 authentication - Create an OAuth Application Registry
91
+
### Basic authentication
92
+
93
+
This method of authentication involves a ServiceNow username and password to authenticate API requests. This method is simple to use and is primarily suggested for testing purposes, as it offers lower security compared to other authentication methods.
94
+
95
+
### Microsoft EntraID OAuth using Certificate
96
+
97
+
This authentication uses app tokens, allowing a registered Entra ID application to access ServiceNow with a token specifying the ServiceNow Entra ID app as the resource.
98
+
99
+
#### Task 1: Register an application in Microsoft Entra ID for OIDC integration with ServiceNow
100
+
101
+
[Learn how to register an app in Microsoft Entra ID.](/entra/identity-platform/quickstart-register-app)
102
+
103
+
1. Sign into the Microsoft Entra admin portal as a global administrator or cloud app administrator.
104
+
1. Go to **Applications** then **App registrations**.
105
+
1. Select **New registration.**
106
+
1. In the new registration form, fill in the following fields:
107
+
1.**Name:** Any name that represents the purpose of app registratio
108
+
1.**Redirect URL:** Not needed
109
+
1. Choose **Register** to complete the creation of the new app registration.
110
+
1. Select **Token configuration** then **Add optional claim** for adding claims setting.
111
+
1. Select **Token type** as **Access** and choose the following claims:
112
+
1.*aud* - for audience validation
113
+
1.*email* - addressable email for user
114
+
1.*upn* - an identifier for the user
115
+
1. Select **Add** to complete adding the claims.
116
+
1. If this is the first time OpenId Connect being setup using claims like email, upn, there’ll be a confirmation to turn on the Microsoft Graph permissions, please check the box and select **Add**.
117
+
1. This flow completes the Microsoft Entra piece of configuration.
118
+
119
+
#### Task 2: Register OIDC provider in ServiceNow
120
+
121
+
1. Login to the ServiceNow instance that needs to be integrated with ESS Agent.
122
+
1. Elevate access permissions using **Elevate role**. Refer to the section **Error! Reference source not found.** – only the first part and not the tasks.
123
+
1. Click **All** in the top navigation bar.
124
+
1. Search for “OAuth” in the search box within dropdown navigation menu.
125
+
1. Select **System OAuth à Application Registry** from the search results (if you don’t see this option, then you don’t have sufficient privileges).
126
+
1. Select **New** in the configuration section pane.
127
+
1. Select **Configure an OIDC provider to verify ID tokens**.
128
+
1. Fill in the following information for the new application registry:
129
+
130
+
|Configuration |Description |
131
+
|--------------|------------|
132
+
|Name |a meaningful name to identify that this OIDC provider was created for ESS Agent |
133
+
|Client ID |The client ID of Entra Application created in Task 1 above |
134
+
|Client secret |This value will not be used; can be any value |
135
+
|OAuth OIDC provider configuration |Add a new OIDC provider configuration by selecting the search icon and choosing **New** in the search popup. Fill in the fields as follows:</br> **OIDC Provider:** A name that represents the Microsoft Entra tenant from task 1 above.</br> **OIDC Metadata URL:**`login.microsoftonline.com/<tenant ID>/.well-known/openid-configuration`</br> Replace < tenant ID > with the Entra tenant ID from task 1 above.</br> **OIDC Configuration Cache Life Span:** 120</br> **Application:** Global</br> **User Claim:** oid</br> **User Field:** User ID</br> **Enable JTI claim verification:** disabled</br> Select **Submit** and update the OIDC Entity form. |
136
+
137
+
#### Task 3: Register an Application in Microsoft Entra ID for connector usage
138
+
139
+
This is the application which plays the role of a user with elevated permissions in the ServiceNow instance.
140
+
141
+
1. Login to Entra administration portal as global administrator (or) cloud app administrator.
142
+
1. Go to **Applications** > **App registrations**.
143
+
1. Select **New registration**.
144
+
1. In the new registration form, fill in the following fields:.
145
+
1.**Name:** any name that represents the purpose of app registration.
146
+
2.**Redirect URI:** Not needed.
147
+
1. Click **Register** to complete the creation of new app registration.
148
+
1. Select **Certificates & secrets** then upload the .cer file of the certificate. In case of SNI certificate, just add trustedCertificateSubjects in the manifest of the application with the relevant authorityId and subjectName.
149
+
150
+
#### Task 4: Create a System User in ServiceNow
151
+
152
+
This is the Application created in the above task 3 which is a user in ServiceNow instance.
153
+
154
+
Go to **User Administration** > **Users** to create a new user.
155
+
156
+
**User ID:** The object ID of the service principal of Application created in Task 3 above.
157
+
158
+
Check **Web service access only**.
159
+
160
+
### Microsoft Entra ID OAuth User Login
161
+
162
+
This is user-token based authentication where the end user can sign into Entra ID 1st party application i.e. ServiceNow connector 1st party app and get an access token with scope for the ServiceNow representative Entra ID app.
163
+
164
+
Perform Task 1 & Task 2 from the previous section Microsoft Entra ID OAuth using Certificate.
165
+
166
+
In the Task 1 – add the 1st party application i.e., ServiceNow connector to the permission scope – Client ID = c26b24aa-7874-4e06-ad55-7d06b1f79b63.
167
+
168
+
In the Task 2 – update the user claim to upn or any other custom claim property from the token in ServiceNow. The user field should match the ServiceNow system user table field containing the upn or user ID.
169
+
170
+
### Using OAuth2 authentication - Create an OAuth Application Registry
92
171
93
172
1. Log in to the ServiceNow instance that needs to be integrated with ESS Agent.
94
173
2. Elevate access permissions using **Elevate role**.
@@ -104,7 +183,7 @@ This section outlines the tasks required to be configured in ServiceNow by an ad
104
183
|**Name**| a meaningful name to identify that this application registry is created for ESS Agent |
105
184
|**Client ID**| autogenerated code <br><divclass="alert">**Note**</br>This value is used in Microsoft 365 Copilot Connector configuration, if no Advanced Scripting is used. |
106
185
|**Client Secret**| leave it blank to automatically generate a string <br><divclass="alert">**Note**</br>This value is used in Microsoft 365 Copilot Connector configuration, if no Advanced Scripting is used. |
107
-
|**Redirect URL**| a required callback URL that the authorization server redirects to </br>For Microsoft 365 Enterprise:</br>`https://gcs.office.com/v1.0/admin/oauth/callback`</br>For Microsoft 365 Government:</br>`https://gcsgcc.office.com/v1.0/admin/oauth/callback`|
186
+
|**Redirect URL**| a required callback URL that the authorization server redirects to </br>For Microsoft 365 Enterprise:</br>`https://gcs.office.com/v1.0/admin/oauth/callback`</br>For Microsoft 365 Government:</br>`https://gcsgcc.office.com/v1.0/admin/oauth/callback` Refer to the note after the table for more information.|
108
187
|**Logo URL**| A URL that contains the image for the application logo |
109
188
|**Active**| Set to active |
110
189
|**Refresh token lifespan**| The number of seconds that a refresh token is valid. </br>By default, refresh tokens expire in 100 days (8,640,000 seconds). Recommended value is 31,536,000 (one year) |
@@ -113,6 +192,9 @@ This section outlines the tasks required to be configured in ServiceNow by an ad
113
192
|**Accessible from**| All application scopes |
114
193
|**Client Type**| Integration as a Service |
115
194
195
+
>[!NOTE]
196
+
>[Please use the actual callback URL from the sign-in popup window during connection configuration by following the steps below, when the URL redirection fails with the error **Invalid redirect_uri**:</br> Copy/paste the complete URL from the authorization popup window</br> Extract redirect_uri parameter.</br> Example: `redirect_uri=https%3a%2f%2ftip1-shared.consent.azure-apim.net%2fredirect`</br> After decoding the URL – replacing %3a with : and %2f with /</br> Update the Redirect URL field.]
197
+
116
198
9. Select **Submit** or **Update** button to save the changes.
Copy file name to clipboardExpand all lines: copilot/manage-public-web-access.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,9 @@ ms.date: 06/27/2025
21
21
22
22
Microsoft 365 Copilot and [Microsoft 365 Copilot Chat](/copilot/overview) have an optional feature that allows Copilot to reference web content when responding to user prompts. Allowing Microsoft 365 Copilot and Microsoft 365 Copilot Chat to reference web content improves the quality of Copilot responses by grounding them in the latest information from the web.
23
23
24
+
> [!NOTE]
25
+
> This article concerns the web search functionality in Microsoft 365 Copilot and Microsoft 365 Copilot Chat. Microsoft 365 **Copilot Search** is an additional, universal search experience that allows users with a Microsoft 365 Copilot license to search across all their Microsoft 365 and third-party data sources. Learn more about [Microsoft 365 Copilot Search](/copilot/microsoft-365/microsoft-365-copilot-search).
26
+
24
27
## Web search
25
28
26
29
When web search is enabled, Microsoft 365 Copilot and Microsoft 365 Copilot Chat may fetch information from the Bing search service when information from the web helps to provide a better, more grounded response. Admin controls and a user-level **Web content** toggle (only for Microsoft 365 Copilot) are available to [manage whether web search is enabled](#controls-available-to-manage-web-search) in your environment.
Copy file name to clipboardExpand all lines: copilot/microsoft-365-copilot-overview.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,6 +57,8 @@ Microsoft 365 Copilot:
57
57
58
58
- Uses content in [Microsoft Graph](/graph/overview) to personalize the responses with a user's work emails, chats, and documents. Copilot only shows the data that users have permission to access.
59
59
60
+
- Includes [Microsoft 365 Copilot Search](/copilot/microsoft-365/microsoft-365-copilot-search), a universal search experience that allows users to search across all their Microsoft 365 and third-party data sources to find what they need quickly.
61
+
60
62
- Coordinates large language models (LLMs). LLMs are a type of artificial intelligence (AI) algorithms. These algorithms use deep learning techniques and data sets to understand, summarize, predict, and generate content.
61
63
62
64
The LLMs include pretrained models, like Generative Pre-Trained Transformers, like GPT-4, that are designed for these tasks. To learn more about Generative Pre-Trained Transformers (GPT), ask [Copilot](https://copilot.microsoft.com).
@@ -65,6 +67,7 @@ To learn more, see:
65
67
66
68
-[Microsoft 365 Copilot architecture and how it works](microsoft-365-copilot-architecture.md)
67
69
-[Microsoft 365 Copilot service description](/office365/servicedescriptions/office-365-platform-service-description/microsoft-365-copilot)
- Video: [Copilot system explained by Microsoft](https://www.youtube.com/watch?v=E5g20qmeKpg)
69
72
- Video: [Microsoft 365 Copilot, LLMs, and your apps](https://www.youtube.com/watch?v=B2-8wrF9Okc)
70
73
- Video: [How to get ready for Microsoft 365 Copilot](https://aka.ms/M365CopilotAdmin)
@@ -87,6 +90,12 @@ With Microsoft 365 Copilot Chat, you can draft content, review what you missed,
87
90
88
91
You can use Microsoft 365 Copilot Chat in Microsoft Teams, in the Microsoft 365 Copilot Chat app, at [Microsoft365.com](https://www.microsoft365.com/), and at [copilot.microsoft.com](https://copilot.microsoft.com/).
89
92
93
+
✅ **Microsoft 365 Copilot Search**
94
+
95
+
Copilot Search is an AI-powered universal search experience across all your Microsoft 365 applications and non-Microsoft data sources. It's integrated with Microsoft 365 Copilot, so users can find the results they need with search, then seamlessly transition to chat for deeper exploration or follow-up task completion.
96
+
97
+
Learn more about [Copilot Search](/copilot/microsoft-365/microsoft-365-copilot-search).
98
+
90
99
✅ **Microsoft Graph**
91
100
92
101
Microsoft Graph includes information on users, their activities, and the organization data they can access. The Microsoft Graph API brings a personalized context into the prompt, like information from a user's emails, chats, documents, and meetings.
0 commit comments