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/app-service/configure-authentication-provider-aad.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
@@ -151,8 +151,7 @@ At present, this allows _any_ client application in your Azure AD tenant to requ
151
151
You have now configured a daemon client application that can access your App Service app using its own identity.
152
152
153
153
> [!NOTE]
154
-
> The access tokens provided to your app via EasyAuth do not have scopes for other APIs, such as Graph, even if your application has permissions to access those APIs.
155
-
To use these APIs, you will need to use Azure Resource Manager to configure the token returned so it can be used to authenticate to other services. You can see an example of [this tutorial](https://docs.microsoft.com/azure/app-service/scenario-secure-app-access-microsoft-graph-as-user?tabs=azure-resource-explorer)
154
+
> The access tokens provided to your app via EasyAuth do not have scopes for other APIs, such as Graph, even if your application has permissions to access those APIs. To use these APIs, you will need to use Azure Resource Manager to configure the token returned so it can be used to authenticate to other services. For more information, see [Tutorial: Access Microsoft Graph from a secured .NET app as the user](/azure/app-service/scenario-secure-app-access-microsoft-graph-as-user?tabs=azure-resource-explorer) .
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/create-workspace-resource.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
@@ -167,7 +167,7 @@ The `New-AzApplicationInsights` PowerShell command does not currently support cr
167
167
```
168
168
169
169
> [!NOTE]
170
-
> * For more information on resource properties, see [Property values](https://docs.microsoft.com/azure/templates/microsoft.insights/components?tabs=bicep#property-values)
170
+
> * For more information on resource properties, see [Property values](/azure/templates/microsoft.insights/components?tabs=bicep#property-values)
171
171
> * Flow_Type and Request_Source are not used, but are included in this sample for completeness.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/understand-guidelines-active-directory-domain-service-site.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
@@ -95,7 +95,7 @@ You should use Active Directory Domain Services (AD DS) in the following scenari
95
95
> [!NOTE]
96
96
> Azure NetApp Files doesn't support the use of AD DS Read-only Domain Controllers (RODC).
97
97
98
-
If you choose to use AD DS with Azure NetApp Files, follow the guidance in [Extend AD DS into Azure Architecture Guide](https://docs.microsoft.com/azure/architecture/reference-architectures/identity/adds-extend-domain) and ensure that you meet the Azure NetApp Files [network](#network-requirements) and [DNS requirements](#ad-ds-requirements) for AD DS.
98
+
If you choose to use AD DS with Azure NetApp Files, follow the guidance in [Extend AD DS into Azure Architecture Guide](/azure/architecture/reference-architectures/identity/adds-extend-domain) and ensure that you meet the Azure NetApp Files [network](#network-requirements) and [DNS requirements](#ad-ds-requirements) for AD DS.
99
99
100
100
### Azure Active Directory Domain Services considerations
Copy file name to clipboardExpand all lines: articles/cloud-shell/overview.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
@@ -28,7 +28,7 @@ You can access the Cloud Shell in three ways:
28
28
29
29

30
30
31
-
-**Code snippets**: On [docs.microsoft.com]() and [Microsoft Learn](/learn/), select the **Try It** button that appears with Azure CLI and Azure PowerShell code snippets:
31
+
-**Code snippets**: In Microsoft [technical documentation](/) and [training resources](/learn), select the **Try It** button that appears with Azure CLI and Azure PowerShell code snippets:
Copy file name to clipboardExpand all lines: articles/service-fabric/how-to-managed-cluster-dedicated-hosts.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Before you begin:
25
25
26
26
* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free)
27
27
* Retrieve a managed cluster ARM template. Sample Resource Manager templates are available in the [Azure samples on GitHub](https://github.com/Azure-Samples/service-fabric-cluster-templates). These templates can be used as a starting point for your cluster template. This guide shows how to deploy a Standard SKU cluster with two node types and 12 nodes.
28
-
* The user needs to have Microsoft.Authorization/roleAssignments/write permissions to the host group such as [User Access Administrator](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#user-access-administrator) or [Owner](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#owner) to do role assignments in a host group. For more information, see [Assign Azure roles using the Azure portal - Azure RBAC](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal?tabs=current#prerequisites).
28
+
* The user needs to have Microsoft.Authorization/roleAssignments/write permissions to the host group such as [User Access Administrator](/azure/role-based-access-control/built-in-roles#user-access-administrator) or [Owner](/azure/role-based-access-control/built-in-roles#owner) to do role assignments in a host group. For more information, see [Assign Azure roles using the Azure portal - Azure RBAC](/azure/role-based-access-control/role-assignments-portal?tabs=current#prerequisites).
29
29
30
30
31
31
## Review the template
@@ -34,7 +34,7 @@ The template used in this guide is from [Azure Samples - Service Fabric cluster
34
34
## Create a client certificate
35
35
Service Fabric managed clusters use a client certificate as a key for access control. If you already have a client certificate that you would like to use for access control to your cluster, you can skip this step.
36
36
37
-
If you need to create a new client certificate, follow the steps in [set and retrieve a certificate from Azure Key Vault](https://docs.microsoft.com/azure/key-vault/certificates/quick-create-portal). Note the certificate thumbprint as it will be required to deploy the template in the next step.
37
+
If you need to create a new client certificate, follow the steps in [set and retrieve a certificate from Azure Key Vault](/azure/key-vault/certificates/quick-create-portal). Note the certificate thumbprint as it will be required to deploy the template in the next step.
38
38
39
39
## Deploy Dedicated Host resources and configure access to Service Fabric Resource Provider
40
40
@@ -63,7 +63,7 @@ Create a dedicated host group and add a role assignment to the host group with t
63
63
> * Each fault domain needs a dedicated host to be placed in it and Service Fabric managed clusters require five fault domains. Therefore, at least five dedicated hosts should be present in each dedicated host group.
64
64
65
65
66
-
3. The [sample ARM deployment template for Dedicated Host Group](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/SF-Managed-Standard-SKU-2-NT-ADH) used in the previous step also adds a role assignment to the host group with contributor access. For more information on Azure roles, see [Azure built-in roles - Azure RBAC](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles#all). This role assignment is defined in the resources section of template with Principal ID determined from the first step and a role definition ID.
66
+
3. The [sample ARM deployment template for Dedicated Host Group](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/SF-Managed-Standard-SKU-2-NT-ADH) used in the previous step also adds a role assignment to the host group with contributor access. For more information on Azure roles, see [Azure built-in roles - Azure RBAC](/azure/role-based-access-control/built-in-roles#all). This role assignment is defined in the resources section of template with Principal ID determined from the first step and a role definition ID.
67
67
68
68
```JSON
69
69
"variables": {
@@ -108,7 +108,7 @@ Create an Azure Service Fabric managed cluster with node type(s) configured to r
108
108
* Cluster Name: Enter a unique name for your cluster, such as mysfcluster.
109
109
* Admin Username: Enter a name for the admin to be used for RDP on the underlying VMs in the cluster.
110
110
* Admin Password: Enter a password for the admin to be used for RDP on the underlying VMs in the cluster.
111
-
* Client Certificate Thumbprint: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](https://docs.microsoft.com/azure/key-vault/certificates/quick-create-portal) to create a self-signed certificate.
111
+
* Client Certificate Thumbprint: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](/azure/key-vault/certificates/quick-create-portal) to create a self-signed certificate.
112
112
* Node Type Name: Enter a unique name for your node type, such as nt1.
113
113
114
114
3. Deploy an ARM template through one of the methods below:
@@ -117,7 +117,7 @@ Create an Azure Service Fabric managed cluster with node type(s) configured to r
117
117
118
118
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-Samples%2Fservice-fabric-cluster-templates%2Fmaster%2FSF-Managed-Standard-SKU-2-NT-ADH%2Fazuredeploy.json)
119
119
120
-
* ARM PowerShell cmdlets: [New-AzResourceGroupDeployment (Az.Resources)](https://docs.microsoft.com/powershell/module/az.resources/new-azresourcegroupdeployment). Store the paths of your ARM template and parameter files in variables, then deploy the template.
120
+
* ARM PowerShell cmdlets: [New-AzResourceGroupDeployment (Az.Resources)](/powershell/module/az.resources/new-azresourcegroupdeployment). Store the paths of your ARM template and parameter files in variables, then deploy the template.
121
121
122
122
```powershell
123
123
$templateFilePath = "<full path to azuredeploy.json>"
Copy file name to clipboardExpand all lines: articles/service-fabric/how-to-managed-cluster-ephemeral-os-disks.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,14 +20,14 @@ Ephemeral OS disks work well where applications are tolerant of individual VM fa
20
20
This article describes how to create a Service Fabric managed cluster node types specifically with Ephemeral OS disks using an Azure Resource Manager template (ARM template).
21
21
22
22
## Prerequisites
23
-
This guide builds upon the managed cluster quick start guide: [Deploy a Service Fabric managed cluster using Azure Resource Manager](https://docs.microsoft.com/azure/service-fabric/quickstart-managed-cluster-template)
23
+
This guide builds upon the managed cluster quick start guide: [Deploy a Service Fabric managed cluster using Azure Resource Manager](/azure/service-fabric/quickstart-managed-cluster-template)
24
24
25
25
Before you begin:
26
26
27
27
* If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free)
28
28
* Retrieve a managed cluster ARM template. Sample Resource Manager templates are available in the [Azure samples on GitHub](https://github.com/Azure-Samples/service-fabric-cluster-templates). These templates can be used as a starting point for your cluster template.
29
29
* Ephemeral OS disks are supported both for primary and secondary node type. This guide shows how to deploy a Standard SKU cluster with two node types - a primary and a secondary node type, which uses Ephemeral OS disk.
30
-
* Ephemeral OS disks aren't supported for every SKU. VM sizes such as DSv1, DSv2, DSv3, Esv3, Fs, FsV2, GS, M, Mdsv2, Bs, Dav4, Eav4 supports Ephemeral OS disks. Ensure the SKU with which you want to deploy supports Ephemeral OS disk. For more information on individual SKU, see [supported VM SKU](https://docs.microsoft.com/azure/virtual-machines/dv3-dsv3-series) and navigate to the desired SKU on left side pane.
30
+
* Ephemeral OS disks aren't supported for every SKU. VM sizes such as DSv1, DSv2, DSv3, Esv3, Fs, FsV2, GS, M, Mdsv2, Bs, Dav4, Eav4 supports Ephemeral OS disks. Ensure the SKU with which you want to deploy supports Ephemeral OS disk. For more information on individual SKU, see [supported VM SKU](/azure/virtual-machines/dv3-dsv3-series) and navigate to the desired SKU on left side pane.
31
31
* Ephemeral OS disks in Service Fabric are placed in the space for temporary disks for the VM SKU. Ensure the VM SKU you're using has more than 127 GiB of temporary disk space to place Ephemeral OS disk.
32
32
33
33
## Review the template
@@ -37,7 +37,7 @@ The template used in this guide is from [Azure Samples - Service Fabric cluster
37
37
## Create a client certificate
38
38
Service Fabric managed clusters use a client certificate as a key for access control. If you already have a client certificate that you would like to use for access control to your cluster, you can skip this step.
39
39
40
-
If you need to create a new client certificate, follow the steps in [set and retrieve a certificate from Azure Key Vault](https://docs.microsoft.com/azure/key-vault/certificates/quick-create-portal). Note the certificate thumbprint as it will be required to deploy the template in the next step.
40
+
If you need to create a new client certificate, follow the steps in [set and retrieve a certificate from Azure Key Vault](/azure/key-vault/certificates/quick-create-portal). Note the certificate thumbprint as it will be required to deploy the template in the next step.
41
41
42
42
## Deploy the template
43
43
@@ -51,7 +51,7 @@ If you need to create a new client certificate, follow the steps in [set and ret
51
51
* Cluster Name: Enter a unique name for your cluster, such as mysfcluster.
52
52
* Admin Username: Enter a name for the admin to be used for RDP on the underlying VMs in the cluster.
53
53
* Admin Password: Enter a password for the admin to be used for RDP on the underlying VMs in the cluster.
54
-
* Client Certificate Thumbprint: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](https://docs.microsoft.com/azure/key-vault/certificates/quick-create-portal) to create a self-signed certificate.
54
+
* Client Certificate Thumbprint: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](/azure/key-vault/certificates/quick-create-portal) to create a self-signed certificate.
55
55
* Node Type Name: Enter a unique name for your node type, such as nt1.
56
56
57
57
@@ -62,7 +62,7 @@ If you need to create a new client certificate, follow the steps in [set and ret
62
62
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-Samples%2Fservice-fabric-cluster-templates%2Fmaster%2FSF-Managed-Standard-SKU-2-NT-Ephemeral%2Fazuredeploy.json)
63
63
64
64
65
-
* ARM PowerShell cmdlets: [New-AzResourceGroupDeployment (Az.Resources)](https://docs.microsoft.com/powershell/module/az.resources/new-azresourcegroupdeployment). Store the paths of your ARM template and parameter files in variables, then deploy the template.
65
+
* ARM PowerShell cmdlets: [New-AzResourceGroupDeployment (Az.Resources)](/powershell/module/az.resources/new-azresourcegroupdeployment). Store the paths of your ARM template and parameter files in variables, then deploy the template.
66
66
67
67
```powershell
68
68
$templateFilePath = "<full path to azuredeploy.json>"
0 commit comments