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: articles/active-directory-b2c/configure-authentication-sample-web-app-with-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,14 +62,14 @@ A computer that's running either:
62
62
63
63
# [Visual Studio](#tab/visual-studio)
64
64
65
-
*[Visual Studio 2019 16.8 or later](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the **ASP.NET and web development** workload
*[Visual Studio 2022 17.0 or later](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) with the **ASP.NET and web development** workload
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/private-link-design.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ The AMPLS object has the following limits:
90
90
91
91
In the below diagram:
92
92
* Each VNet connects to only **one** AMPLS object.
93
-
* AMPLS A connects to two workspaces and one Application Insight component, using 2 of the possible 300 Log Analytics workspaces and 1 of the possible 1 Application Insights components it can connect to.
93
+
* AMPLS A connects to two workspaces and one Application Insight component, using 2 of the possible 300 Log Analytics workspaces and 1 of the possible 1000 Application Insights components it can connect to.
94
94
* Workspace2 connects to AMPLS A and AMPLS B, using two of the five possible AMPLS connections.
95
95
* AMPLS B is connected to Private Endpoints of two VNets (VNet2 and VNet3), using two of the 10 possible Private Endpoint connections.
Copy file name to clipboardExpand all lines: articles/cognitive-services/Bing-Web-Search/use-display-requirements.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: nitinme
8
8
ms.service: cognitive-services
9
9
ms.subservice: bing-web-search
10
10
ms.topic: conceptual
11
-
ms.date: 01/31/2019
11
+
ms.date: 03/02/2022
12
12
ms.author: aahi
13
13
---
14
14
@@ -30,7 +30,6 @@ These use and display requirements apply to any implementation of the content an
30
30
31
31
## Definitions
32
32
33
-
34
33
|Term |Description |
35
34
|---------|---------|
36
35
|Answer | A category of results returned in a response. For example, a response from the Bing Web Search API can include answers in the categories of webpage results, image, video, visual, and news. |
@@ -48,67 +47,68 @@ Do not:
48
47
## Bing Search APIs
49
48
50
49
> [!NOTE]
51
-
> The requirements in this section apply to only the Search APIs, which does not include Bing Spell Check or Bing Autosuggest.
50
+
> The requirements in this section apply to only the Search APIs, which does not include Bing Spell Check or Bing Autosuggest.
52
51
53
52
### Internet search experience requirements
54
53
55
-
All data returned in responses may only be used in internet search experiences. An internet search experience means the content displayed:
54
+
All data returned in responses may only be used in internet search experiences. An internet search experience means the content displayed:
56
55
57
-
- Is relevant and responsive to the end user's direct query, or other indication of their search interest and intent (for example, a user-indicated search query).
56
+
- Is relevant and responsive to the end user's direct query, or other indication of their search interest and intent (for example, a user-indicated search query).
58
57
59
58
- Helps users find and navigate to the response's data sources. For example, providing clickable links from hyperlinks in the response.
60
59
61
-
- Includes multiple results for the user to select from.
60
+
- Includes multiple results for the user to select from.
62
61
63
62
- Are in a placement that enables users to search.
64
63
65
64
- Includes a visible indication that the content is an internet search result. For example, a statement that the content is "from the web".
66
65
67
66
- Includes any other appropriate measures to ensure your Bing Search API data does not violate any applicable laws or third-party rights. Consult your legal advisors to determine what measures may be appropriate.
68
67
69
-
The only exception to these internet search experience requirements is for URL discovery, as described later in this article.
68
+
The only exception to these internet search experience requirements is for URL discovery, as described later in this article.
70
69
71
70
### Restrictions
72
71
73
72
Do not:
74
73
75
-
- Copy, store, or cache any data from responses (except retention to the extent permitted by [continuity of service](#continuity-of-service).
74
+
- Copy, store, or cache any data from responses (except retention to the extent permitted by [continuity of service](#continuity-of-service).
76
75
77
76
- Use data received from the Search APIs as part of any machine learning or similar algorithmic activity. Do not use this data to train, evaluate, or improve new or existing services that you or third parties might offer.
78
77
79
-
- Modify the content of results (other than to reformat them in a way that does not violate any other requirement), unless required by law or agreed to by Microsoft.
78
+
- Modify the content of results (other than to reformat them in a way that does not violate any other requirement), unless required by law or agreed to by Microsoft.
80
79
81
80
- Omit attribution information and URLs associated with result content.
82
81
83
-
- Reorder, including by omission, the results displayed in an answer when an order or ranking is provided, unless required by law or agreed to by Microsoft.
82
+
- Reorder, including by omission, the results displayed in an answer when an order or ranking is provided, unless required by law or agreed to by Microsoft.
84
83
85
84
> [!NOTE]
86
85
> This requirement does not apply to reordering implemented through the portal for the Bing Custom Search API.
87
86
88
-
- Display other content within any part of a response in a way that would lead a user to believe that the other content is part of the response.
87
+
- Display other content within any part of a response in a way that would lead a user to believe that the other content is part of the response.
89
88
90
-
- Display advertising that is not provided by Microsoft on any page that displays any part of a response.
89
+
- Display advertising that is not provided by Microsoft on any page that displays any part of a response.
91
90
92
91
- Display any advertising on pages with responses:
93
-
- From the Bing Image, News Search, Video Search, or Visual Search APIs
94
-
- That are filtered or limited primarily (or solely) to image, news and/or video or visual search results.
92
+
- From the Bing Image, News Search, Video Search, or Visual Search APIs
93
+
- That are filtered or limited primarily (or solely) to image, news and/or video or visual search results.
94
+
95
+
### Notices and branding
95
96
96
-
### Notices and branding
97
97
Do:
98
98
99
99
- Prominently include a functional hyperlink to the [Microsoft Privacy Statement](https://go.microsoft.com/fwlink/?LinkId=521839), near each point in the user experience (UX) that offers a user the ability to input a search query. Label the hyperlink **Microsoft Privacy Statement**.
100
100
101
-
- Prominently display Bing branding, consistent with the [Bing Trademark Usage Guidelines](https://go.microsoft.com/fwlink/?linkid=833278), near each point in the UX that offers a user the ability to input a search query. Such branding must clearly state to the user that Microsoft is powering the internet search experience.
101
+
- Prominently display Bing branding, consistent with the [Bing Trademark Usage Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks), near each point in the UX that offers a user the ability to input a search query. Such branding must clearly state to the user that Microsoft is powering the internet search experience.
102
102
103
-
- You can attribute each response (or portion of a response) displayed from the Bing Web Search, Image Search, News Search, Video Search, and Visual Search APIs to Microsoft, unless Microsoft specifies otherwise in writing for your use. This is described in [Bing Trademark Usage Guidelines](https://go.microsoft.com/fwlink/?linkid=833278).
103
+
- You can attribute each response (or portion of a response) displayed from the Bing Web Search, Image Search, News Search, Video Search, and Visual Search APIs to Microsoft, unless Microsoft specifies otherwise in writing for your use. This is described in [Bing Trademark Usage Guidelines](https://www.microsoft.com/legal/intellectualproperty/trademarks).
104
104
105
105
Do not:
106
106
107
107
- Attribute responses (or portions of responses) displayed from the Bing Custom Search API to Microsoft, unless Microsoft specifies otherwise in writing for your particular use.
108
108
109
109
### Transferring responses
110
110
111
-
If you enable a user to transfer a response from a Search API to another user, such as through a messaging app or social media posting, the following apply:
111
+
If you enable a user to transfer a response from a Search API to another user, such as through a messaging app or social media posting, the following apply:
112
112
113
113
- Transferred responses must:
114
114
- Consist of content that is unmodified from the content of the responses displayed to the transferring user. Formatting changes are permissible.
@@ -120,7 +120,7 @@ If you enable a user to transfer a response from a Search API to another user, s
120
120
- You may not automate the transfer of responses. A transfer must be initiated by a user action clearly evidencing an intent to transfer a response.
121
121
- You may only enable a user to transfer responses that were displayed in response to the transferring user's query.
122
122
123
-
### Continuity of service
123
+
### Continuity of service
124
124
125
125
Do not copy, store, or cache any data from Search API responses. However, to enable continuity of service access and data rendering, you may retain results solely under the following conditions:
126
126
@@ -140,28 +140,28 @@ You may retain results specific to a single user securely on a server you contro
140
140
141
141
Whenever retained, results for a specific user cannot be commingled with results for another user. That is, the results of each user must be retained and delivered separately.
142
142
143
-
### General
143
+
### General
144
144
145
145
For all presentation of retained results:
146
146
147
147
- Include a clear, visible notice of the time the query was sent.
148
-
- Present the user with a button or similar means to re-query and obtain updated results.
148
+
- Present the user with a button or similar means to re-query and obtain updated results.
149
149
- Retain the Bing branding in the presentation of the results.
150
150
- Delete (and refresh with a new query if needed) the stored results within the timeframes specified.
151
151
152
-
### Non-display URL discovery
152
+
### Non-display URL discovery
153
153
154
154
You may only use search responses in a non-internet search experience for the sole purpose of discovering URLs of sources of information responsive to a query from your user or customer. You may copy such URLs in a report or similar response you provide:
155
155
156
156
- Only to that user or customer, in response to that query.
157
157
- Only if it includes significant additional valuable content, relevant to the query.
158
158
159
-
The previous sections of Search APIs use and display requirements do not apply to this non-display use, except for the following:
159
+
The previous sections of Search APIs use and display requirements do not apply to this non-display use, except for the following:
160
160
161
161
- Do not cache, copy, or store any data or content from, or derived from, the search response, other than the limited URL copying described previously.
162
162
- Ensure your use of data (including the URLs) received from the Search APIs does not violate any applicable laws or third-party rights.
163
163
- Do not use the data (including the URLs) received from the Search APIs as part of any search index or machine learning or similar algorithmic activity. Do not use this data to create train, evaluate, or improve services that you or third parties might offer.
164
164
165
165
## GDPR compliance
166
166
167
-
With respect to any personal data subject to the European Union General Data Protection Regulation (GDPR) and that is processed in connection with calls to the Search APIs, Bing Spell Check API, or Bing Autosuggest API, you understand that you and Microsoft are independent data controllers under the GDPR. You are independently responsible for your compliance with the GDPR.
167
+
With respect to any personal data subject to the European Union General Data Protection Regulation (GDPR) and that is processed in connection with calls to the Search APIs, Bing Spell Check API, or Bing Autosuggest API, you understand that you and Microsoft are independent data controllers under the GDPR. You are independently responsible for your compliance with the GDPR.
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/router/azure-function-rule-engine.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ The decision flow (as shown above) is as follows:
88
88
89
89
Before moving on any further in the process, let us first define an Azure function that scores worker.
90
90
> [!NOTE]
91
-
> The following Azure function is using Javascript. For more information, please refer to [Quickstart: Create a JavaScript function in Azure using Visual Studio Code](../../../azure-functions/create-first-function-vs-code-node.md)
91
+
> The following Azure function is using JavaScript. For more information, please refer to [Quickstart: Create a JavaScript function in Azure using Visual Studio Code](../../../azure-functions/create-first-function-vs-code-node.md)
Copy file name to clipboardExpand all lines: articles/web-application-firewall/afds/waf-front-door-tuning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,7 +140,7 @@ One benefit of using an exclusion list is that only the match variable you selec
140
140
141
141
It’s important to consider that exclusions are a global setting. This means that the configured exclusion will apply to all traffic passing through your WAF, not just a specific web app or URI. For example, this could be a concern if *1=1* is a valid request in the body for a certain web app, but not for others under the same WAF policy. If it makes sense to use different exclusion lists for different applications, consider using different WAF policies for each application and applying them to each application's frontend.
142
142
143
-
When configuring exclusion lists for managed rules, you can choose to exclude all rules within a rule set, all rules within a rule group, or an individual rule. An exclusion list can be configured using [PowerShell](/powershell/module/az.frontdoor/New-AzFrontDoorWafManagedRuleExclusionObject), [Azure CLI](/cli/azure/network/front-door/waf-policy/managed-rules/exclusion), [Rest API](/rest/api/frontdoorservice/webapplicationfirewall/policies/createorupdate), or the Azure portal.
143
+
When configuring exclusion lists for managed rules, you can choose to exclude all rules within a rule set, all rules within a rule group, or an individual rule. An exclusion list can be configured using [PowerShell](/powershell/module/az.frontdoor/New-AzFrontDoorWafManagedRuleExclusionObject), [Azure CLI](/cli/azure/network/front-door/waf-policy/managed-rules/exclusion), [REST API](/rest/api/frontdoorservice/webapplicationfirewall/policies/createorupdate), or the Azure portal.
144
144
145
145
* Exclusions at a rule level
146
146
* Applying exclusions at a rule level means that the specified exclusions will not be analyzed against that individual rule only, while it will still be analyzed by all other rules in the rule set. This is the most granular level for exclusions, and it can be used to fine-tune the managed rule set based on the information you find in the WAF logs when troubleshooting an event.
0 commit comments