Skip to content

Commit 4ca8107

Browse files
authored
Merge pull request #76805 from MicrosoftDocs/master
5/15 AM Publish
2 parents b0df8f8 + 54943d1 commit 4ca8107

File tree

77 files changed

+874
-883
lines changed

Some content is hidden

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

77 files changed

+874
-883
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23059,6 +23059,11 @@
2305923059
"redirect_url": "/azure/storage/blobs/storage-dotnet-shared-access-signature-part-2",
2306023060
"redirect_document_id": true
2306123061
},
23062+
{
23063+
"source_path": "articles/storage/blobs/storage-dotnet-shared-access-signature-part-2.md",
23064+
"redirect_url": "/azure/storage/common/storage-dotnet-shared-access-signature-part-1",
23065+
"redirect_document_id": false
23066+
},
2306223067
{
2306323068
"source_path": "articles/storage/storage-e2e-troubleshooting.md",
2306423069
"redirect_url": "/azure/storage/common/storage-e2e-troubleshooting",

articles/active-directory/b2b/tutorial-bulk-invite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ foreach ($email in $invitations)
105105
{New-AzureADMSInvitation `
106106
-InvitedUserEmailAddress $email.InvitedUserEmailAddress `
107107
-InvitedUserDisplayName $email.Name `
108-
-InviteRedirectUrl https://myapps.azure.com `
108+
-InviteRedirectUrl https://myapps.microsoft.com `
109109
-InvitedUserMessageInfo $messageInfo `
110110
-SendInvitationMessage $true
111111
}

articles/active-directory/develop/quickstart-v2-windows-desktop.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ In this quickstart, you'll learn how to write a Windows desktop .NET (WPF) appli
6767
6868
#### Step 2: Download your Visual Studio project
6969

70-
[Download the Visual Studio project](https://github.com/Azure-Samples/active-directory-dotnet-desktop-msgraph-v2/archive/msal3x.zip)
70+
[Download the Visual Studio project](https://github.com/Azure-Samples/active-directory-dotnet-desktop-msgraph-v2/archive/msal3x.zip) ([View Project on Github](https://github.com/Azure-Samples/active-directory-dotnet-desktop-msgraph-v2/))
7171

7272
#### Step 3: Configure your Visual Studio project
7373

articles/active-directory/hybrid/how-to-connect-device-writeback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ ms.collection: M365-identity-device-management
2727
2828
The following documentation provides information on how to enable the device writeback feature in Azure AD Connect. Device Writeback is used in the following scenarios:
2929

30-
* Enable [Windows Hello for Business using hybrid certificate trust deployment](https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#device-registration)
30+
* Enable [Windows Hello for Business using hybrid certificate trust deployment](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-hybrid-cert-trust-prereqs#device-registration)
3131
* Enable conditional access based on devices to ADFS (2012 R2 or higher) protected applications (relying party trusts).
3232

3333
This provides additional security and assurance that access to applications is granted only to trusted devices. For more information on conditional access, see [Managing Risk with Conditional Access](../active-directory-conditional-access-azure-portal.md) and [Setting up On-premises Conditional Access using Azure Active Directory Device Registration](../../active-directory/active-directory-device-registration-on-premises-setup.md).

articles/active-directory/hybrid/how-to-connect-health-agent-install.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following table is a list of requirements for using Azure AD Connect Health.
4040

4141
### Outbound connectivity to the Azure service endpoints
4242

43-
During installation and runtime, the agent requires connectivity to Azure AD Connect Health service endpoints. If outbound connectivity is blocked using Firewalls, make sure that the following URLs are not blocked by default. Do not disable security monitoring or inspection of these URLs, but allow them as you would other internet traffic. They permit communication with Azure AD Connect Health service endpoints. Read more about [check outbound connectivity](https://docs.microsoft.com/azure/load-balancer/load-balancer-outbound-connections)
43+
During installation and runtime, the agent requires connectivity to Azure AD Connect Health service endpoints. If outbound connectivity is blocked using Firewalls, make sure that the following URLs are not blocked by default. Do not disable security monitoring or inspection of these URLs, but allow them as you would other internet traffic. They permit communication with Azure AD Connect Health service endpoints. Learn how to [check outbound connectivity with Test-AzureADConnectHealthConnectivity](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-health-agent-install#test-connectivity-to-azure-ad-connect-health-service).
4444

4545
| Domain Environment | Required Azure service endpoints |
4646
| --- | --- |

articles/active-directory/manage-apps/end-user-experiences.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: app-mgmt
99
ms.workload: identity
1010
ms.topic: conceptual
11-
ms.date: 11/09/2018
11+
ms.date: 05/03/2019
1212
ms.author: celested
1313
ms.reviewer: arvindh
1414
ms.collection: M365-identity-device-management
@@ -48,7 +48,9 @@ Most federated applications that support SAML 2.0, WS-Federation, or OpenID conn
4848
## Direct sign-on links
4949
Azure AD also supports direct single sign-on links to individual applications that support password-based single sign-on, linked single sign-on, and any form of federated single sign-on.
5050

51-
These links are specifically crafted URLs that send a user through the Azure AD sign-in process for a specific application without requiring the user launch them from the Azure AD access panel or Office 365. These **User access URLs** can be found under the properties of available enterprise applications under Azure Active Directory in the Azure portal.
51+
These links are specifically crafted URLs that send a user through the Azure AD sign-in process for a specific application without requiring the user launch them from the Azure AD access panel or Office 365. These **User access URLs** can be found under the properties of available enterprise applications. In the Azure portal, select **Azure Active Directory** > **Enterprise applications**. Select the application, and then select **Properties**.
52+
53+
![Example of the User access URL in Twitter properties](media/end-user-experiences/direct-sign-on-link.png)
5254

5355
These links can be copied and pasted anywhere you want to provide a sign-in link to the selected application. This could be in an email, or in any custom web-based portal that you have set up for user application access. Here's an example of an Azure AD direct single sign-on URL for Twitter:
5456

54.8 KB
Loading

articles/active-directory/saas-apps/workspotcontrol-tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -236,12 +236,12 @@ To enable Azure AD users to sign in to Workspot Control, they must be provisione
236236

237237
In this section, we test our Azure AD single sign-on configuration through *Access Panel*.
238238

239-
When you click the **Workspot Control** tile in Access Panel, you should be automatically signed in to the Workspot Control for which you set up SSO. For more information, see [Introduction to the Access Panel](https://docs.microsoft.com/en-us/azure/active-directory/user-help/my-apps-portal-end-user-access).
239+
When you click the **Workspot Control** tile in Access Panel, you should be automatically signed in to the Workspot Control for which you set up SSO. For more information, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/user-help/my-apps-portal-end-user-access).
240240

241241
## Additional resources
242242

243-
- [Tutorials for integrating SaaS applications with Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/tutorial-list)
243+
- [Tutorials for integrating SaaS applications with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/saas-apps/tutorial-list)
244244

245-
- [Single sign-on to applications in Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/what-is-single-sign-on)
245+
- [Single sign-on to applications in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
246246

247247
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)

articles/aks/limit-egress-traffic.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ In AKS, there are two sets of ports and addresses:
5959
* The [optional recommended addresses and ports for AKS clusters](#optional-recommended-addresses-and-ports-for-aks-clusters) aren't required for all scenarios, but integration with other services such as Azure Monitor won't work correctly. Review this list of optional ports and FQDNs, and authorize any of the services and components used in your AKS cluster.
6060

6161
> [!NOTE]
62-
> Limiting egress traffic only works on new AKS clusters created after you enable the feature flag registration. You can't limit egress traffic on an existing AKS cluster created before the feature flag was registered.
62+
> Limiting egress traffic only works on new AKS clusters created after you enable the feature flag registration. For existing clusters, [perform a cluster upgrade operation][aks-upgrade] using the `az aks upgrade` command before you limit the egress traffic.
6363
6464
## Required ports and addresses for AKS clusters
6565

@@ -115,3 +115,4 @@ In this article, you learned what ports and addresses to allow if you restrict e
115115
[az-feature-register]: /cli/azure/feature#az-feature-register
116116
[az-feature-list]: /cli/azure/feature#az-feature-list
117117
[az-provider-register]: /cli/azure/provider#az-provider-register
118+
[aks-upgrade]: upgrade-cluster.md

articles/aks/support-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ Preview features or feature-flag features aren't meant for production. Ongoing c
144144

145145
Features in public preview are fall under 'best effort' support as these features are in preview and not meant for production and are supported by the AKS technical support teams during business hours only. For additional information please see:
146146

147-
* [Azure Support FAQ](https://azure.microsoft.com/en-us/support/faq/)
147+
* [Azure Support FAQ](https://azure.microsoft.com/support/faq/)
148148

149149
> [!NOTE]
150150
> Preview features take effect at the Azure *subscription* level. Don't install preview features on a production subscription. On a production subscription, preview features can change default API behavior and affect regular operations.

0 commit comments

Comments
 (0)