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
| Use HTTP-Only Cookie |**No**|**Yes** allows Application Proxy to include the HTTPOnly flag in HTTP response headers. This flag provides additional security benefits, for example, it prevents client-side scripting (CSS) from copying or modifying the cookies.<br></br><br></br>Before we supported the HTTP-Only setting, Application Proxy encrypted and transmitted cookies over a secured TLS channel to protect against modification. | Use **Yes** because of the additional security benefits.<br></br><br></br>Use **No** for clients or user agents that do require access to the session cookie. For example, use **No** for an RDP or MTSC client that connects to a Remote Desktop Gateway server through Application Proxy.|
27
-
| Use Secure Cookie |**No**|**Yes** allows Application Proxy to include the Secure flag in HTTP response headers. Secure Cookies enhances security by transmitting cookies over a TLS secured channel such as HTTPS. This prevents cookies from being observed by unauthorized parties due to the transmission of the cookie in clear text. | Use **Yes** because of the additional security benefits.|
27
+
| Use Secure Cookie |**Yes**|**Yes** allows Application Proxy to include the Secure flag in HTTP response headers. Secure Cookies enhances security by transmitting cookies over a TLS secured channel such as HTTPS. This prevents cookies from being observed by unauthorized parties due to the transmission of the cookie in clear text. | Use **Yes** because of the additional security benefits.|
28
28
| Use Persistent Cookie |**No**|**Yes** allows Application Proxy to set its access cookies to not expire when the web browser is closed. The persistence lasts until the access token expires, or until the user manually deletes the persistent cookies. | Use **No** because of the security risk associated with keeping users authenticated.<br></br><br></br>We suggest only using **Yes** for older applications that can't share cookies between processes. It's better to update your application to handle sharing cookies between processes instead of using persistent cookies. For example, you might need persistent cookies to allow a user to open Office documents in explorer view from a SharePoint site. Without persistent cookies, this operation might fail if the access cookies aren't shared between the browser, the explorer process, and the Office process. |
Copy file name to clipboardExpand all lines: articles/active-directory/external-identities/user-properties.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,6 +109,8 @@ It's possible to convert UserType from Member to Guest and vice-versa by editing
109
109
110
110
Guest users have [default restricted directory permissions](../fundamentals/users-default-permissions.md). They can manage their own profile, change their own password, and retrieve some information about other users, groups, and apps. However, they can't read all directory information.
111
111
112
+
B2B guest users are not supported in Microsoft Teams shared channels. For access to shared channels see [B2B direct connect.](b2b-direct-connect-overview.md)
113
+
112
114
There may be cases where you want to give your guest users higher privileges. You can add a guest user to any role and even remove the default guest user restrictions in the directory to give a user the same privileges as members. It's possible to turn off the default limitations so that a guest user in the company directory has the same permissions as a member user. For more information, check out the [Restrict guest access permissions in Azure Active Directory](../enterprise-users/users-restrict-guest-permissions.md) article.
113
115
114
116
@@ -125,4 +127,4 @@ If a guest user accepts your invitation and they subsequently change their email
125
127
126
128
*[What is Azure AD B2B collaboration?](what-is-b2b.md)
127
129
*[B2B collaboration user tokens](user-token.md)
128
-
*[B2B collaboration user claims mapping](claims-mapping.md)
130
+
*[B2B collaboration user claims mapping](claims-mapping.md)
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/automate-provisioning-to-applications-introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Thousands of organizations are running Azure AD cloud-hosted services, with its
37
37
38
38
39
39
40
-
Use the following table to find content specific to your scenario. For example, if you want employee and contractor identities management from an HR system to Active Directory (AD) or Azure Active Directory (Azure AD), follow the link to *Connect identities with your system of record*.
40
+
Use the following table to find content specific to your scenario. For example, if you want employee and contractor identities management from an HR system to Active Directory Domain Services (AD DS) or Azure Active Directory (Azure AD), follow the link to *Connect identities with your system of record*.
41
41
42
42
| What | From | To | Read |
43
43
| - | - | - | - |
@@ -83,7 +83,7 @@ In this example, the organization has users spread across multiple on-premises H
1. MIM imports user information from each HR stem. MIM determines which users are needed for those employees in different directories. MIM provisions those identities in Active Directory.
86
+
1. MIM imports user information from each HR stem. MIM determines which users are needed for those employees in different directories. MIM provisions those identities in AD DS.
87
87
88
88
2. Azure AD Connect Sync then synchronizes those users and groups to Azure AD and provides users access to their resources.
This article presents solutions that enable you to:
23
23
24
24
* Connect identities with your system of record
25
-
* Synchronize identities between Active Directory (AD) and Azure Active Directory (Azure AD)
25
+
* Synchronize identities between Active Directory Domain Services (AD DS) and Azure Active Directory (Azure AD)
26
26
* Automate provisioning of users into non-Microsoft applications
27
27
28
28
## Connect identities with your system of record
@@ -31,17 +31,17 @@ In most designs, the human resources (HR) system is the source-of-authority for
31
31
32
32
### Synchronizing identities with cloud HR
33
33
34
-
The Azure AD provisioning service enables organizations to [bring identities from popular HR systems](../app-provisioning/what-is-hr-driven-provisioning.md) (examples: [Workday](../saas-apps/workday-inbound-tutorial.md) and [SuccessFactors](../saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)), into Azure AD directly, or into Active Directory Domain Services. This provisioning capability enables new hires to access the resources they need from the first day of work.
34
+
The Azure AD provisioning service enables organizations to [bring identities from popular HR systems](../app-provisioning/what-is-hr-driven-provisioning.md) (examples: [Workday](../saas-apps/workday-inbound-tutorial.md) and [SuccessFactors](../saas-apps/sap-successfactors-inbound-provisioning-cloud-only-tutorial.md)), into Azure AD directly, or into AD DS. This provisioning capability enables new hires to access the resources they need from the first day of work.
35
35
36
36
### On-premises HR + joining multiple data sources
37
37
38
38
To create a full user profile for an employee identity, organizations often merge information from multiple HR systems, databases, and other user data stores. MIM provides a rich set of [connectors](https://learn.microsoft.com/microsoft-identity-manager/supported-management-agents) and integration solutions interoperating with heterogeneous platforms.
39
39
40
-
MIM offers [rule extension](/previous-versions/windows/desktop/forefront-2010/ms698810(v=vs.100)?redirectedfrom=MSDN) and [workflow capabilities](https://microsoft.github.io/MIMWAL/) features for advanced scenarios requiring data transformation and consolidation from multiple sources. These connectors, rule extensions, and workflow capabilities enable organizations to aggregate user data in the MIM metaverse to form a single identity for each user. The identity can be [provisioned into downstream systems](/microsoft-identity-manager/microsoft-identity-manager-2016-supported-platforms) such as Active Directory Domain Services.
40
+
MIM offers [rule extension](/previous-versions/windows/desktop/forefront-2010/ms698810(v=vs.100)?redirectedfrom=MSDN) and [workflow capabilities](https://microsoft.github.io/MIMWAL/) features for advanced scenarios requiring data transformation and consolidation from multiple sources. These connectors, rule extensions, and workflow capabilities enable organizations to aggregate user data in the MIM metaverse to form a single identity for each user. The identity can be [provisioned into downstream systems](/microsoft-identity-manager/microsoft-identity-manager-2016-supported-platforms) such as AD DS.
41
41
42
42
43
43
44
-
## Synchronize identities between Active Directory and Azure AD
44
+
## Synchronize identities between Active Directory Domain Services (AD DS) and Azure AD
45
45
46
46
As customers move applications to the cloud, and integrate with Azure AD, users often need accounts in Azure AD, and AD to access the applications for their work. Here are five common scenarios in which objects need to be synchronized between AD and Azure AD.
47
47
@@ -67,10 +67,10 @@ As customers transition identity management to the cloud, more users and groups
Copy file name to clipboardExpand all lines: articles/app-service/reference-app-settings.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
@@ -334,7 +334,7 @@ For more information on custom containers, see [Run a custom container in Azure]
334
334
335
335
| Setting name| Description | Example |
336
336
|-|-|-|
337
-
|`WEBSITES_ENABLE_APP_SERVICE_STORAGE`| Set to `true` to enable the `/home` directory to be shared across scaled instances. The default is `false` for custom containers. ||
337
+
|`WEBSITES_ENABLE_APP_SERVICE_STORAGE`| Set to `true` to enable the `/home` directory to be shared across scaled instances. The default is `true` for custom containers. ||
338
338
|`WEBSITES_CONTAINER_START_TIME_LIMIT`| Amount of time in seconds to wait for the container to complete start-up before restarting the container. Default is `230`. You can increase it up to the maximum of `1800`. ||
339
339
|`DOCKER_REGISTRY_SERVER_URL`| URL of the registry server, when running a custom container in App Service. For security, this variable is not passed on to the container. |`https://<server-name>.azurecr.io`|
340
340
|`DOCKER_REGISTRY_SERVER_USERNAME`| Username to authenticate with the registry server at `DOCKER_REGISTRY_SERVER_URL`. For security, this variable is not passed on to the container. ||
0 commit comments