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/industry/agriculture/query-telemetry-data-from-azure-farmbeats.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
@@ -113,7 +113,7 @@ Follow the steps to visualize data on TSI:
113
113
1. Go to **Azure Portal** > **FarmBeats DataHub resource group** > select **Time Series Insights** environment (tsi-xxxx) > **Data Access Policies**. Add user with Reader or Contributor access.
114
114
2. Go to the **Overview** page of **Time Series Insights** environment (tsi-xxxx) and select the **Time Series Insights Explorer URL**. You'll now be able to visualize the ingested telemetry.
115
115
116
-
Apart from storing, querying and visualization of telemetry, TSI also enables integration to a Power BI dashboard. For more information, see [here](https://docs.microsoft.com/azure/time-series-insights/how-to-connect-power-bi)
116
+
Apart from storing, querying and visualization of telemetry, TSI also enables integration to a Power BI dashboard. For more information, see [here](../../time-series-insights/how-to-connect-power-bi.md)
Copy file name to clipboardExpand all lines: articles/marketplace/find-tenant-object-id.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,14 +52,15 @@ If you need to get screenshots of these items in Azure Cloud Shell to use for de
52
52
1. Sign in to the [Office 365 Admin Portal](https://portal.office.com/adminportal/home) with an account in the desired tenant with the appropriate administrative rights.
53
53
2. In the left-side menu, expand the **Admin Centers** section at the bottom and then select the Azure Active Directory option to launch the admin console in a new browser window.
54
54
3. Select **Users**.
55
-
4. Browse to or search for the desired user, then select the account name to view the user account’s profile information.
55
+
4. Browse to or search for the desired user, then select the account name to view the user account's profile information.
56
56
5. The Object ID is located in the Identity section on the right.
57
57
58
58
:::image type="content" source="media/tenant-and-object-id/azure-ad-admin-center.png" alt-text="Azure Active Directory admin center.":::
59
59
60
60
6. Find **role assignments** by selecting **Access control (IAM)** in the left menu, then **Role assignments**.
61
61
62
-
:::image type="content" source="https://docs.microsoft.com/azure/role-based-access-control/media/role-assignments-portal/role-assignments.png" alt-text="Role assignments for Azure resources.":::
62
+
:::image type="content" source="../role-based-access-control/media/role-assignments-portal/rg-role-assignments.png" alt-text="Role assignments for Azure resources.":::
Copy file name to clipboardExpand all lines: articles/security/develop/threat-modeling-tool-cryptography.md
+3-11Lines changed: 3 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,17 @@
1
1
---
2
2
title: Cryptography - Microsoft Threat Modeling Tool - Azure | Microsoft Docs
3
3
description: Learn about cryptography mitigation for threats exposed in the Threat Modeling Tool. See mitigation information and view code examples.
4
-
services: security
5
-
documentationcenter: na
6
4
author: jegeib
7
5
manager: jegeib
8
6
editor: jegeib
9
-
10
-
ms.assetid: na
11
7
ms.service: security
12
8
ms.subservice: security-develop
13
-
ms.workload: na
14
-
ms.tgt_pltfrm: na
15
-
ms.devlang: na
16
9
ms.topic: article
17
10
ms.date: 02/07/2017
18
11
ms.author: jegeib
19
-
20
12
---
21
13
22
-
# Security Frame: Cryptography | Mitigations
14
+
# Security Frame: Cryptography | Mitigation
23
15
24
16
| Product/Service | Article |
25
17
| --------------- | ------- |
@@ -167,12 +159,12 @@ ms.author: jegeib
167
159
168
160
| Title | Details |
169
161
| ----------------------- | ------------ |
170
-
|**Component**| IoT Device |
162
+
|**Component**| IoT Device |
171
163
|**SDL Phase**| Build |
172
164
|**Applicable Technologies**| Generic |
173
165
|**Attributes**| Device OS - Windows IoT Core, Device Connectivity - Azure IoT device SDKs |
174
166
|**References**|[TPM on Windows IoT Core](/windows/iot-core/secure-your-device/TPM), [Set up TPM on Windows IoT Core](/windows/iot-core/secure-your-device/setuptpm), [Azure IoT Device SDK TPM](https://github.com/Azure/azure-iot-hub-vs-cs/wiki/Device-Provisioning-with-TPM)|
175
-
|**Steps**| Symmetric or Certificate Private keys securely in a hardware protected storage like TPM or Smart Card chips. Windows 10 IoT Core supports the user of a TPM and there are several compatible TPMs that can be used: https://docs.microsoft.com/windows/iot-core/secure-your-device/tpm#discrete-tpm-dtpm. It is recommended to use a Firmware or Discrete TPM. A Software TPM should only be used for development and testing purposes. Once a TPM is available and the keys are provisioned in it, the code that generates the token should be written without hard coding any sensitive information in it. |
167
+
|**Steps**| Symmetric or Certificate Private keys securely in a hardware protected storage like TPM or Smart Card chips. Windows 10 IoT Core supports the user of a TPM and there are several compatible TPMs that can be used: [Discrete TPM (dTPM)](/windows/iot-core/secure-your-device/tpm#discrete-tpm-dtpm). It is recommended to use a Firmware or Discrete TPM. A Software TPM should only be used for development and testing purposes. Once a TPM is available and the keys are provisioned in it, the code that generates the token should be written without hard coding any sensitive information in it. |
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-node-transition-apis.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,6 @@
2
2
title: Start and stop cluster nodes
3
3
description: Learn how to use fault injection to test a Service Fabric application by starting and stopping cluster nodes.
4
4
author: LMWF
5
-
6
5
ms.topic: conceptual
7
6
ms.date: 6/12/2017
8
7
ms.author: lemai
@@ -21,17 +20,16 @@ As described earlier, a *stopped* Service Fabric node is a node intentionally ta
21
20
22
21
In addition, some errors returned by these APIs are not as descriptive as they could be. For example, invoking the Stop Node API on an already *stopped* node will return the error *InvalidAddress*. This experience could be improved.
23
22
24
-
Also, the duration a node is stopped for is “infinite” until the Start Node API is invoked. We’ve found this can cause problems and may be error-prone. For example, we’ve seen problems where a user invoked the Stop Node API on a node and then forgot about it. Later, it was unclear if the node was *down* or *stopped*.
23
+
Also, the duration a node is stopped for is "infinite" until the Start Node API is invoked. We've found this can cause problems and may be error-prone. For example, we've seen problems where a user invoked the Stop Node API on a node and then forgot about it. Later, it was unclear if the node was *down* or *stopped*.
25
24
26
25
27
26
## Introducing the Node Transition APIs
28
27
29
-
We’ve addressed these issues above in a new set of APIs. The new Node Transition API (managed: [StartNodeTransitionAsync()][snt]) may be used to transition a Service Fabric node to a *stopped* state, or to transition it from a *stopped* state to a normal up state. Please note that the “Start” in the name of the API does not refer to starting a node. It refers to beginning an asynchronous operation that the system will execute to transition the node to either *stopped* or started state.
28
+
We've addressed these issues above in a new set of APIs. The new Node Transition API (managed: [StartNodeTransitionAsync()][snt]) may be used to transition a Service Fabric node to a *stopped* state, or to transition it from a *stopped* state to a normal up state. Please note that the "Start" in the name of the API does not refer to starting a node. It refers to beginning an asynchronous operation that the system will execute to transition the node to either *stopped* or started state.
30
29
31
30
**Usage**
32
31
33
-
If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it. A successful call does not imply the operation is finished yet. To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation. The Node Transition Progress API returns an NodeTransitionProgress object. This object’s State property specifies the current state of the operation. If the state is “Running”, then the operation is executing. If it is Completed, the operation finished without error. If it is Faulted, there was a problem executing the operation. The Result property’s Exception property will indicate what the issue was. See https://docs.microsoft.com/dotnet/api/system.fabric.testcommandprogressstate for more information about the State property, and the “Sample Usage” section below for code examples.
34
-
32
+
If the Node Transition API does not throw an exception when invoked, then the system has accepted the asynchronous operation, and will execute it. A successful call does not imply the operation is finished yet. To get information about the current state of the operation, call the Node Transition Progress API (managed: [GetNodeTransitionProgressAsync()][gntp]) with the guid used when invoking Node Transition API for this operation. The Node Transition Progress API returns an NodeTransitionProgress object. This object's State property specifies the current state of the operation. If the state is "Running", then the operation is executing. If it is Completed, the operation finished without error. If it is Faulted, there was a problem executing the operation. The Result property's Exception property will indicate what the issue was. See [TestCommandProgressState Enum](/dotnet/api/system.fabric.testcommandprogressstate) for more information about the State property, and the "Sample Usage" section below for code examples.
35
33
36
34
**Differentiating between a stopped node and a down node**
37
35
If a node is *stopped* using the Node Transition API, the output of a node query (managed: [GetNodeListAsync()][nodequery], PowerShell: [Get-ServiceFabricNode][nodequeryps]) will show that this node has an *IsStopped* property value of true. Note this is different from the value of the *NodeStatus* property, which will say *Down*. If the *NodeStatus* property has a value of *Down*, but *IsStopped* is false, then the node was not stopped using the Node Transition API, and is *Down* due to some other reason. If the *IsStopped* property is true, and the *NodeStatus* property is *Down*, then it was stopped using the Node Transition API.
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-sfctl-chaos.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,6 @@
2
2
title: Azure Service Fabric CLI- sfctl chaos
3
3
description: Learn about sfctl, the Azure Service Fabric command line interface. Includes a list of commands for managing chaos.
4
4
author: jeffj6123
5
-
6
5
ms.topic: reference
7
6
ms.date: 1/16/2020
8
7
ms.author: jejarry
@@ -72,7 +71,7 @@ Get the status of Chaos indicating whether or not Chaos is running, the Chaos pa
72
71
## sfctl chaos start
73
72
Starts Chaos in the cluster.
74
73
75
-
If Chaos is not already running in the cluster, it starts Chaos with the passed in Chaos parameters. If Chaos is already running when this call is made, the call fails with the error code FABRIC_E_CHAOS_ALREADY_RUNNING. Refer to the article [Induce controlled Chaos in Service Fabric clusters](https\://docs.microsoft.com/azure/service-fabric/service-fabric-controlled-chaos) for more details.
74
+
If Chaos is not already running in the cluster, it starts Chaos with the passed in Chaos parameters. If Chaos is already running when this call is made, the call fails with the error code FABRIC_E_CHAOS_ALREADY_RUNNING. Refer to the article [Induce controlled Chaos in Service Fabric clusters](service-fabric-controlled-chaos.md) for more details.
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/sap/hana-vm-troubleshoot-scale-out-ha-on-sles.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,17 +2,14 @@
2
2
title: SAP HANA scale-out HSR-Pacemaker with SLES on Azure VMs troubleshooting| Microsoft Docs
3
3
description: Guide to check and troubleshoot a complex SAP HANA scale-out high-availability configuration based on SAP HANA System Replication (HSR) and Pacemaker on SLES 12 SP3 running on Azure virtual machines
@@ -43,7 +40,7 @@ SUSE published a [detailed description of this performance-optimized setup][sles
43
40
For virtual machine types that are supported for SAP HANA scale-out, check the [SAP HANA certified IaaS directory][sap-hana-iaas-list].
44
41
45
42
> [!NOTE]
46
-
> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we’ll remove them from this article.
43
+
> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we'll remove them from this article.
47
44
48
45
There was a technical issue with SAP HANA scale-out in combination with multiple subnets and vNICs and setting up HSR. It's mandatory to use the latest SAP HANA 2.0 patches where this issue was fixed. The following SAP HANA versions are supported:
0 commit comments