Skip to content

Commit a7ebef5

Browse files
committed
2 parents 4a36d77 + e278a38 commit a7ebef5

File tree

47 files changed

+674
-509
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

47 files changed

+674
-509
lines changed

.openpublishing.publish.config.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -233,6 +233,11 @@
233233
"url": "https://github.com/Azure-Samples/azure-iot-samples-node",
234234
"branch": "master"
235235
},
236+
{
237+
"path_to_root": "azure-iot-sdk-node",
238+
"url": "https://github.com/Azure/azure-iot-sdk-node",
239+
"branch": "master"
240+
},
236241
{
237242
"path_to_root": "iot-samples-c",
238243
"url": "https://github.com/Azure/azure-iot-sdk-c",

.openpublishing.redirection.json

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17800,6 +17800,11 @@
1780017800
"redirect_url": "/azure/sql-data-warehouse/sql-data-warehouse-load-with-data-factory",
1780117801
"redirect_document_id": false
1780217802
},
17803+
{
17804+
"source_path": "articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-get-started-visualize-with-power-bi.md",
17805+
"redirect_url": "/power-bi/service-azure-sql-data-warehouse-with-direct-connect",
17806+
"redirect_document_id": false
17807+
},
1780317808
{
1780417809
"source_path": "articles/sql-data-warehouse/sql-data-warehouse-load-from-azure-blob-storage-with-data-factory.md",
1780517810
"redirect_url": "/azure/sql-data-warehouse/sql-data-warehouse-load-with-data-factory",
@@ -17937,7 +17942,7 @@
1793717942
},
1793817943
{
1793917944
"source_path": "articles/sql-data-warehouse/sql-data-warehouse-get-started-visualize-with-power-bi.md",
17940-
"redirect_url": "/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-get-started-visualize-with-power-bi",
17945+
"redirect_url": "/power-bi/service-azure-sql-data-warehouse-with-direct-connect",
1794117946
"redirect_document_id": true
1794217947
},
1794317948
{

articles/active-directory/develop/v2-oauth2-auth-code-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ At a high level, the entire authentication flow for a native/mobile application
3131

3232
## Request an authorization code
3333

34-
The authorization code flow begins with the client directing the user to the `/authorize` endpoint. In this request, the client requests the `openid`, `offline_access`, and `https://graph.microsoft.com/mail.read ` permissions from from the user. Some permissions are admin-restricted, for example writing data to an organization's directory by using `Directory.ReadWrite.All`. If your application requests access to one of these permissions from an organizational user, the user receives an error message that says they're not authorized to consent to your app's permissions. To request access to admin-restricted scopes, you should request them directly from a company administrator. For more information, read [Admin-restricted permissions](v2-permissions-and-consent.md#admin-restricted-permissions).
34+
The authorization code flow begins with the client directing the user to the `/authorize` endpoint. In this request, the client requests the `openid`, `offline_access`, and `https://graph.microsoft.com/mail.read ` permissions from the user. Some permissions are admin-restricted, for example writing data to an organization's directory by using `Directory.ReadWrite.All`. If your application requests access to one of these permissions from an organizational user, the user receives an error message that says they're not authorized to consent to your app's permissions. To request access to admin-restricted scopes, you should request them directly from a company administrator. For more information, read [Admin-restricted permissions](v2-permissions-and-consent.md#admin-restricted-permissions).
3535

3636
```
3737
// Line breaks for legibility only

articles/analysis-services/analysis-services-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes how to backup and restore model metadata and
44
author: minewiskan
55
ms.service: azure-analysis-services
66
ms.topic: conceptual
7-
ms.date: 04/29/2020
7+
ms.date: 05/05/2020
88
ms.author: owend
99
ms.reviewer: minewiskan
1010

@@ -20,7 +20,7 @@ Backing up tabular model databases in Azure Analysis Services is much the same a
2020
>
2121
2222
> [!NOTE]
23-
> If the storage account is in a different region, firewall settings must be configured to allow access from **All networks**. Firewall settings configured for Selected networks with whitelisted IP addresses and Allow trusted Microsoft services exception is not supported.
23+
> If the storage account is in a different region, configure storage account firewall settings to allow access from **Selected networks**. In Firewall **Address range**, specify the IP address range for the region the Analysis Services server is in. Configuring storage account firewall settings to allow access from All networks is supported, however choosing Selected networks and specifying an IP address range is preferred. To learn more, see [Network connectivity FAQ](analysis-services-network-faq.md#backup-and-restore).
2424
2525
Backups are saved with an .abf extension. For in-memory tabular models, both model data and metadata are stored. For DirectQuery tabular models, only model metadata is stored. Backups can be compressed and encrypted, depending on the options you choose.
2626

articles/cognitive-services/LUIS/luis-concept-data-alteration.md

Lines changed: 8 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Data alteration - LUIS
33
description: Learn how data can be changed before predictions in Language Understanding (LUIS)
44
ms.topic: conceptual
5-
ms.date: 05/05/2020
5+
ms.date: 05/06/2020
66
---
77

88
# Alter utterance data before or during prediction
@@ -70,18 +70,15 @@ The Bing spell check API used in LUIS does not support a list of words to ignore
7070
## Change time zone of prebuilt datetimeV2 entity
7171
When a LUIS app uses the prebuilt [datetimeV2](luis-reference-prebuilt-datetimev2.md) entity, a datetime value can be returned in the prediction response. The timezone of the request is used to determine the correct datetime to return. If the request is coming from a bot or another centralized application before getting to LUIS, correct the timezone LUIS uses.
7272

73-
### Endpoint querystring parameter
74-
The timezone is corrected by adding the user's timezone to the endpoint using the appropriate parameter based on the API version. The value of the parameter should be the positive or negative number, in minutes, to alter the time.
73+
### V3 prediction API to alter timezone
7574

76-
|API version|Querystring parameter|
77-
|--|--|
78-
|v2|`timezoneOffset`|
79-
|v3|`datetimeReference`|
75+
In V3, the `datetimeReference` determines the timezone offset. Learn more about [V3 predictions](luis-migration-api-v3.md#v3-post-body).
8076

81-
### Daylight savings example
82-
If you need the returned prebuilt datetimeV2 to adjust for daylight savings time, you should use the querystring parameter with a +/- value in minutes for the [endpoint](https://go.microsoft.com/fwlink/?linkid=2092356) query.
77+
### V2 prediction API to alter timezone
78+
The timezone is corrected by adding the user's timezone to the endpoint using the `timezoneOffset` parameter based on the API version. The value of the parameter should be the positive or negative number, in minutes, to alter the time.
8379

84-
#### [V2 prediction endpoint request](#tab/V2)
80+
#### V2 prediction daylight savings example
81+
If you need the returned prebuilt datetimeV2 to adjust for daylight savings time, you should use the querystring parameter with a +/- value in minutes for the [endpoint](https://go.microsoft.com/fwlink/?linkid=2092356) query.
8582

8683
Add 60 minutes:
8784

@@ -91,21 +88,7 @@ Remove 60 minutes:
9188

9289
`https://{region}.api.cognitive.microsoft.com/luis/v2.0/apps/{appId}?q=Turn the lights on?timezoneOffset=-60&verbose={boolean}&spellCheck={boolean}&staging={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
9390

94-
#### [V3 prediction endpoint request](#tab/V3)
95-
96-
Add 60 minutes:
97-
98-
`https://{region}.api.cognitive.microsoft.com/luis/v3.0-preview/apps/{appId}/slots/production/predict?query=Turn the lights on?datetimeReference=60&spellCheck={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
99-
100-
Remove 60 minutes:
101-
102-
`https://{region}.api.cognitive.microsoft.com/luis/v3.0-preview/apps/{appId}/slots/production/predict?query=Turn the lights on?datetimeReference=-60&spellCheck={boolean}&bing-spell-check-subscription-key={string}&log={boolean}`
103-
104-
Learn more about the [V3 prediction endpoint](luis-migration-api-v3.md).
105-
106-
* * *
107-
108-
## C# code determines correct value of parameter
91+
#### V2 prediction C# code determines correct value of parameter
10992

11093
The following C# code uses the [TimeZoneInfo](https://docs.microsoft.com/dotnet/api/system.timezoneinfo) class's [FindSystemTimeZoneById](https://docs.microsoft.com/dotnet/api/system.timezoneinfo.findsystemtimezonebyid#examples) method to determine the correct offset value based on system time:
11194

articles/cognitive-services/Speech-Service/quickstart-custom-speech-commands-create-new.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,8 @@ For now, we have no parameters so we can move on to **Completion rules** section
120120
### Add a Completion rule
121121
122122
Now add a Completion rule with the following configuration. This rule indicates user that a fulfillment action is being taken.
123+
124+
123125
| Setting | Suggested value | Description |
124126
| ---------- | ---------------------------------------- | -------------------------------------------------- |
125127
| Rule Name | ConfirmationResponse | A name describing the purpose of the rule |

articles/cosmos-db/cassandra-change-feed.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,8 @@ The following example shows how to get a change feed on all the rows in a Cassan
1717

1818
In each iteration, the query resumes at the last point changes were read, using paging state. We can see a continuous stream of new changes to the table in the Keyspace. We will see changes to rows that are inserted, or updated. Watching for delete operations using change feed in Cassandra API is currently not supported.
1919

20+
# [C#](#tab/csharp)
21+
2022
```C#
2123
//set initial start time for pulling the change feed
2224
DateTime timeBegin = DateTime.UtcNow;
@@ -65,6 +67,9 @@ In each iteration, the query resumes at the last point changes were read, using
6567
}
6668

6769
```
70+
71+
# [Java](#tab/java)
72+
6873
```java
6974
Session cassandraSession = utils.getSession();
7075

@@ -99,19 +104,27 @@ In each iteration, the query resumes at the last point changes were read, using
99104
}
100105

101106
```
107+
---
108+
102109
In order to get the changes to a single row by primary key, you can add the primary key in the query. The following example shows how to track changes for the row where "user_id = 1"
103110

111+
# [C#](#tab/csharp)
112+
104113
```C#
105114
//Return the latest change for all row in 'user' table where user_id = 1
106115
IStatement changeFeedQueryStatement = new SimpleStatement(
107116
$"SELECT * FROM uprofile.user where user_id = 1 AND COSMOS_CHANGEFEED_START_TIME() = '{timeBegin.ToString("yyyy-MM-ddTHH:mm:ss.fffZ", CultureInfo.InvariantCulture)}'");
108117

109118
```
119+
120+
# [Java](#tab/java)
121+
110122
```java
111123
String query="SELECT * FROM uprofile.user where user_id=1 and COSMOS_CHANGEFEED_START_TIME()='"
112124
+ dtf.format(now)+ "'";
113125
SimpleStatement st=new SimpleStatement(query);
114126
```
127+
---
115128
## Current limitations
116129

117130
The following limitations are applicable when using change feed with Cassandra API:

articles/cosmos-db/create-sql-api-java-changefeed.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,6 @@ mvn clean package
8686

8787
# [Java SDK 4.0](#tab/v4sdk)
8888

89-
**Java SDK 4.0**
9089
```java
9190
changeFeedProcessorInstance = getChangeFeedProcessor("SampleHost_1", feedContainer, leaseContainer);
9291
changeFeedProcessorInstance.start()
@@ -101,7 +100,6 @@ mvn clean package
101100
102101
# [Java SDK 3.7.0](#tab/v3sdk)
103102
104-
**Java SDK 3.7.0**
105103
```java
106104
changeFeedProcessorInstance = getChangeFeedProcessor("SampleHost_1", feedContainer, leaseContainer);
107105
changeFeedProcessorInstance.start()
@@ -114,7 +112,7 @@ mvn clean package
114112
while (!isProcessorRunning.get()); //Wait for Change Feed processor start
115113
```
116114
---
117-
115+
118116
```"SampleHost_1"``` is the name of the Change Feed processor worker. ```changeFeedProcessorInstance.start()``` is what actually starts the Change Feed processor.
119117
120118
Return to the Azure Portal Data Explorer in your browser. Under the **InventoryContainer-leases** container, click **items** to see its contents. You will see that Change Feed Processor has populated the lease container, i.e. the processor has assigned the ```SampleHost_1``` worker a lease on some partitions of the **InventoryContainer**.
@@ -125,7 +123,6 @@ mvn clean package
125123
126124
# [Java SDK 4.0](#tab/v4sdk)
127125
128-
**Java SDK 4.0**
129126
```java
130127
public static ChangeFeedProcessor getChangeFeedProcessor(String hostName, CosmosAsyncContainer feedContainer, CosmosAsyncContainer leaseContainer) {
131128
ChangeFeedProcessorOptions cfOptions = new ChangeFeedProcessorOptions();
@@ -153,7 +150,6 @@ mvn clean package
153150
154151
# [Java SDK 3.7.0](#tab/v3sdk)
155152
156-
**Java SDK 3.7.0**
157153
```java
158154
public static ChangeFeedProcessor getChangeFeedProcessor(String hostName, CosmosContainer feedContainer, CosmosContainer leaseContainer) {
159155
ChangeFeedProcessorOptions cfOptions = new ChangeFeedProcessorOptions();
@@ -196,7 +192,6 @@ mvn clean package
196192
197193
# [Java SDK 4.0](#tab/v4sdk)
198194
199-
**Java SDK 4.0**
200195
```java
201196
public static void deleteDocument() {
202197
@@ -225,7 +220,6 @@ mvn clean package
225220
```
226221
# [Java SDK 3.7.0](#tab/v3sdk)
227222
228-
**Java SDK 3.7.0**
229223
```java
230224
public static void deleteDocument() {
231225

articles/cosmos-db/mongodb-change-streams.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following error codes and messages are supported when using change streams:
4040

4141
The following example shows how to get change streams on all the items in the collection. This example creates a cursor to watch items when they are inserted, updated, or replaced. The `$match` stage, `$project` stage, and `fullDocument` option are required to get the change streams. Watching for delete operations using change streams is currently not supported. As a workaround, you can add a soft marker on the items that are being deleted. For example, you can add an attribute in the item called "deleted." When you'd like to delete the item, you can set "deleted" to `true` and set a TTL on the item. Since updating "deleted" to `true` is an update, this change will be visible in the change stream.
4242

43-
### JavaScript:
43+
# [JavaScript](#tab/javascript)
4444

4545
```javascript
4646
var cursor = db.coll.watch(
@@ -56,8 +56,7 @@ while (!cursor.isExhausted()) {
5656
}
5757
}
5858
```
59-
60-
### C#:
59+
# [C#](#tab/csharp)
6160

6261
```csharp
6362
var pipeline = new EmptyPipelineDefinition<ChangeStreamDocument<BsonDocument>>()

articles/event-grid/toc.yml

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -164,21 +164,15 @@
164164
- name: Monitor and troubleshoot
165165
items:
166166
- name: Diagnostic logs
167-
href:
167+
href: diagnostic-logs.md
168168
- name: Metrics
169169
href: metrics.md
170170
- name: How-to guides
171171
items:
172-
- name: Configure private endpoints (preview)
173-
href: configure-private-endpoints.md
174-
- name: Configure IP firewall (preview)
175-
href: configure-firewall.md
176172
- name: Post to custom topic
177173
href: post-to-custom-topic.md
178174
- name: Receive events at HTTP endpoint
179175
href: receive-events.md
180-
- name: Secure WebHook with AAD
181-
href: secure-webhook-delivery.md
182176
- name: Dead letter and retry
183177
href: manage-event-delivery.md
184178
- name: Filter events
@@ -197,6 +191,14 @@
197191
href: custom-disaster-recovery.md
198192
- name: Track asynchronous REST operations
199193
href: ../azure-resource-manager/management/async-operations.md?toc=%2fazure%2fevent-grid%2ftoc.json
194+
- name: Secure
195+
items:
196+
- name: Configure private endpoints (preview)
197+
href: configure-private-endpoints.md
198+
- name: Configure IP firewall (preview)
199+
href: configure-firewall.md
200+
- name: Secure WebHook with AAD
201+
href: secure-webhook-delivery.md
200202
- name: Troubleshoot
201203
items:
202204
- name: Enable diagnostic logs

0 commit comments

Comments
 (0)