Docs update tracker

Updates from: 09/19/2023 01:17:14

Service	Microsoft Docs article	Related commit history on GitHub	Change details
active-directory	Application Provisioning Quarantine Status	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md	Previously updated : 10/06/2022 Last updated : 09/15/2023 While in quarantine: There are three ways to check whether an application is in quarantine: -- In the Azure portal, navigate to Azure Active Directory > Enterprise applications > <application name> > Provisioning and review the progress bar for a quarantine message. +- In the Microsoft Entra admin center, navigate to Identity > Applications > Enterprise applications > <application name> > Provisioning and review the progress bar for a quarantine message. ![Provisioning status bar showing quarantine status](./media/application-provisioning-quarantine-status/progress-bar-quarantined.png) -- In the Azure portal, navigate to Azure Active Directory > Audit Logs > filter on Activity: Quarantine and review the quarantine history. The view in the progress bar as described above shows whether provisioning is currently in quarantine. The audit logs show the quarantine history for an application. +- In the Microsoft Entra admin center, navigate to Identity > Monitoring & health > Audit Logs > filter on Activity: Quarantine and review the quarantine history. The view in the progress bar as described above shows whether provisioning is currently in quarantine. The audit logs show the quarantine history for an application. - Use the Microsoft Graph request [Get synchronizationJob](/graph/api/synchronization-synchronizationjob-get?tabs=http&view=graph-rest-beta&preserve-view=true) to programmatically get the status of the provisioning job: Below are the common reasons your application may go into quarantine \|\|\| \|SCIM Compliance issue: An HTTP/404 Not Found response was returned rather than the expected HTTP/200 OK response. In this case, the Azure AD provisioning service has made a request to the target application and received an unexpected response.\|Check the admin credentials section. See if the application requires specifying the tenant URL and that the URL is correct. If you don't see an issue, contact the application developer to ensure that their service is SCIM-compliant. https://tools.ietf.org/html/rfc7644#section-3.4.2 \| \|Invalid credentials: When attempting to authorize, access to the target application, we received a response from the target application that indicates the credentials provided are invalid.\|Navigate to the admin credentials section of the provisioning configuration UI and authorize access again with valid credentials. If the application is in the gallery, review the application configuration tutorial for anymore required steps.\| -\|Duplicate roles: Roles imported from certain applications like Salesforce and Zendesk must be unique. \|Navigate to the application [manifest](../develop/reference-app-manifest.md) in the Azure portal and remove the duplicate role.\| +\|Duplicate roles: Roles imported from certain applications like Salesforce and Zendesk must be unique. \|Navigate to the application [manifest](../develop/reference-app-manifest.md) in the Microsoft Entra admin center and remove the duplicate role.\| A Microsoft Graph request to get the status of the provisioning job shows the following reason for quarantine: - `EncounteredQuarantineException` indicates that invalid credentials were provided. The provisioning service is unable to establish a connection between the source system and the target system. First, resolve the issue that caused the application to be placed in quarantine. After you've resolved the issue, restart the provisioning job. Certain changes to the application's provisioning settings, such as attribute mappings or scoping filters, will automatically restart provisioning for you. The progress bar on the application's Provisioning page indicates when provisioning last started. If you need to restart the provisioning job manually, use one of the following methods: -- Use the Azure portal to restart the provisioning job. On the application's Provisioning page, select Restart provisioning. This action fully restarts the provisioning service, which can take some time. A full initial cycle will run again, which clears escrows, removes the app from quarantine, and clears any watermarks. The service will then evaluate all the users in the source system again and determine if they are in scope for provisioning. This can be useful when your application is currently in quarantine, as this article discusses, or you need to make a change to your attribute mappings. Note that the initial cycle takes longer to complete than the typical incremental cycle due to the number of objects that need to be evaluated. You can learn more about the performance of initial and incremental cycles [here](application-provisioning-when-will-provisioning-finish-specific-user.md). +- Use the Microsoft Entra admin center to restart the provisioning job. On the application's Provisioning page, select Restart provisioning. This action fully restarts the provisioning service, which can take some time. A full initial cycle will run again, which clears escrows, removes the app from quarantine, and clears any watermarks. The service will then evaluate all the users in the source system again and determine if they are in scope for provisioning. This can be useful when your application is currently in quarantine, as this article discusses, or you need to make a change to your attribute mappings. Note that the initial cycle takes longer to complete than the typical incremental cycle due to the number of objects that need to be evaluated. You can learn more about the performance of initial and incremental cycles [here](application-provisioning-when-will-provisioning-finish-specific-user.md). - Use Microsoft Graph to [restart the provisioning job](/graph/api/synchronization-synchronizationjob-restart?tabs=http&view=graph-rest-beta&preserve-view=true). You'll have full control over what you restart. You can choose to clear escrows (to restart the escrow counter that accrues toward quarantine status), clear quarantine (to remove the application from quarantine), or clear watermarks. Use the following request:
active-directory	Application Provisioning When Will Provisioning Finish Specific User	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md	Previously updated : 06/29/2023 Last updated : 09/15/2023 When you first configure automatic provisioning, the Current Status section After a provisioning cycle is complete, the Statistics to date section shows the cumulative numbers of users and groups that have been provisioned to date, along with the completion date and duration of the last cycle. The Activity ID uniquely identifies the most recent provisioning cycle. The Job ID is a unique identifier for the provisioning job, and is specific to the app in your tenant. -The provisioning progress is viewed in the Azure portal at Azure Active Directory > Enterprise Apps > \[application name\] > Provisioning. +The provisioning progress is viewed in the Microsoft Entra admin center at Identity > Applications > Enterprise applications > \[application name\] > Provisioning. ![Provisioning page progress bar](./media/application-provisioning-when-will-provisioning-finish-specific-user/provisioning-progress-bar-section.png) The provisioning progress is viewed in the Azure portal at Azure Active Direct To see the provisioning status for a selected user, consult the [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context) in Azure AD. All operations run by the user provisioning service are recorded in the Azure AD provisioning logs. The logs include read and write operations made to the source and target systems. Associated user data related to read and write operations is also logged. -You can access the provisioning logs in the Azure portal by selecting Azure Active Directory > Enterprise Apps > Provisioning logs (preview) in the Activity section. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). +You can access the provisioning logs in the Microsoft Entra admin center by selecting Identity > Applications > Enterprise applications > Provisioning logs in the Activity** section. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). The provisioning logs record all the operations performed by the provisioning service, including: The provisioning logs record all the operations performed by the provisioning se * Comparing the user objects between the system * Adding, updating, or disabling the user account in the target system based on the comparison -For more information on how to read the provisioning logs in the Azure portal, see [provisioning reporting guide](check-status-user-account-provisioning.md). +For more information on how to read the provisioning logs in the Microsoft Entra admin center, see [provisioning reporting guide](check-status-user-account-provisioning.md). ## How long will it take to provision users? When you're using automatic user provisioning with an application, there are some things to keep in mind. First, Azure AD automatically provisions and updates user accounts in an app based on things like [user and group assignment](../manage-apps/assign-user-or-group-access-portal.md). The sync happens at a regularly scheduled time interval, typically every 40 minutes.
active-directory	Check Status User Account Provisioning	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/check-status-user-account-provisioning.md	Previously updated : 05/05/2023 Last updated : 09/15/2023 This article describes how to check the status of provisioning jobs after they h ## Overview -Provisioning connectors are set up and configured using the [Azure portal](https://portal.azure.com), by following the [provided documentation](../saas-apps/tutorial-list.md) for the supported application. When the connector is configured and running, provisioning jobs can be reported using the following methods: +Provisioning connectors are set up and configured using the [Microsoft Entra admin center](https://entra.microsoft.com), by following the [provided documentation](../saas-apps/tutorial-list.md) for the supported application. When the connector is configured and running, provisioning jobs can be reported using the following methods: -- The [Azure portal](https://portal.azure.com) +- The [Microsoft Entra admin center](https://entra.microsoft.com) - Streaming the provisioning logs into [Azure Monitor](../app-provisioning/application-provisioning-log-analytics.md). This method allows for extended data retention and building custom dashboards, alerts, and queries. This article uses the following terms: * Source System - The repository of users that the Azure AD provisioning service synchronizes from. Azure Active Directory is the source system for most preintegrated provisioning connectors, however there are some exceptions (example: Workday Inbound Synchronization). * Target System - The repository of users where the Azure AD provisioning service synchronizes. The repository is typically a SaaS application, such as Salesforce, ServiceNow, G Suite, and Dropbox for Business. In some cases the repository can be an on-premises system such as Active Directory, such as Workday Inbound Synchronization to Active Directory. -## Getting provisioning reports from the Azure portal +## Getting provisioning reports from the Microsoft Entra admin center -To get provisioning report information for a given application, start by launching the [Azure portal](https://portal.azure.com) and Azure Active Directory > Enterprise Apps > Provisioning logs in the Activity section. You can also browse to the Enterprise Application for which provisioning is configured. For example, if you're provisioning users to LinkedIn Elevate, the navigation path to the application details is: +To get provisioning report information for a given application: +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). +1. Browse to Identity > Applications > Enterprise applications. +1. Select Provisioning logs in the Activity section. You can also browse to the Enterprise Application for which provisioning is configured. For example, if you're provisioning users to LinkedIn Elevate, the navigation path to the application details is: -Azure Active Directory > Enterprise Applications > All applications > LinkedIn Elevate +Identity > Applications > Enterprise applications > All applications > LinkedIn Elevate From the all applications area, you access both the provisioning progress bar and provisioning logs. The Current Status should be the first place admins look to check on the ope ## Provisioning logs -All activities performed by the provisioning service are recorded in the Azure AD [provisioning logs](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). You can access the provisioning logs in the Azure portal by selecting Azure Active Directory > Enterprise Apps > Provisioning logs in the Activity section. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see [Provisioning logs](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). +All activities performed by the provisioning service are recorded in the Azure AD [provisioning logs](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). You can access the provisioning logs in the Microsoft Entra admin center. You can search the provisioning data based on the name of the user or the identifier in either the source system or the target system. For details, see [Provisioning logs](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). ## Troubleshooting
active-directory	Configure Automatic User Provisioning Portal	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/configure-automatic-user-provisioning-portal.md	Previously updated : 05/02/2023 Last updated : 09/15/2023 -# Managing user account provisioning for enterprise apps in the Azure portal +# Managing user account provisioning for enterprise apps in the Microsoft Entra admin center This article describes the general steps for managing automatic user account provisioning and deprovisioning for applications that support it. User account provisioning is the act of creating, updating, and/or disabling user account records in an applicationΓÇÖs local user profile store. Most cloud and SaaS applications store the role and permissions in the user's own local user profile store. The presence of such a user record in the user's local store is required for single sign-on and access to work. To learn more about automatic user account provisioning, see [Automate User Provisioning and Deprovisioning to SaaS Applications with Azure Active Directory](user-provisioning.md). This article describes the general steps for managing automatic user account pro [!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)] -Use the Azure portal to view and manage all applications that are configured for single sign-on in a directory. Enterprise apps are apps that are deployed and used within your organization. Follow these steps to view and manage your enterprise applications: +Use the Microsoft Entra admin center to view and manage all applications that are configured for single sign-on in a directory. Enterprise apps are apps that are deployed and used within your organization. Follow these steps to view and manage your enterprise applications: -1. Sign in to the [Azure portal](https://portal.azure.com). -1. Browse to Azure Active Directory > Enterprise applications. +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). +1. Browse to Identity > Applications > Enterprise applications. 1. A list of all configured apps is shown, including apps that were added from the gallery. 1. Select any app to load its resource pane, where you can view reports and manage app settings. 1. Select Provisioning to manage user account provisioning settings for the selected app.
active-directory	Customize Application Attributes	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/customize-application-attributes.md	Previously updated : 03/29/2023 Last updated : 09/15/2023 # Tutorial - Customize user provisioning attribute-mappings for SaaS applications in Azure Active Directory -Microsoft Azure AD provides support for user provisioning to third-party SaaS applications such as Salesforce, G Suite and others. If you enable user provisioning for a third-party SaaS application, the Azure portal controls its attribute values through attribute-mappings. +Microsoft Azure AD provides support for user provisioning to third-party SaaS applications such as Salesforce, G Suite and others. If you enable user provisioning for a third-party SaaS application, the Microsoft Entra admin center controls its attribute values through attribute-mappings. Before you get started, make sure you're familiar with app management and single sign-on (SSO) concepts. Check out the following links: - [Quickstart Series on App Management in Azure AD](../manage-apps/view-applications-portal.md) You can customize the default attribute-mappings according to your business need Follow these steps to access the Mappings feature of user provisioning: -1. Sign in to the [Azure portal](https://portal.azure.com). -1. Browse to Azure Active Directory > Enterprise applications. +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). +1. Browse to Identity > Applications > Enterprise applications. 1. A list of all configured apps is shown, including apps that were added from the gallery. 1. Select any app to load its app management pane, where you can view reports and manage app settings. 1. Select Provisioning to manage user account provisioning settings for the selected app. The attributes provisioned as part of Group objects can be customized in the sam The user attributes supported for a given application are preconfigured. Most application's user management APIs don't support schema discovery. So, the Azure AD provisioning service isn't able to dynamically generate the list of supported attributes by making calls to the application. -However, some applications support custom attributes, and the Azure AD provisioning service can read and write to custom attributes. To enter their definitions into the Azure portal, select the Show advanced options check box at the bottom of the Attribute Mapping screen, and then select Edit attribute list for your app. +However, some applications support custom attributes, and the Azure AD provisioning service can read and write to custom attributes. To enter their definitions into the Microsoft Entra admin center, select the Show advanced options check box at the bottom of the Attribute Mapping screen, and then select Edit attribute list for your app. Applications and systems that support customization of the attribute list include: Applications and systems that support customization of the attribute list includ > [!NOTE] -> Editing the list of supported attributes is only recommended for administrators who have customized the schema of their applications and systems, and have first-hand knowledge of how their custom attributes have been defined or if a source attribute isn't automatically displayed in the Azure portal UI. This sometimes requires familiarity with the APIs and developer tools provided by an application or system. The ability to edit the list of supported attributes is locked down by default, but customers can enable the capability by navigating to the following URL: https://portal.azure.com/?Microsoft_AAD_Connect_Provisioning_forceSchemaEditorEnabled=true . You can then navigate to your application to view the [attribute list](#editing-the-list-of-supported-attributes). +> Editing the list of supported attributes is only recommended for administrators who have customized the schema of their applications and systems, and have first-hand knowledge of how their custom attributes have been defined or if a source attribute isn't automatically displayed in the Microsoft Entra admin center UI. This sometimes requires familiarity with the APIs and developer tools provided by an application or system. The ability to edit the list of supported attributes is locked down by default, but customers can enable the capability by navigating to the following URL: https://portal.azure.com/?Microsoft_AAD_Connect_Provisioning_forceSchemaEditorEnabled=true . You can then navigate to your application to view the [attribute list](#editing-the-list-of-supported-attributes). > [!NOTE] > When a directory extension attribute in Azure AD doesn't show up automatically in your attribute mapping drop-down, you can manually add it to the "Azure AD attribute list". When manually adding Azure AD directory extension attributes to your provisioning app, note that directory extension attribute names are case-sensitive. For example: If you have a directory extension attribute named `extension_53c9e2c0exxxxxxxxxxxxxxxx_acmeCostCenter`, make sure you enter it in the same format as defined in the directory. Provisioning multi-valued directory extension attributes is not supported. When you're editing the list of supported attributes, the following properties a - Multi-value? - Whether the attribute supports multiple values. - Exact case? - Whether the attributes values are evaluated in a case-sensitive way. - API Expression - Don't use, unless instructed to do so by the documentation for a specific provisioning connector (such as Workday).-- Referenced Object Attribute - If it's a Reference type attribute, then this menu lets you select the table and attribute in the target application that contains the value associated with the attribute. For example, if you have an attribute named "Department" whose stored value references an object in a separate "Departments" table, you would select "Departments.Name". The reference tables and the primary ID fields supported for a given application are preconfigured and can't be edited using the Azure portal. However, you can edit them using the [Microsoft Graph API](/graph/api/resources/synchronization-configure-with-custom-target-attributes). +- Referenced Object Attribute - If it's a Reference type attribute, then this menu lets you select the table and attribute in the target application that contains the value associated with the attribute. For example, if you have an attribute named "Department" whose stored value references an object in a separate "Departments" table, you would select "Departments.Name". The reference tables and the primary ID fields supported for a given application are preconfigured and can't be edited using the Microsoft Entra admin center. However, you can edit them using the [Microsoft Graph API](/graph/api/resources/synchronization-configure-with-custom-target-attributes). #### Provisioning a custom extension attribute to a SCIM compliant application The SCIM RFC defines a core user and group schema, while also allowing for extensions to the schema to meet your application's needs. To add a custom attribute to a SCIM application: - 1. Sign in to the [Azure portal](https://portal.azure.com), select Enterprise Applications, select your application, and then select Provisioning. - 2. Under Mappings, select the object (user or group) for which you'd like to add a custom attribute. - 3. At the bottom of the page, select Show advanced options. - 4. Select Edit attribute list for AppName. - 5. At the bottom of the attribute list, enter information about the custom attribute in the fields provided. Then select Add Attribute. + 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). + 1. Browse to Identity > Applications > Enterprise applications. + 1. Select your application, and then select Provisioning. + 1. Under Mappings, select the object (user or group) for which you'd like to add a custom attribute. + 1. At the bottom of the page, select Show advanced options. + 1. Select Edit attribute list for AppName. + 1. At the bottom of the attribute list, enter information about the custom attribute in the fields provided. Then select Add Attribute. For SCIM applications, the attribute name must follow the pattern shown in the example. The "CustomExtensionName" and "CustomAttribute" can be customized per your application's requirements, for example: urn:ietf:params:scim:schemas:extension:CustomExtensionName:2.0:User:CustomAttribute
active-directory	Define Conditional Rules For Provisioning User Accounts	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md	Previously updated : 05/05/2023 Last updated : 09/15/2023 zone_pivot_groups: app-provisioning-cross-tenant-synchronization Scoping filters are configured as part of the attribute mappings for each Azure [!INCLUDE [portal updates](~/articles/active-directory/includes/portal-update.md)] -1. Sign in to the [Azure portal](https://portal.azure.com). +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). ::: zone pivot="app-provisioning" -2. Go to the Azure Active Directory > Enterprise applications > All applications. + +2. Browse to Identity > Applications > Enterprise applications > All applications. 3. Select the application for which you have configured automatic provisioning: for example, "ServiceNow".+ ::: zone-end ::: zone pivot="cross-tenant-synchronization" -2. Go to Azure Active Directory > Cross-tenant Synchronization > Configurations + +2. Browse to Identity > External Identities > Cross-tenant Synchronization > Configurations 3. Select your configuration.+ ::: zone-end 4. Select the Provisioning tab. ::: zone pivot="app-provisioning"+ 5. In the Mappings section, select the mapping that you want to configure a scoping filter for: for example, "Synchronize Azure Active Directory Users to ServiceNow".+ ::: zone-end ::: zone pivot="cross-tenant-synchronization"+ 5. In the Mappings section, select the mapping that you want to configure a scoping filter for: for example, "Provision Azure Active Directory Users".+ ::: zone-end 6. Select the Source object scope menu.- 7. Select Add scoping filter.- 8. Define a clause by selecting a source Attribute Name, an Operator, and an Attribute Value to match against. The following operators are supported: a. EQUALS. Clause returns "true" if the evaluated attribute matches the input string value exactly (case sensitive).
active-directory	Export Import Provisioning Configuration	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/export-import-provisioning-configuration.md	Previously updated : 05/12/2023 Last updated : 09/15/2023 In this article, you learn how to: -- Export and import your provisioning configuration from the Azure portal +- Export and import your provisioning configuration from the Microsoft Entra admin center - Export and import your provisioning configuration by using the Microsoft Graph API -## Export and import your provisioning configuration from the Azure portal +## Export and import your provisioning configuration from the Microsoft Entra admin center ### Export your provisioning configuration In this article, you learn how to: To export your configuration: -1. Sign in to the [Azure portal](https://portal.azure.com). -1. In the left navigation panel, select Azure Active Directory. -1. In the Azure Active Directory pane, select Enterprise applications and choose your application. +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Application Administrator](../roles/permissions-reference.md#application-administrator). +1. Browse to Identity > Applications > Enterprise applications and choose your application. 1. In the left navigation pane, select provisioning. From the provisioning configuration page, click on attribute mappings, then show advanced options, and finally review your schema. The schema editor opens. 1. Click on download in the command bar at the top of the page to download your schema. You can use the Microsoft Graph API and the Microsoft Graph Explorer to export y ### Step 1: Retrieve your Provisioning App Service Principal ID (Object ID) -1. Sign in to the [Azure portal](https://portal.azure.com), and navigate to the Properties section of your provisioning application. For example, if you want to export your Workday to AD User Provisioning application mapping navigate to the Properties section of that app. +1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com), and navigate to the Properties section of your provisioning application. For example, if you want to export your Workday to AD User Provisioning application mapping navigate to the Properties section of that app. 1. In the Properties section of your provisioning app, copy the GUID value associated with the Object ID field. This value is also called the ServicePrincipalId of your App and it's used in Microsoft Graph Explorer operations. ![Workday App Service Principal ID](./media/export-import-provisioning-configuration/wd_export_01.png) Copy the JSON object from the response and save it to a file to create a backup ### Step 5: Import the Provisioning Schema > [!CAUTION] -> Perform this step only if you need to modify the schema for configuration that cannot be changed using the Azure portal or if you need to restore the configuration from a previously backed up file with valid and working schema. +> Perform this step only if you need to modify the schema for configuration that cannot be changed using the Microsoft Entra admin center or if you need to restore the configuration from a previously backed up file with valid and working schema. In the Microsoft Graph Explorer, configure the following PUT query, replacing [servicePrincipalId] and [ProvisioningJobId] with the ServicePrincipalId and the ProvisioningJobId retrieved in the previous steps.
active-directory	Expression Builder	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/expression-builder.md	Previously updated : 04/26/2023 Last updated : 09/15/2023
active-directory	Functions For Customizing Application Data	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/functions-for-customizing-application-data.md	Previously updated : 10/20/2022 Last updated : 09/15/2023
active-directory	How Provisioning Works	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/how-provisioning-works.md	Previously updated : 04/10/2023 Last updated : 09/15/2023 To request an automatic Azure AD provisioning connector for an app that doesn't ## Authorization -Credentials are required for Azure AD to connect to the application's user management API. While you're configuring automatic user provisioning for an application, you need to enter valid credentials. For gallery applications, you can find credential types and requirements for the application by referring to the app tutorial. For non-gallery applications, you can refer to the [SCIM](./use-scim-to-provision-users-and-groups.md#authorization-to-provisioning-connectors-in-the-application-gallery) documentation to understand the credential types and requirements. In the Azure portal, you're able to test the credentials by having Azure AD attempt to connect to the app's provisioning app using the supplied credentials. +Credentials are required for Azure AD to connect to the application's user management API. While you're configuring automatic user provisioning for an application, you need to enter valid credentials. For gallery applications, you can find credential types and requirements for the application by referring to the app tutorial. For non-gallery applications, you can refer to the [SCIM](./use-scim-to-provision-users-and-groups.md#authorization-to-provisioning-connectors-in-the-application-gallery) documentation to understand the credential types and requirements. In the Microsoft Entra admin center, you're able to test the credentials by having Azure AD attempt to connect to the app's provisioning app using the supplied credentials. ## Mapping attributes -When you enable user provisioning for a third-party SaaS application, the Azure portal controls its attribute values through attribute mappings. Mappings determine the user attributes that flow between Azure AD and the target application when user accounts are provisioned or updated. +When you enable user provisioning for a third-party SaaS application, the Microsoft Entra admin center controls its attribute values through attribute mappings. Mappings determine the user attributes that flow between Azure AD and the target application when user accounts are provisioned or updated. There's a preconfigured set of attributes and attribute mappings between Azure AD user objects and each SaaS appΓÇÖs user objects. Some apps manage other types of objects along with Users, such as Groups. After the initial cycle, all other cycles will: The provisioning service continues running back-to-back incremental cycles indefinitely, at intervals defined in the [tutorial specific to each application](../saas-apps/tutorial-list.md). Incremental cycles continue until one of the events occurs: -- The service is manually stopped using the Azure portal, or using the appropriate Microsoft Graph API command.-- A new initial cycle is triggered using the Restart provisioning option in the Azure portal, or using the appropriate Microsoft Graph API command. The action clears any stored watermark and causes all source objects to be evaluated again. Also, the action doesn't break the links between source and target objects. To break the links, use [Restart synchronizationJob](/graph/api/synchronization-synchronizationjob-restart?view=graph-rest-beta&tabs=http&preserve-view=true) with the request: +- The service is manually stopped using the Microsoft Entra admin center, or using the appropriate Microsoft Graph API command. +- A new initial cycle is triggered using the Restart provisioning option in the Microsoft Entra admin center, or using the appropriate Microsoft Graph API command. The action clears any stored watermark and causes all source objects to be evaluated again. Also, the action doesn't break the links between source and target objects. To break the links, use [Restart synchronizationJob](/graph/api/synchronization-synchronizationjob-restart?view=graph-rest-beta&tabs=http&preserve-view=true) with the request: <!-- { "blockType": "request", Resolve these failures by adjusting the attribute values for the affected user i ### Quarantine -If most or all of the calls that are made against the target system consistently fail because of an error (for example invalid admin credentials) the provisioning job goes into a "quarantine" state. This state is indicated in the [provisioning summary report](./check-status-user-account-provisioning.md) and via email if email notifications were configured in the Azure portal. +If most or all of the calls that are made against the target system consistently fail because of an error (for example invalid admin credentials) the provisioning job goes into a "quarantine" state. This state is indicated in the [provisioning summary report](./check-status-user-account-provisioning.md) and via email if email notifications were configured in the Microsoft Entra admin center. When in quarantine, the frequency of incremental cycles is gradually reduced to once per day. Performance depends on whether your provisioning job is running an initial provi ### How to tell if users are being provisioned properly -All operations run by the user provisioning service are recorded in the Azure AD [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). The logs include all read and write operations made to the source and target systems, and the user data that was read or written during each operation. For information on how to read the provisioning logs in the Azure portal, see the [provisioning reporting guide](./check-status-user-account-provisioning.md). +All operations run by the user provisioning service are recorded in the Azure AD [Provisioning logs (preview)](../reports-monitoring/concept-provisioning-logs.md?context=azure/active-directory/manage-apps/context/manage-apps-context). The logs include all read and write operations made to the source and target systems, and the user data that was read or written during each operation. For information on how to read the provisioning logs in the Microsoft Entra admin center, see the [provisioning reporting guide](./check-status-user-account-provisioning.md). ## Deprovisioning The Azure AD provisioning service keeps source and target systems in sync by deprovisioning accounts when user access is removed.
active-directory	Hr Attribute Retrieval Issues	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/hr-attribute-retrieval-issues.md	Previously updated : 10/20/2022 Last updated : 09/15/2023
active-directory	Hr Manager Update Issues	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/hr-manager-update-issues.md	Previously updated : 10/20/2022 Last updated : 09/15/2023 The Azure AD provisioning service automatically updates manager information so that the user-manager relationship in Azure AD is always in sync with your HR data. It uses a process called manager reference resolution to accurately update the manager attribute. Before going into the process details, it is important to understand how manager information is stored in Azure AD and on-premises Active Directory. * In on-premises Active Directory, the manager attribute stores the distinguishedName (dn) of the manager's account in AD. -* In Azure AD, the manager attribute is a DirectoryObject navigation property in Azure AD. When you view the user record in the Azure portal, it shows the displayName of the manager record in Azure AD. +* In Azure AD, the manager attribute is a DirectoryObject navigation property in Azure AD. When you view the user record in the Microsoft Entra admin center, it shows the displayName of the manager record in Azure AD. The manager reference resolution is a two step-process: * Step 1: Link the manager's HR source record with the manager's target account record using a pair of attributes referred to as source anchor and target anchor.
active-directory	Hr User Creation Issues	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/hr-user-creation-issues.md	Previously updated : 10/20/2022 Last updated : 09/15/2023
active-directory	Hr User Update Issues	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/hr-user-update-issues.md	Previously updated : 10/20/2022 Last updated : 09/15/2023
active-directory	Hr Writeback Issues	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/hr-writeback-issues.md	Previously updated : 10/20/2022 Last updated : 09/15/2023
active-directory	Inbound Provisioning Api Configure App	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-configure-app.md	Previously updated : 07/07/2023 Last updated : 09/15/2023 If you're configuring inbound user provisioning to on-premises Active Directory, ## Create your API-driven provisioning app -1. Log in to the [Microsoft Entra admin center](<https://entra.microsoft.com>). +1. Log in to the [Microsoft Entra admin center](<https://entra.microsoft.com>) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823). 2. Browse to Azure Active Directory > Applications > Enterprise applications. 3. Click on New application to create a new provisioning application. [![Screenshot of Entra Admin Center.](media/inbound-provisioning-api-configure-app/provisioning-entra-admin-center.png)](media/inbound-provisioning-api-configure-app/provisioning-entra-admin-center.png#lightbox)
active-directory	Inbound Provisioning Api Curl Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-curl-tutorial.md	## Verify processing of the bulk request payload -1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with global administrator or application administrator login credentials. +1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823). 1. Browse to Azure Active Directory -> Applications -> Enterprise applications. 1. Under all applications, use the search filter text box to find and open your API-driven provisioning application. 1. Open the Provisioning blade. The landing page displays the status of the last run.
active-directory	Inbound Provisioning Api Custom Attributes	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-custom-attributes.md	Previously updated : 07/24/2023 Last updated : 09/15/2023 You have configured API-driven provisioning app. You're provisioning app is succ In this step, we'll add the two attributes "HireDate" and "JobCode" that are not part of the standard SCIM schema to the provisioning app and use them in the provisioning data flow. -1. Log in to Microsoft Entra admin center with application administrator role. -1. Go to Enterprise applications and open your API-driven provisioning app. +1. Log in to your [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823). +1. Browse to Enterprise applications and open your API-driven provisioning app. 1. Open the Provisioning blade. 1. Click on the Edit Provisioning button. 1. Expand the Mappings section and click on the attribute mapping link. <br>
active-directory	Inbound Provisioning Api Grant Access	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-grant-access.md	Previously updated : 07/07/2023 Last updated : 09/15/2023 Depending on how your API client authenticates with Azure AD, you can select bet ## Configure a service principal This configuration registers an app in Azure AD that represents the external API client and grants it permission to invoke the inbound provisioning API. The service principal client id and client secret can be used in the OAuth client credentials grant flow. -1. Log in to Microsoft Entra admin center (https://entra.microsoft.com) with global administrator or application administrator login credentials. +1. Log in to Microsoft Entra admin center (https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) login credentials. 1. Browse to Azure Active Directory -> Applications -> App registrations. 1. Click on the option New registration. 1. Provide an app name, select the default options, and click on Register.
active-directory	Inbound Provisioning Api Graph Explorer	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-graph-explorer.md	Previously updated : 07/18/2023 Last updated : 09/15/2023 This tutorial describes how you can quickly test [API-driven inbound provisionin You can verify the processing either from the Microsoft Entra admin center or using Graph Explorer. ### Verify processing from Microsoft Entra admin center -1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with global administrator or application administrator login credentials. +1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) login credentials. 1. Browse to Azure Active Directory -> Applications -> Enterprise applications. 1. Under all applications, use the search filter text box to find and open your API-driven provisioning application. 1. Open the Provisioning blade. The landing page displays the status of the last run.
active-directory	Inbound Provisioning Api Postman	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-postman.md	Previously updated : 07/19/2023 Last updated : 09/15/2023 If the API invocation is successful, you see the message `202 Accepted.` Under H You can verify the processing either from the Microsoft Entra admin center or using Postman. ### Verify processing from Microsoft Entra admin center -1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with global administrator or application administrator login credentials. +1. Log in to [Microsoft Entra admin center](https://entra.microsoft.com) with at least [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823) level credentials. 1. Browse to Azure Active Directory -> Applications -> Enterprise applications. 1. Under all applications, use the search filter text box to find and open your API-driven provisioning application. 1. Open the Provisioning blade. The landing page displays the status of the last run.
active-directory	Inbound Provisioning Api Powershell	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/inbound-provisioning-api-powershell.md	Previously updated : 07/18/2023 Last updated : 09/15/2023 To illustrate the procedure, let's use the CSV file `Samples/csv-with-2-records. This section explains how to send the generated bulk request payload to your inbound provisioning API endpoint. -1. Log in to your Microsoft Entra admin center as Application Administrator or Global Administrator. -1. Copy the `ServicePrincipalId` associated with your provisioning app from Provisioning App > Properties > Object ID. +1. Log in to your [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Application Administrator](https://go.microsoft.com/fwlink/?linkid=2247823). +1. Browse to Provisioning App > Properties > Object ID and copy the `ServicePrincipalId` associated with your provisioning app. :::image type="content" border="true" source="./media/inbound-provisioning-api-powershell/object-id.png" alt-text="Screenshot of the Object ID." lightbox="./media/inbound-provisioning-api-powershell/object-id.png"::: -1. As user with Global Administrator role, run the following command by providing the correct values for `ServicePrincipalId` and `TenantId`. It will prompt you for authentication if an authenticated session doesn't already exist for this tenant. Provide your consent to permissions prompted during authentication. +1. As user with Global Administrator role, run the following command by providing the correct values for `ServicePrincipalId` and `TenantId`. It will prompt you for authentication if an authenticated session doesn't already exist for this tenant. Provide your consent to permissions prompted during authentication. ```powershell .\CSV2SCIM.ps1 -Path '..\Samples\csv-with-2-records.csv' -AttributeMapping $AttributeMapping -ServicePrincipalId <servicePrincipalId> -TenantId "contoso.onmicrosoft.com" This section explains how to send the generated bulk request payload to your inb $ThumbPrint = $ClientCertificate.ThumbPrint ``` The generated certificate is stored Current User\Personal\Certificates. You can view it using the Control Panel -> Manage user certificates option. -1. To associate this certificate with a valid service principal, log in to your Microsoft Entra admin center as Application Administrator. +1. To associate this certificate with a valid service principal, log in to your Microsoft Entra admin center as Application Administrator. 1. Open [the service principal you configured](inbound-provisioning-api-grant-access.md#configure-a-service-principal) under App Registrations. 1. Copy the Object ID from the Overview blade. Use the value to replace the string `<AppObjectId>`. Copy the Application (client) Id. We will use it later and it is referenced as `<AppClientId>`. 1. Run the following command to upload your certificate to the registered service principal.
active-directory	Isv Automatic Provisioning Multi Tenant Apps	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/isv-automatic-provisioning-multi-tenant-apps.md	Learn more about using Microsoft Graph for provisioning: * [Microsoft Graph Auth Overview](/graph/auth/) -* [Getting started with Microsoft Graph](https://developer.microsoft.com/graph/get-started) +* [Getting started with Microsoft Graph](https://developer.microsoft.com/graph/rest-api/) ## Using SAML JIT for provisioning
active-directory	On Premises Powershell Connector	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/on-premises-powershell-connector.md	The connector provides a bridge between the capabilities of the ECMA Connector H - Connectivity between hosting server, the connector, and the target system that the PowerShell scripts interact with. - The execution policy on the server must be configured to allow the connector to run Windows PowerShell scripts. Unless the scripts the connector runs are digitally signed, configure the execution policy by running this command: `Set-ExecutionPolicy -ExecutionPolicy RemoteSigned`-- Deploying this connector requires one or more PowerShell scripts. Some Microsoft products may provide scripts for use with this connector, and the support statement for those scripts would be provided by that product. If you are developing your own scripts for use with this connector, you'll need to have familiarity with the [Extensible Connectivity Management Agent API](https://msdn.microsoft.com/library/windows/desktop/hh859557.aspx) to develop and maintain those scripts. If you are integrating with third party systems using your own scripts in a production environment, we recommend you work with the third party vendor or a deployment partner for help, guidance and support for this integration. +- Deploying this connector requires one or more PowerShell scripts. Some Microsoft products may provide scripts for use with this connector, and the support statement for those scripts would be provided by that product. If you are developing your own scripts for use with this connector, you'll need to have familiarity with the [Extensible Connectivity Management Agent API](/previous-versions/windows/desktop/forefront-2010/hh859557(v=vs.100)?redirectedfrom=MSDN) to develop and maintain those scripts. If you are integrating with third party systems using your own scripts in a production environment, we recommend you work with the third party vendor or a deployment partner for help, guidance and support for this integration. The connectivity tab allows you to supply configuration parameters for connectin \| Password \| \<Blank\> \| Password of the credential to store for use when the connector is run. \| \| Impersonate Connector Account \|Unchecked\| When true, the synchronization service runs the Windows PowerShell scripts in the context of the credentials supplied. When possible, it is recommended that the $Credentials parameter is passed to each script is used instead of impersonation.\| \| Load User Profile When Impersonating \|Unchecked\|Instructs Windows to load the user profile of the connectorΓÇÖs credentials during impersonation. If the impersonated user has a roaming profile, the connector does not load the roaming profile.\| -\| Logon Type When Impersonating \|None\|Logon type during impersonation. For more information, see the [dwLogonType][dw] documentation. \| +\| Logon Type When Impersonating \|None\|Logon type during impersonation. For more information, see the [dwLogonType](/windows/win32/api/winbase/nf-winbase-logonusera#parameters) documentation. \| \|Signed Scripts Only \|Unchecked\| If true, the Windows PowerShell connector validates that each script has a valid digital signature. If false, ensure that the Synchronization Service serverΓÇÖs Windows PowerShell execution policy is RemoteSigned or Unrestricted.\| \|Common Module Script Name (with extension)\|xADSyncPSConnectorModule.psm1\|The connector allows you to store a shared Windows PowerShell module in the configuration. When the connector runs a script, the Windows PowerShell module is extracted to the file system so that it can be imported by each script.\| \|Common Module Script\|[AD Sync PowerShell Connector Module code](https://github.com/microsoft/MIMPowerShellConnectors/blob/master/src/ECMA2HostCSV/Scripts/CommonModule.psm1) as value. This module will be automatically created by the ECMA2Host when the connector is running.\|\|
active-directory	On Premises Scim Provisioning	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/on-premises-scim-provisioning.md	# Azure AD on-premises application provisioning to SCIM-enabled apps -The Azure Active Directory (Azure AD) provisioning service supports a [SCIM 2.0](https://techcommunity.microsoft.com/t5/identity-standards-blog/provisioning-with-scim-getting-started/ba-p/880010) client that can be used to automatically provision users into cloud or on-premises applications. This article outlines how you can use the Azure AD provisioning service to provision users into an on-premises application that's SCIM enabled. If you want to provision users into non-SCIM on-premises applications that use SQL as a data store, see the [Azure AD ECMA Connector Host Generic SQL Connector tutorial](tutorial-ecma-sql-connector.md). If you want to provision users into cloud apps such as DropBox and Atlassian, review the app-specific [tutorials](../../active-directory/saas-apps/tutorial-list.md). +The Azure Active Directory (Azure AD) provisioning service supports a [SCIM 2.0](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/provisioning-with-scim-getting-started/ba-p/880010) client that can be used to automatically provision users into cloud or on-premises applications. This article outlines how you can use the Azure AD provisioning service to provision users into an on-premises application that's SCIM enabled. If you want to provision users into non-SCIM on-premises applications that use SQL as a data store, see the [Azure AD ECMA Connector Host Generic SQL Connector tutorial](tutorial-ecma-sql-connector.md). If you want to provision users into cloud apps such as DropBox and Atlassian, review the app-specific [tutorials](../../active-directory/saas-apps/tutorial-list.md). ![Diagram that shows SCIM architecture.](./media/on-premises-scim-provisioning/scim-4.png) The following video provides an overview of on-premises provisioning. > [!VIDEO https://www.youtube.com/embed/QdfdpaFolys] ## Additional requirements -* Ensure your [SCIM](https://techcommunity.microsoft.com/t5/identity-standards-blog/provisioning-with-scim-getting-started/ba-p/880010) implementation meets the [Azure AD SCIM requirements](use-scim-to-provision-users-and-groups.md). +* Ensure your [SCIM](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/provisioning-with-scim-getting-started/ba-p/880010) implementation meets the [Azure AD SCIM requirements](use-scim-to-provision-users-and-groups.md). Azure AD offers open-source [reference code](https://github.com/AzureAD/SCIMReferenceCode/wiki) that developers can use to bootstrap their SCIM implementation. The code is as is. * Support the /schemas endpoint to reduce configuration required in the Azure portal.
active-directory	Sap Successfactors Integration Reference	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/app-provisioning/sap-successfactors-integration-reference.md	To further secure the connectivity between Azure AD provisioning service and Suc 1. Copy all IP address ranges listed within the element addressPrefixes and use the range to build your IP address restriction list. 1. Translate the CIDR values to IP ranges. -1. Log in to SuccessFactors admin portal to add IP ranges to the allowlist. Refer to SAP [support note 2253200](https://apps.support.sap.com/sap/support/knowledge/en/2253200). You can now [enter IP ranges](https://answers.sap.com/questions/12882263/whitelisting-sap-cloud-platform-ip-address-range-i.html) in this tool. +1. Log in to SuccessFactors admin portal to add IP ranges to the allowlist. Refer to SAP [support note 2253200](https://userapps.support.sap.com/sap/support/knowledge/2253200). You can now [enter IP ranges](https://answers.sap.com/questions/12882263/whitelisting-sap-cloud-platform-ip-address-range-i.html) in this tool. ## Supported entities For every user in SuccessFactors, Azure AD provisioning service retrieves the following entities. Each entity is expanded using the OData API $expand query parameter as outlined in the Retrieval rule column. Some entities are expanded by default, while some entities are expanded only if a specific attribute is present in the mapping.
active-directory	Concept Continuous Access Evaluation Workload	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/conditional-access/concept-continuous-access-evaluation-workload.md	Continuous access evaluation (CAE) for [workload identities](../workload-identit Continuous access evaluation doesn't currently support managed identities. -## Scope of preview +## Scope of support The continuous access evaluation for workload identities is supported only on access requests sent to Microsoft Graph as a resource provider. More resource providers will be added over time.
active-directory	V2 Protocols Oidc	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/develop/v2-protocols-oidc.md	To sign out a user, perform both of these operations: * Redirect the user's user-agent to the Microsoft identity platform's logout URI * Clear your app's cookies or otherwise end the user's session in your application. -If you fail to perform either operation, the user may remain authenticated and not be prompted to sign-in the next time they user your app. +If you fail to perform either operation, the user may remain authenticated and not be prompted to sign-in the next time they use your app. Redirect the user-agent to the `end_session_endpoint` as shown in the OpenID Connect configuration document. The `end_session_endpoint` supports both HTTP GET and POST requests.
active-directory	Apps	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/governance/apps.md	Microsoft Entra identity governance can be integrated with many other applicatio \| [Acunetix 360](../../active-directory/saas-apps/acunetix-360-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Adobe Identity Management](../../active-directory/saas-apps/adobe-identity-management-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Adobe Identity Management (OIDC)](../../active-directory/saas-apps/adobe-identity-management-provisioning-oidc-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Airbase](../../active-directory/saas-apps/airbase-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Aha!](../../active-directory/saas-apps/aha-tutorial.md) \| \| ΓùÅ \| \| [Airstack](../../active-directory/saas-apps/airstack-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Akamai Enterprise Application Access](../../active-directory/saas-apps/akamai-enterprise-application-access-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Airtable](../../active-directory/saas-apps/airtable-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Albert](../../active-directory/saas-apps/albert-provisioning-tutorial.md) \| ΓùÅ \| \| \| [AlertMedia](../../active-directory/saas-apps/alertmedia-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Alexis HR](../../active-directory/saas-apps/alexishr-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Alinto Protect (renamed Cleanmail)](../../active-directory/saas-apps/alinto-protect-provisioning-tutorial.md) \| ΓùÅ \| \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Autodesk SSO](../../active-directory/saas-apps/autodesk-sso-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Azure Databricks SCIM Connector](/azure/databricks/administration-guide/users-groups/scim/aad) \| ΓùÅ \| \| \| [AWS IAM Identity Center](../../active-directory/saas-apps/aws-single-sign-on-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Axiad Cloud](../../active-directory/saas-apps/axiad-cloud-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [BambooHR](../../active-directory/saas-apps/bamboo-hr-tutorial.md) \| \| ΓùÅ \| \| [BenQ IAM](../../active-directory/saas-apps/benq-iam-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Bentley - Automatic User Provisioning](../../active-directory/saas-apps/bentley-automatic-user-provisioning-tutorial.md) \| ΓùÅ \| \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Cisco Umbrella User Management](../../active-directory/saas-apps/cisco-umbrella-user-management-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Cisco Webex](../../active-directory/saas-apps/cisco-webex-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Clarizen One](../../active-directory/saas-apps/clarizen-one-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Cleanmail Swiss](../../active-directory/saas-apps/cleanmail-swiss-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Clebex](../../active-directory/saas-apps/clebex-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Cloud Academy SSO](../../active-directory/saas-apps/cloud-academy-sso-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Coda](../../active-directory/saas-apps/coda-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Concur](../../active-directory/saas-apps/concur-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Cornerstone OnDemand](../../active-directory/saas-apps/cornerstone-ondemand-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [CybSafe](../../active-directory/saas-apps/cybsafe-provisioning-tutorial.md) \| ΓùÅ \| \| +\| [Dagster Cloud](../../active-directory/saas-apps/dagster-cloud-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Datadog](../../active-directory/saas-apps/datadog-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Documo](../../active-directory/saas-apps/documo-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [DocuSign](../../active-directory/saas-apps/docusign-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Dropbox Business](../../active-directory/saas-apps/dropboxforbusiness-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Fortes Change Cloud](../../active-directory/saas-apps/fortes-change-cloud-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Frankli.io](../../active-directory/saas-apps/frankli-io-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Freshservice Provisioning](../../active-directory/saas-apps/freshservice-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Funnel Leasing](../../active-directory/saas-apps/funnel-leasing-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Fuze](../../active-directory/saas-apps/fuze-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [G Suite](../../active-directory/saas-apps/g-suite-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Genesys Cloud for Azure](../../active-directory/saas-apps/purecloud-by-genesys-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Grammarly](../../active-directory/saas-apps/grammarly-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Group Talk](../../active-directory/saas-apps/grouptalk-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Gtmhub](../../active-directory/saas-apps/gtmhub-provisioning-tutorial.md) \| ΓùÅ \| \| +\| [H5mag](../../active-directory/saas-apps/h5mag-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Harness](../../active-directory/saas-apps/harness-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| HCL Domino \| ΓùÅ \| \| +\| [Headspace](../../active-directory/saas-apps/headspace-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [HelloID](../../active-directory/saas-apps/helloid-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Holmes Cloud](../../active-directory/saas-apps/holmes-cloud-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Hootsuite](../../active-directory/saas-apps/hootsuite-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Hoxhunt](../../active-directory/saas-apps/hoxhunt-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Howspace](../../active-directory/saas-apps/howspace-provisioning-tutorial.md) \| ΓùÅ \| \| -\| [H5mag](../../active-directory/saas-apps/h5mag-provisioning-tutorial.md) \| ΓùÅ \| \| +\| [Humbol](../../active-directory/saas-apps/humbol-provisioning-tutorial.md) \| ΓùÅ \| \| \| IBM DB2 ([SQL connector](../../active-directory/app-provisioning/tutorial-ecma-sql-connector.md) ) \| ΓùÅ \| \| \| IBM Tivoli Directory Server ([LDAP connector](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) ) \| ΓùÅ \| \| \| [Ideo](../../active-directory/saas-apps/ideo-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Ideagen Cloud](../../active-directory/saas-apps/ideagen-cloud-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Infor CloudSuite](../../active-directory/saas-apps/infor-cloudsuite-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [InformaCast](../../active-directory/saas-apps/informacast-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [iPass SmartConnect](../../active-directory/saas-apps/ipass-smartconnect-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Iris Intranet](../../active-directory/saas-apps/iris-intranet-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Insight4GRC](../../active-directory/saas-apps/insight4grc-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Juno Journey](../../active-directory/saas-apps/juno-journey-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Keeper Password Manager & Digital Vault](../../active-directory/saas-apps/keeper-password-manager-digitalvault-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Keepabl](../../active-directory/saas-apps/keepabl-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Kintone](../../active-directory/saas-apps/kintone-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Kisi Phsyical Security](../../active-directory/saas-apps/kisi-physical-security-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Klaxoon](../../active-directory/saas-apps/klaxoon-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Klaxoon SAML](../../active-directory/saas-apps/klaxoon-saml-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [LinkedIn Sales Navigator](../../active-directory/saas-apps/linkedinsalesnavigator-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Lucid (All Products)](../../active-directory/saas-apps/lucid-all-products-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Lucidchart](../../active-directory/saas-apps/lucidchart-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [LUSID](../../active-directory/saas-apps/LUSID-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Leapsome](../../active-directory/saas-apps/leapsome-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [LogicGate](../../active-directory/saas-apps/logicgate-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Looop](../../active-directory/saas-apps/looop-provisioning-tutorial.md) \| ΓùÅ \| \| \| [LogMeIn](../../active-directory/saas-apps/logmein-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Maptician](../../active-directory/saas-apps/maptician-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Markit Procurement Service](../../active-directory/saas-apps/markit-procurement-service-provisioning-tutorial.md) \| ΓùÅ \| \| \| [MediusFlow](../../active-directory/saas-apps/mediusflow-provisioning-tutorial.md) \| ΓùÅ \| \| \| [MerchLogix](../../active-directory/saas-apps/merchlogix-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Meta Networks Connector](../../active-directory/saas-apps/meta-networks-connector-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Miro](../../active-directory/saas-apps/miro-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Monday.com](../../active-directory/saas-apps/mondaycom-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [MongoDB Atlas](../../active-directory/saas-apps/mongodb-cloud-tutorial.md) \| \| ΓùÅ \| +\| [Moqups](../../active-directory/saas-apps/moqups-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Mural Identity](../../active-directory/saas-apps/mural-identity-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [MX3 Diagnostics](../../active-directory/saas-apps/mx3-diagnostics-connector-provisioning-tutorial.md) \| ΓùÅ \| \| \| [myPolicies](../../active-directory/saas-apps/mypolicies-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Netsparker Enterprise](../../active-directory/saas-apps/netsparker-enterprise-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [New Relic by Organization](../../active-directory/saas-apps/new-relic-by-organization-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [NordPass](../../active-directory/saas-apps/nordpass-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Notion](../../active-directory/saas-apps/notion-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| Novell eDirectory ([LDAP connector](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) ) \| ΓùÅ \| \| \| [Office Space Software](../../active-directory/saas-apps/officespace-software-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Olfeo SAAS](../../active-directory/saas-apps/olfeo-saas-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| Open DJ ([LDAP connector](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) ) \| ΓùÅ \| \| \| Open DS ([LDAP connector](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) ) \| ΓùÅ \| \| +\| [OpenForms](../../active-directory/saas-apps/openforms-provisioning-tutorial.md) \| ΓùÅ \| \| \| [OpenLDAP](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) \| ΓùÅ \| \| \| [OpenText Directory Services](../../active-directory/saas-apps/open-text-directory-services-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Oracle Cloud Infrastructure Console](../../active-directory/saas-apps/oracle-cloud-infrastructure-console-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| Oracle Database ([SQL connector](../../active-directory/app-provisioning/tutorial-ecma-sql-connector.md) ) \| ΓùÅ \| \| \| Oracle E-Business Suite \| ΓùÅ \| ΓùÅ \| \| [Oracle Fusion ERP](../../active-directory/saas-apps/oracle-fusion-erp-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [O'Reilly Learning Platform](../../active-directory/saas-apps/oreilly-learning-platform-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| Oracle Internet Directory \| ΓùÅ \| \| \| Oracle PeopleSoft ERP \| ΓùÅ \| ΓùÅ \| \| Oracle SunONE Directory Server ([LDAP connector](../../active-directory/app-provisioning/on-premises-ldap-connector-configure.md) ) \| ΓùÅ \| \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Real Links](../../active-directory/saas-apps/real-links-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Reward Gateway](../../active-directory/saas-apps/reward-gateway-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [RFPIO](../../active-directory/saas-apps/rfpio-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Rhombus Systems](../../active-directory/saas-apps/rhombus-systems-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Ring Central](../../active-directory/saas-apps/ringcentral-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Robin](../../active-directory/saas-apps/robin-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Rollbar](../../active-directory/saas-apps/rollbar-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Rouse Sales](../../active-directory/saas-apps/rouse-sales-provisioning-tutorial.md) \| ΓùÅ \| \| -\| [Salesforce](../../active-directory/saas-apps/salesforce-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Salesforce](../../active-directory/saas-apps/salesforce-provisioning-tutorial.md) \| ΓùÅ \| \| +\| [SafeGuard Cyber](../../active-directory/saas-apps/safeguard-cyber-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Salesforce Sandbox](../../active-directory/saas-apps/salesforce-sandbox-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Samanage](../../active-directory/saas-apps/samanage-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| SAML-based apps \| \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Swit](../../active-directory/saas-apps/swit-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Symantec Web Security Service (WSS)](../../active-directory/saas-apps/symantec-web-security-service.md) \| ΓùÅ \| ΓùÅ \| \| [Tableau Cloud](../../active-directory/saas-apps/tableau-online-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Tailscale](../../active-directory/saas-apps/tailscale-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Talentech](../../active-directory/saas-apps/talentech-provisioning-tutorial.md) \| ΓùÅ \| \| +\| [Tanium SSO](../../active-directory/saas-apps/tanium-sso-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Tap App Security](../../active-directory/saas-apps/tap-app-security-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Taskize Connect](../../active-directory/saas-apps/taskize-connect-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Teamgo](../../active-directory/saas-apps/teamgo-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Uber](../../active-directory/saas-apps/uber-provisioning-tutorial.md) \| ΓùÅ \| \| \| [UNIFI](../../active-directory/saas-apps/unifi-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [uniFlow Online](../../active-directory/saas-apps/uniflow-online-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [uni-tel ) \| ΓùÅ \| \| +\| [Vault Platform](../../active-directory/saas-apps/vault-platform-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Vbrick Rev Cloud](../../active-directory/saas-apps/vbrick-rev-cloud-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [V-Client](../../active-directory/saas-apps/v-client-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Velpic](../../active-directory/saas-apps/velpic-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Visibly](../../active-directory/saas-apps/visibly-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Visitly](../../active-directory/saas-apps/visitly-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Vonage](../../active-directory/saas-apps/vonage-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [WATS](../../active-directory/saas-apps/wats-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Webroot Security Awareness Training](../../active-directory/saas-apps/webroot-security-awareness-training-provisioning-tutorial.md) \| ΓùÅ \| \| \| [WEDO](../../active-directory/saas-apps/wedo-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Whimsical](../../active-directory/saas-apps/whimsical-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| Microsoft Entra identity governance can be integrated with many other applicatio \| [Workplace by Facebook](../../active-directory/saas-apps/workplace-by-facebook-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Workgrid](../../active-directory/saas-apps/workgrid-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| \| [Wrike](../../active-directory/saas-apps/wrike-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \| +\| [Xledger](../../active-directory/saas-apps/xledger-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Yellowbox](../../active-directory/saas-apps/yellowbox-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Zapier](../../active-directory/saas-apps/zapier-provisioning-tutorial.md) \| ΓùÅ \| \| \| [Zendesk](../../active-directory/saas-apps/zendesk-provisioning-tutorial.md) \| ΓùÅ \| ΓùÅ \|
active-directory	Tutorial Prepare User Accounts	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/governance/tutorial-prepare-user-accounts.md	Next, we create Britta Simon. This is the account that is used as our manager. As an alternative, the following PowerShell script may also be used to quickly create two users needed execute a lifecycle workflow. One user represents our new employee and the second represents the new employee's manager. ->[!IMPORTANT] ->The following PowerShell script is provided to quickly create the two users required for this tutorial. These users can also be created manually by signing in to the Microsoft Entra Admin center as a global administrator and creating them. +> [!IMPORTANT] +> The following PowerShell script is provided to quickly create the two users required for this tutorial. These users can also be created in the Microsoft Entra Admin center. In order to create this step, save the following PowerShell script to a location on a machine that has access to Azure.
active-directory	Lines Elibrary Advance Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lines-elibrary-advance-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Lines eLibrary Advance for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Lines eLibrary Advance tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Lines eLibrary Advance for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Lines eLibrary Advance tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Lines eLibrary Advance for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Liquidfiles Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/liquidfiles-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to LiquidFiles Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the LiquidFiles tile in the My Apps, this will redirect to LiquidFiles Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the LiquidFiles tile in the My Apps, this will redirect to LiquidFiles Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Litmos Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/litmos-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SAP Litmos for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SAP Litmos tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SAP Litmos for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SAP Litmos tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SAP Litmos for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Lms And Education Management System Leaf Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lms-and-education-management-system-leaf-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to LMS and Education Management System Leaf Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the LMS and Education Management System Leaf tile in the My Apps, this will redirect to LMS and Education Management System Leaf Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the LMS and Education Management System Leaf tile in the My Apps, this will redirect to LMS and Education Management System Leaf Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Locus Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/locus-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Locus Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Locus tile in the My Apps, this will redirect to Locus Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Locus tile in the My Apps, this will redirect to Locus Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Lusha Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lusha-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Lusha for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Lusha tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Lusha for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Lusha tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Lusha for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Lusid Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lusid-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the LUSID for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the LUSID tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the LUSID for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the LUSID tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the LUSID for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Lynda Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lynda-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Lynda.com Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Lynda.com tile in the My Apps, this will redirect to Lynda.com Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Lynda.com tile in the My Apps, this will redirect to Lynda.com Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Lytx Drivecam Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lytx-drivecam-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Lytx DriveCam for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Lytx DriveCam tile in the My Apps, you should be automatically signed in to the Lytx DriveCam for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Lytx DriveCam tile in the My Apps, you should be automatically signed in to the Lytx DriveCam for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Lyve Cloud Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/lyve-cloud-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Lyve Cloud for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Lyve Cloud tile in the My Apps, you should be automatically signed in to the Lyve Cloud for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Lyve Cloud tile in the My Apps, you should be automatically signed in to the Lyve Cloud for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mail Luck Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mail-luck-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Mail Luck! Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Mail Luck! tile in the My Apps, this will redirect to Mail Luck! Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Mail Luck! tile in the My Apps, this will redirect to Mail Luck! Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Manabipocket Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/manabipocket-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Manabi Pocket Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Manabi Pocket tile in the My Apps, this will redirect to Manabi Pocket Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Manabi Pocket tile in the My Apps, this will redirect to Manabi Pocket Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Manifestly Checklists Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/manifestly-checklists-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Manifestly Checklists for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Manifestly Checklists tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Manifestly Checklists for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Manifestly Checklists tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Manifestly Checklists for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mapiq Essentials Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mapiq-essentials-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Mapiq Essentials Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Mapiq Essentials tile in the My Apps, this will redirect to Mapiq Essentials Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Mapiq Essentials tile in the My Apps, this will redirect to Mapiq Essentials Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Maximo Application Suite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/maximo-application-suite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal to be taken to the Maximo login page where you need to enter in your SAML identity as a fully qualified email address. If the user has already authenticated with the IDP the Maximo Application Suite won't have to login again, and the browser will be redirected to the home page. -* You can also use Microsoft My Apps to test the application in any mode. When you click the Maximo Application Suite tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Maximo Application Suite for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can also use Microsoft My Apps to test the application in any mode. When you click the Maximo Application Suite tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Maximo Application Suite for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). > [!Note] > Screenshots are from MAS Continuous-delivery 8.9 and may differ in future versions.
active-directory	Maxxpoint Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/maxxpoint-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the MaxxPoint for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the MaxxPoint tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the MaxxPoint for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the MaxxPoint tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the MaxxPoint for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mcm Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mcm-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to MCM Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the MCM tile in the My Apps, this will redirect to MCM Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the MCM tile in the My Apps, this will redirect to MCM Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Meta Work Accounts Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/meta-work-accounts-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Meta Work Accounts for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Meta Work Accounts tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Meta Work Accounts for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Meta Work Accounts tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Meta Work Accounts for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mihcm Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mihcm-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to MiHCM Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the MiHCM tile in the My Apps, this will redirect to MiHCM Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the MiHCM tile in the My Apps, this will redirect to MiHCM Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mindflash Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mindflash-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Learn Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Trakstar Learn tile in the My Apps, this will redirect to Learn Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Trakstar Learn tile in the My Apps, this will redirect to Learn Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mint Tms Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mint-tms-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the MINT TMS for which you set up the SSO. -* You can use Microsoft My Apps. When you click the MINT TMS tile in the My Apps, you should be automatically signed in to the MINT TMS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the MINT TMS tile in the My Apps, you should be automatically signed in to the MINT TMS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Mist Cloud Admin Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mist-cloud-admin-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Mist Cloud Admin SSO for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Mist Cloud Admin SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mist Cloud Admin SSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Mist Cloud Admin SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mist Cloud Admin SSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mobilexpense Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mobilexpense-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Mobile Xpense for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Mobile Xpense tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mobile Xpense for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Mobile Xpense tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mobile Xpense for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Momenta Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/momenta-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Momenta for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Momenta tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Momenta for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Momenta tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Momenta for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Motus Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/motus-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Motus for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Motus tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Motus for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Motus tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Motus for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Moxiengage Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/moxiengage-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Moxi Engage Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Moxi Engage tile in the My Apps, this will redirect to Moxi Engage Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Moxi Engage tile in the My Apps, this will redirect to Moxi Engage Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Moxtra Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/moxtra-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Moxtra Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Moxtra tile in the My Apps, this will redirect to Moxtra Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Moxtra tile in the My Apps, this will redirect to Moxtra Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mural Identity Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mural-identity-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Mural Identity for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Mural Identity tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mural Identity for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Mural Identity tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Mural Identity for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Change log
active-directory	Myaos Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/myaos-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the myAOS for which you set up the SSO. -* You can use Microsoft My Apps. When you click the myAOS tile in the My Apps, you should be automatically signed in to the myAOS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the myAOS tile in the My Apps, you should be automatically signed in to the myAOS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Myaryaka Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/myaryaka-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to MyAryaka Sign-On URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the MyAryaka tile in the My Apps, this will redirect to MyAryaka Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the MyAryaka tile in the My Apps, this will redirect to MyAryaka Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Myawardpoints Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/myawardpoints-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to My Award Points Top Sub/Top Team Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the My Award Points Top Sub/Top Team tile in the My Apps, this will redirect to My Award Points Top Sub/Top Team Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the My Award Points Top Sub/Top Team tile in the My Apps, this will redirect to My Award Points Top Sub/Top Team Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mymobilityhq Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mymobilityhq-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to myMobilityHQ Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the myMobilityHQ tile in the My Apps, this will redirect to myMobilityHQ Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the myMobilityHQ tile in the My Apps, this will redirect to myMobilityHQ Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Mypolicies Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mypolicies-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the myPolicies for which you set up the SSO. -* You can use Microsoft My Apps. When you click the myPolicies tile in the My Apps, you should be automatically signed in to the myPolicies for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the myPolicies tile in the My Apps, you should be automatically signed in to the myPolicies for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Mysdworxcom Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/mysdworxcom-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the my.sdworx.com for which you set up the SSO. -* You can use Microsoft My Apps. When you click the my.sdworx.com tile in the My Apps, you should be automatically signed in to the my.sdworx.com for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the my.sdworx.com tile in the My Apps, you should be automatically signed in to the my.sdworx.com for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	N2f Expensereports Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/n2f-expensereports-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the N2F - Expense reports for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the N2F - Expense reports tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the N2F - Expense reports for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the N2F - Expense reports tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the N2F - Expense reports for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Navan Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/navan-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Navan for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Navan tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Navan for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Navan tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Navan for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Negometrixportal Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/negometrixportal-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to NegometrixPortal Single Sign On (SSO) Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the NegometrixPortal Single Sign On (SSO) tile in the My Apps, this will redirect to NegometrixPortal Single Sign On (SSO) Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the NegometrixPortal Single Sign On (SSO) tile in the My Apps, this will redirect to NegometrixPortal Single Sign On (SSO) Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Neotalogicstudio Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/neotalogicstudio-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Neota Studio Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Neota Studio tile in the My Apps, this will redirect to Neota Studio Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Neota Studio tile in the My Apps, this will redirect to Neota Studio Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Netskope Cloud Exchange Administration Console Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/netskope-cloud-exchange-administration-console-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Netskope Cloud Exchange Administration Console Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Netskope Cloud Exchange Administration Console tile in the My Apps, this will redirect to Netskope Cloud Exchange Administration Console Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Netskope Cloud Exchange Administration Console tile in the My Apps, this will redirect to Netskope Cloud Exchange Administration Console Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Netskope Cloud Security Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/netskope-cloud-security-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Netskope Administrator Console for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Netskope Administrator Console tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Netskope Administrator Console for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Netskope Administrator Console tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Netskope Administrator Console for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Netsparker Enterprise Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/netsparker-enterprise-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Invicti for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Invicti tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Invicti for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Invicti tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Invicti for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Newsignature Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/newsignature-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Cloud Management Portal for Microsoft Azure Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Cloud Management Portal for Microsoft Azure tile in the My Apps, this will redirect to Cloud Management Portal for Microsoft Azure Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Cloud Management Portal for Microsoft Azure tile in the My Apps, this will redirect to Cloud Management Portal for Microsoft Azure Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Nice Cxone Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/nice-cxone-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to NICE CXone Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the NICE CXone tile in the My Apps, this will redirect to NICE CXone Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the NICE CXone tile in the My Apps, this will redirect to NICE CXone Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Nodetrax Project Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/nodetrax-project-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Nodetrax Project for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Nodetrax Project tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Nodetrax Project for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Nodetrax Project tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Nodetrax Project for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Nomadesk Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/nomadesk-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Nomadesk Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Nomadesk tile in the My Apps, this will redirect to Nomadesk Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Nomadesk tile in the My Apps, this will redirect to Nomadesk Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Ns1 Sso Azure Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/ns1-sso-azure-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the NS1 SSO for Azure for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the NS1 SSO for Azure tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the NS1 SSO for Azure for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the NS1 SSO for Azure tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the NS1 SSO for Azure for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Onedesk Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/onedesk-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the OneDesk for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the OneDesk tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the OneDesk for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the OneDesk tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the OneDesk for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Oneflow Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oneflow-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Oneflow for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Oneflow tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Oneflow for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Oneflow tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Oneflow for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oneteam Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oneteam-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Oneteam for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Oneteam tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Oneteam for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Oneteam tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Oneteam for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Opal Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/opal-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Opal for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Opal tile in the My Apps, you should be automatically signed in to the Opal for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Opal tile in the My Apps, you should be automatically signed in to the Opal for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Openlearning Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/openlearning-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to OpenLearning Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the OpenLearning tile in the My Apps, this will redirect to OpenLearning Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the OpenLearning tile in the My Apps, this will redirect to OpenLearning Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Optiturn Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/optiturn-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to OptiTurn Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the OptiTurn tile in the My Apps, this will redirect to OptiTurn Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the OptiTurn tile in the My Apps, this will redirect to OptiTurn Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oracle Access Manager For Oracle Ebs Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oracle-access-manager-for-oracle-ebs-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Oracle Access Manager for Oracle E-Business Suite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Oracle Access Manager for Oracle E-Business Suite tile in the My Apps, this will redirect to Oracle Access Manager for Oracle E-Business Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Oracle Access Manager for Oracle E-Business Suite tile in the My Apps, this will redirect to Oracle Access Manager for Oracle E-Business Suite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oracle Access Manager For Oracle Retail Merchandising Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oracle-access-manager-for-oracle-retail-merchandising-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Oracle Access Manager for Oracle Retail Merchandising Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Oracle Access Manager for Oracle Retail Merchandising tile in the My Apps, this will redirect to Oracle Access Manager for Oracle Retail Merchandising Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Oracle Access Manager for Oracle Retail Merchandising tile in the My Apps, this will redirect to Oracle Access Manager for Oracle Retail Merchandising Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oracle Idcs For Ebs Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oracle-idcs-for-ebs-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Oracle IDCS for E-Business Suite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Oracle IDCS for E-Business Suite tile in the My Apps, this will redirect to Oracle IDCS for E-Business Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Oracle IDCS for E-Business Suite tile in the My Apps, this will redirect to Oracle IDCS for E-Business Suite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oracle Idcs For Jd Edwards Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oracle-idcs-for-jd-edwards-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Oracle IDCS for JD Edwards Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Oracle IDCS for JD Edwards tile in the My Apps, this will redirect to Oracle IDCS for JD Edwards Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Oracle IDCS for JD Edwards tile in the My Apps, this will redirect to Oracle IDCS for JD Edwards Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oracle Idcs For Peoplesoft Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oracle-idcs-for-peoplesoft-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Oracle IDCS for PeopleSoft Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Oracle IDCS for PeopleSoft tile in the My Apps, this will redirect to Oracle IDCS for PeopleSoft Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Oracle IDCS for PeopleSoft tile in the My Apps, this will redirect to Oracle IDCS for PeopleSoft Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Oreilly Learning Platform Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/oreilly-learning-platform-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the O'Reilly learning platform for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the O'Reilly learning platform tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the O'Reilly learning platform for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the O'Reilly learning platform tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the O'Reilly learning platform for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Pagedna Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pagedna-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PageDNA Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PageDNA tile in the My Apps, this will redirect to PageDNA Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PageDNA tile in the My Apps, this will redirect to PageDNA Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Palantir Foundry Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/palantir-foundry-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Palantir Foundry for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Palantir Foundry tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Palantir Foundry for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Palantir Foundry tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Palantir Foundry for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Parallels Desktop Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/parallels-desktop-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Parallels Desktop Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Parallels Desktop tile in the My Apps, this will redirect to Parallels Desktop Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Parallels Desktop tile in the My Apps, this will redirect to Parallels Desktop Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Parkable Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/parkable-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Parkable Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Parkable tile in the My Apps, this will redirect to Parkable Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Parkable tile in the My Apps, this will redirect to Parkable Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Parkhere Corporate Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/parkhere-corporate-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ParkHere Corporate for which you set up the SSO. -* You can use Microsoft My Apps. When you click the ParkHere Corporate tile in the My Apps, you should be automatically signed in to the ParkHere Corporate for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ParkHere Corporate tile in the My Apps, you should be automatically signed in to the ParkHere Corporate for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Patentsquare Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/patentsquare-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PatentSQUARE Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PatentSQUARE tile in the My Apps, this will redirect to PatentSQUARE Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PatentSQUARE tile in the My Apps, this will redirect to PatentSQUARE Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pavaso Digital Close Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pavaso-digital-close-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Pavaso Digital Close for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Pavaso Digital Close tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Pavaso Digital Close for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Pavaso Digital Close tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Pavaso Digital Close for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Peakon Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/peakon-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Peakon for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Peakon tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Peakon for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Peakon tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Peakon for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pennylane Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pennylane-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Pennylane Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the Pennylane tile in the My Apps, this will redirect to Pennylane Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the Pennylane tile in the My Apps, this will redirect to Pennylane Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Peoplecart Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/peoplecart-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Peoplecart Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Peoplecart tile in the My Apps, this will redirect to Peoplecart Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Peoplecart tile in the My Apps, this will redirect to Peoplecart Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Perceptionunitedstates Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/perceptionunitedstates-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the UltiPro Perception for which you set up the SSO. -* You can use Microsoft My Apps. When you click the UltiPro Perception tile in the My Apps, you should be automatically signed in to the UltiPro Perception for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the UltiPro Perception tile in the My Apps, you should be automatically signed in to the UltiPro Perception for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Percolate Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/percolate-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Percolate for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Percolate tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Percolate for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Percolate tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Percolate for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Periscope Data Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/periscope-data-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Periscope Data Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Periscope Data tile in the My Apps, this will redirect to Periscope Data Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Periscope Data tile in the My Apps, this will redirect to Periscope Data Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Phenom Txm Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/phenom-txm-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Phenom TXM for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Phenom TXM tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Phenom TXM for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Phenom TXM tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Phenom TXM for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pinpoint Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pinpoint-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Pinpoint (SAML) Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Pinpoint (SAML) tile in the My Apps, this will redirect to Pinpoint (SAML) Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Pinpoint (SAML) tile in the My Apps, this will redirect to Pinpoint (SAML) Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Pksha Chatbot Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pksha-chatbot-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PKSHA Chatbot Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PKSHA Chatbot tile in the My Apps, this will redirect to PKSHA Chatbot Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PKSHA Chatbot tile in the My Apps, this will redirect to PKSHA Chatbot Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Planview Admin Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/planview-admin-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Planview Admin for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Planview Admin tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Planview Admin for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Planview Admin tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Planview Admin for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Planview Leankit Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/planview-leankit-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Planview LeanKit for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Planview LeanKit tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Planview LeanKit for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Planview LeanKit tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Planview LeanKit for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pluto Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pluto-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Pluto Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Pluto tile in the My Apps, this will redirect to Pluto Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Pluto tile in the My Apps, this will redirect to Pluto Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Policystat Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/policystat-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PolicyStat Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PolicyStat tile in the My Apps, this will redirect to PolicyStat Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PolicyStat tile in the My Apps, this will redirect to PolicyStat Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Postbeyond Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/postbeyond-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PostBeyond Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PostBeyond tile in the My Apps, this will redirect to PostBeyond Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PostBeyond tile in the My Apps, this will redirect to PostBeyond Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Predict360 Sso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/predict360-sso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Predict360 SSO for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Predict360 SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Predict360 SSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Predict360 SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Predict360 SSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Predictixordering Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/predictixordering-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Predictix Ordering Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Predictix Ordering tile in the My Apps, this will redirect to Predictix Ordering Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Predictix Ordering tile in the My Apps, this will redirect to Predictix Ordering Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Predictixpricereporting Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/predictixpricereporting-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Predictix Price Reporting Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Predictix Price Reporting tile in the My Apps, this will redirect to Predictix Price Reporting Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Predictix Price Reporting tile in the My Apps, this will redirect to Predictix Price Reporting Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Preset Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/preset-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Preset for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Preset tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Preset for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Preset tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Preset for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Printerlogic Saas Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/printerlogic-saas-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the PrinterLogic for which you set up the SSO. -* You can also use Microsoft My Apps to test the application in any mode. When you click the PrinterLogic tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the PrinterLogic for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can also use Microsoft My Apps to test the application in any mode. When you click the PrinterLogic tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the PrinterLogic for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Printix Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/printix-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Printix Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Printix tile in the My Apps, this will redirect to Printix Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Printix tile in the My Apps, this will redirect to Printix Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Proactis Rego Invoice Capture Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/proactis-rego-invoice-capture-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Proactis Rego Invoice Capture for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Proactis Rego Invoice Capture tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Proactis Rego Invoice Capture for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Proactis Rego Invoice Capture tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Proactis Rego Invoice Capture for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Proactis Rego Source To Contract Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/proactis-rego-source-to-contract-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Proactis Rego Source-to-Contract Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Proactis Rego Source-to-Contract tile in the My Apps, this will redirect to Proactis Rego Source-to-Contract Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Proactis Rego Source-to-Contract tile in the My Apps, this will redirect to Proactis Rego Source-to-Contract Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Proactis Rego Source To Pay Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/proactis-rego-source-to-pay-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Proactis Rego Source-to-Pay Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Proactis Rego Source-to-Pay tile in the My Apps, this will redirect to Proactis Rego Source-to-Pay Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Proactis Rego Source-to-Pay tile in the My Apps, this will redirect to Proactis Rego Source-to-Pay Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Profitco Saml App Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/profitco-saml-app-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Profit.co for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Profit.co tile in the My Apps, you should be automatically signed in to the Profit.co for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Profit.co tile in the My Apps, you should be automatically signed in to the Profit.co for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Projectplace Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/projectplace-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ProjectPlace for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ProjectPlace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProjectPlace for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ProjectPlace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProjectPlace for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Promaster Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/promaster-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ProMaster (by Inlogik) for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ProMaster (by Inlogik) tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProMaster (by Inlogik) for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ProMaster (by Inlogik) tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProMaster (by Inlogik) for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pronovos Ops Manager Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pronovos-ops-manager-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ProNovos Ops Manager for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ProNovos Ops Manager tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProNovos Ops Manager for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ProNovos Ops Manager tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ProNovos Ops Manager for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Proofpoint Ondemand Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/proofpoint-ondemand-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Proofpoint on Demand Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Proofpoint on Demand tile in the My Apps, this will redirect to Proofpoint on Demand Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Proofpoint on Demand tile in the My Apps, this will redirect to Proofpoint on Demand Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Proofpoint Security Awareness Training Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/proofpoint-security-awareness-training-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Proofpoint Security Awareness Training for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Proofpoint Security Awareness Training tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Proofpoint Security Awareness Training for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Proofpoint Security Awareness Training tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Proofpoint Security Awareness Training for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Pwc Identity Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pwc-identity-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PwC Identity Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PwC Identity tile in the My Apps, this will redirect to PwC Identity Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PwC Identity tile in the My Apps, this will redirect to PwC Identity Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pymetrics Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/pymetrics-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to pymetrics Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the pymetrics tile in the My Apps, this will redirect to pymetrics Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the pymetrics tile in the My Apps, this will redirect to pymetrics Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Qradar Soar Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/qradar-soar-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the QRadar SOAR for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the QRadar SOAR tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the QRadar SOAR for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the QRadar SOAR tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the QRadar SOAR for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Qreserve Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/qreserve-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the QReserve for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the QReserve tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the QReserve for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the QReserve tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the QReserve for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Qualaroo Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/qualaroo-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Qualaroo for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Qualaroo tile in the My Apps, you should be automatically signed in to the Qualaroo for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Qualaroo tile in the My Apps, you should be automatically signed in to the Qualaroo for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Quantum Workplace Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/quantum-workplace-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Quantum Workplace for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Quantum Workplace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Quantum Workplace for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Quantum Workplace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Quantum Workplace for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Questetra Bpm Suite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/questetra-bpm-suite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Questetra BPM Suite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Questetra BPM Suite tile in the My Apps, this will redirect to Questetra BPM Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Questetra BPM Suite tile in the My Apps, this will redirect to Questetra BPM Suite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rackspacesso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rackspacesso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Rackspace SSO for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Rackspace SSO tile in the My Apps, you should be automatically signed in to the Rackspace SSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Rackspace SSO tile in the My Apps, you should be automatically signed in to the Rackspace SSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). You can also use the Validate button in the Rackspace SSO Single sign-on settings:
active-directory	Radancys Employee Referrals Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/radancys-employee-referrals-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Radancy's Employee Referrals for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Radancy's Employee Referrals tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Radancy's Employee Referrals for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Radancy's Employee Referrals tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Radancy's Employee Referrals for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Radiant Iot Portal Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/radiant-iot-portal-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Radiant IOT Portal Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Radiant IOT Portal tile in the My Apps, this will redirect to Radiant IOT Portal Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Radiant IOT Portal tile in the My Apps, this will redirect to Radiant IOT Portal Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Raketa Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/raketa-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Raketa Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Raketa tile in the My Apps, this will redirect to Raketa Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Raketa tile in the My Apps, this will redirect to Raketa Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Real Links Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/real-links-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Real Links Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Real Links tile in the My Apps, this will redirect to Real Links Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Real Links tile in the My Apps, this will redirect to Real Links Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Recurly Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/recurly-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Recurly for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Recurly tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Recurly for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Recurly tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Recurly for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Redocly Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/redocly-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Redocly Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Redocly tile in the My Apps, this will redirect to Redocly Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Redocly tile in the My Apps, this will redirect to Redocly Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Redvector Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/redvector-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to RedVector Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the RedVector tile in the My Apps, this will redirect to RedVector Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the RedVector tile in the My Apps, this will redirect to RedVector Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Renraku Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/renraku-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to PHONE APPLI PEOPLE Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the PHONE APPLI PEOPLE tile in the My Apps, this will redirect to PHONE APPLI PEOPLE Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the PHONE APPLI PEOPLE tile in the My Apps, this will redirect to PHONE APPLI PEOPLE Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Reprints Desk Article Galaxy Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/reprints-desk-article-galaxy-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Reprints Desk - Article Galaxy for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Reprints Desk - Article Galaxy tile in the My Apps, you should be automatically signed in to the Reprints Desk - Article Galaxy for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Reprints Desk - Article Galaxy tile in the My Apps, you should be automatically signed in to the Reprints Desk - Article Galaxy for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Respondent Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/respondent-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Respondent for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Respondent tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Respondent for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Respondent tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Respondent for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Reviewsnap Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/reviewsnap-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Reviewsnap for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Reviewsnap tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Reviewsnap for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Reviewsnap tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Reviewsnap for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rightanswers Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rightanswers-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to RightAnswers Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the RightAnswers tile in the My Apps, this will redirect to RightAnswers Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the RightAnswers tile in the My Apps, this will redirect to RightAnswers Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Risecom Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/risecom-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Rise.com for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Rise.com tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Rise.com for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Rise.com tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Rise.com for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Riskware Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/riskware-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Riskware Sign-On URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Riskware tile in the My Apps, this will redirect to Riskware Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Riskware tile in the My Apps, this will redirect to Riskware Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rocketreach Sso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rocketreach-sso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the RocketReach SSO for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the RocketReach SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the RocketReach SSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the RocketReach SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the RocketReach SSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rolepoint Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rolepoint-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to RolePoint Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the RolePoint tile in the My Apps, this will redirect to RolePoint Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the RolePoint tile in the My Apps, this will redirect to RolePoint Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rootly Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rootly-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Rootly for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Rootly tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Rootly for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Rootly tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Rootly for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rsa Archer Suite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rsa-archer-suite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to RSA Archer Suite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the RSA Archer Suite tile in the My Apps, this will redirect to RSA Archer Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the RSA Archer Suite tile in the My Apps, this will redirect to RSA Archer Suite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Rstudio Connect Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/rstudio-connect-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the RStudio Connect SAML Authentication for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the RStudio Connect SAML Authentication tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the RStudio Connect SAML Authentication for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the RStudio Connect SAML Authentication tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the RStudio Connect SAML Authentication for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Runmyprocess Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/runmyprocess-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to RunMyProcess Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the RunMyProcess tile in the My Apps, this will redirect to RunMyProcess Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the RunMyProcess tile in the My Apps, this will redirect to RunMyProcess Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Safeconnect Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/safeconnect-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SafeConnect Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SafeConnect tile in the My Apps, this will redirect to SafeConnect Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SafeConnect tile in the My Apps, this will redirect to SafeConnect Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Safety Culture Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/safety-culture-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically logged in to SafetyCulture for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SafetyCulture tile in My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IdP mode, you should be automatically logged in to SafetyCulture for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SafetyCulture tile in My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IdP mode, you should be automatically logged in to SafetyCulture for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Saml Toolkit Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/saml-toolkit-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Azure AD SAML Toolkit Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Azure AD SAML Toolkit tile in the My Apps, this will redirect to Azure AD SAML Toolkit Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Azure AD SAML Toolkit tile in the My Apps, this will redirect to Azure AD SAML Toolkit Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sauce Labs Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sauce-labs-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Sauce Labs for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Sauce Labs tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Sauce Labs for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Sauce Labs tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Sauce Labs for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Scalex Enterprise Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/scalex-enterprise-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ScaleX Enterprise for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ScaleX Enterprise tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ScaleX Enterprise for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ScaleX Enterprise tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ScaleX Enterprise for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Scilife Azure Ad Sso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/scilife-azure-ad-sso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Scilife Azure AD SSO Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Scilife Azure AD SSO tile in the My Apps, this will redirect to Scilife Azure AD SSO Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Scilife Azure AD SSO tile in the My Apps, this will redirect to Scilife Azure AD SSO Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Sciquest Spend Director Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sciquest-spend-director-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SciQuest Spend Director Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SciQuest Spend Director tile in the My Apps, this will redirect to SciQuest Spend Director Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SciQuest Spend Director tile in the My Apps, this will redirect to SciQuest Spend Director Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Screencast Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/screencast-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Screencast-O-Matic Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Screencast-O-Matic tile in the My Apps, this will redirect to Screencast-O-Matic Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Screencast-O-Matic tile in the My Apps, this will redirect to Screencast-O-Matic Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Screensteps Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/screensteps-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to ScreenSteps Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the ScreenSteps tile in the My Apps, this will redirect to ScreenSteps Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ScreenSteps tile in the My Apps, this will redirect to ScreenSteps Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Scuba Analytics Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/scuba-analytics-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Scuba Analytics for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Scuba Analytics tile in the My Apps, you should be automatically signed in to the Scuba Analytics for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Scuba Analytics tile in the My Apps, you should be automatically signed in to the Scuba Analytics for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Seattletimessso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/seattletimessso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SeattleTimesSSO for which you set up the SSO. -* You can use Microsoft My Apps. When you click the SeattleTimesSSO tile in the My Apps, you should be automatically signed in to the SeattleTimesSSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SeattleTimesSSO tile in the My Apps, you should be automatically signed in to the SeattleTimesSSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Seculio Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/seculio-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Seculio for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Seculio tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Seculio for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Seculio tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Seculio for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Securedeliver Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/securedeliver-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SECURE DELIVER Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SECURE DELIVER tile in the My Apps, this will redirect to SECURE DELIVER Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SECURE DELIVER tile in the My Apps, this will redirect to SECURE DELIVER Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Securetransport Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/securetransport-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SecureTransport Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SecureTransport tile in the My Apps, this will redirect to SecureTransport Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SecureTransport tile in the My Apps, this will redirect to SecureTransport Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Sedgwickcms Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sedgwickcms-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Sedgwick CMS for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Sedgwick CMS tile in the My Apps, you should be automatically signed in to the Sedgwick CMS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Sedgwick CMS tile in the My Apps, you should be automatically signed in to the Sedgwick CMS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Seekout Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/seekout-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SeekOut for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SeekOut tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SeekOut for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SeekOut tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SeekOut for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sensoscientific Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sensoscientific-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SensoScientific Wireless Temperature Monitoring System for which you set up the SSO. -* You can use Microsoft My Apps. When you click the SensoScientific Wireless Temperature Monitoring System tile in the My Apps, you should be automatically signed in to the SensoScientific Wireless Temperature Monitoring System for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SensoScientific Wireless Temperature Monitoring System tile in the My Apps, you should be automatically signed in to the SensoScientific Wireless Temperature Monitoring System for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Servicessosafe Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/servicessosafe-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SoSafe for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SoSafe tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SoSafe for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SoSafe tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SoSafe for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Servusconnect Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/servusconnect-tutorial.md	You may test your Azure AD single sign-on configuration using one of the followi * Go to [ServusConnect Sign-on URL](https://app.servusconnect.com/) directly and initiate the login flow from there. See [Sign-on with SSO](#sign-on-with-sso), below. -* You can use Microsoft My Apps. When you click the ServusConnect tile in the My Apps, this will redirect to ServusConnect Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ServusConnect tile in the My Apps, this will redirect to ServusConnect Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Sign-on with SSO
active-directory	Settlingmusic Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/settlingmusic-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Settling music Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Settling music tile in the My Apps, this will redirect to Settling music Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Settling music tile in the My Apps, this will redirect to Settling music Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sevone Network Monitoring System Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sevone-network-monitoring-system-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SevOne Network Monitoring System (NMS) Sign-On URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SevOne Network Monitoring System (NMS) tile in the My Apps, this will redirect to SevOne Network Monitoring System (NMS) Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SevOne Network Monitoring System (NMS) tile in the My Apps, this will redirect to SevOne Network Monitoring System (NMS) Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sharefile Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sharefile-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Citrix ShareFile Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Citrix ShareFile tile in the My Apps, this will redirect to Citrix ShareFile Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Citrix ShareFile tile in the My Apps, this will redirect to Citrix ShareFile Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sharevault Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sharevault-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ShareVault for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ShareVault tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ShareVault for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ShareVault tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ShareVault for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Shiftplanning Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/shiftplanning-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Humanity Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Humanity tile in the My Apps, this will redirect to Humanity Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Humanity tile in the My Apps, this will redirect to Humanity Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Shiphazmat Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/shiphazmat-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ShipHazmat for which you set up the SSO. -* You can use Microsoft My Apps. When you click the ShipHazmat tile in the My Apps, you should be automatically signed in to the ShipHazmat for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ShipHazmat tile in the My Apps, you should be automatically signed in to the ShipHazmat for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Showpad Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/showpad-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Showpad Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Showpad tile in the My Apps, this will redirect to Showpad Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Showpad tile in the My Apps, this will redirect to Showpad Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Shucchonavi Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/shucchonavi-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Shuccho Navi Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Shuccho Navi tile in the My Apps, this will redirect to Shuccho Navi Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Shuccho Navi tile in the My Apps, this will redirect to Shuccho Navi Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Signagelive Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/signagelive-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Signagelive Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Signagelive tile in the My Apps, this will redirect to Signagelive Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Signagelive tile in the My Apps, this will redirect to Signagelive Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Signiant Media Shuttle Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/signiant-media-shuttle-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Signiant Media Shuttle Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Signiant Media Shuttle tile in the My Apps, this will redirect to Signiant Media Shuttle Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Signiant Media Shuttle tile in the My Apps, this will redirect to Signiant Media Shuttle Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Silverback Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/silverback-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Silverback Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Silverback tile in the My Apps, this will redirect to Silverback Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Silverback tile in the My Apps, this will redirect to Silverback Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Sketch Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sketch-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Sketch Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Sketch tile in the My Apps, this will redirect to Sketch Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Sketch tile in the My Apps, this will redirect to Sketch Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skillcast Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skillcast-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Skillcast Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Skillcast tile in the My Apps, this will redirect to Skillcast Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Skillcast tile in the My Apps, this will redirect to Skillcast Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skilljar Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skilljar-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Skilljar Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Skilljar tile in the My Apps, this will redirect to Skilljar Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Skilljar tile in the My Apps, this will redirect to Skilljar Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skills Workflow Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skills-workflow-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Skills Workflow Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Skills Workflow tile in the My Apps, this will redirect to Skills Workflow Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Skills Workflow tile in the My Apps, this will redirect to Skills Workflow Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skillsmanager Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skillsmanager-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Skills Manager for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Skills Manager tile in the My Apps, you should be automatically signed in to the Skills Manager for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Skills Manager tile in the My Apps, you should be automatically signed in to the Skills Manager for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skybreathe Analytics Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skybreathe-analytics-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Skybreathe┬« Analytics for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Skybreathe┬« Analytics tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Skybreathe┬« Analytics for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Skybreathe┬« Analytics tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Skybreathe┬« Analytics for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skydeskemail Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skydeskemail-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SkyDesk Email Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SkyDesk Email tile in the My Apps, this will redirect to SkyDesk Email Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SkyDesk Email tile in the My Apps, this will redirect to SkyDesk Email Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Skysite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/skysite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SKYSITE for which you set up the SSO. -* You can use Microsoft My Apps. When you click the SKYSITE tile in the My Apps, you should be automatically signed in to the SKYSITE for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SKYSITE tile in the My Apps, you should be automatically signed in to the SKYSITE for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smallimprovements Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smallimprovements-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Small Improvements Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Small Improvements tile in the My Apps, this will redirect to Small Improvements Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Small Improvements tile in the My Apps, this will redirect to Small Improvements Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smart360 Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smart360-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Smart360 Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Smart360 tile in the My Apps, this will redirect to Smart360 Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Smart360 tile in the My Apps, this will redirect to Smart360 Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smartfile Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smartfile-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SmartFile Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SmartFile tile in the My Apps, this will redirect to SmartFile Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SmartFile tile in the My Apps, this will redirect to SmartFile Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smarthr Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smarthr-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SmartHR Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SmartHR tile in the My Apps, this will redirect to SmartHR Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SmartHR tile in the My Apps, this will redirect to SmartHR Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smartkargo Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smartkargo-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SmartKargo Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SmartKargo tile in the My Apps, this will redirect to SmartKargo Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SmartKargo tile in the My Apps, this will redirect to SmartKargo Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Smartlpa Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/smartlpa-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SmartLPA Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SmartLPA tile in the My Apps, this will redirect to SmartLPA Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SmartLPA tile in the My Apps, this will redirect to SmartLPA Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Snackmagic Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/snackmagic-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Snackmagic for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Snackmagic tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Snackmagic for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Snackmagic tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Snackmagic for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Snowflake Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/snowflake-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Snowflake for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Snowflake tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Snowflake for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Snowflake tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Snowflake for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Soc Sst Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/soc-sst-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SOC SST for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SOC SST tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SOC SST for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SOC SST tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SOC SST for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Softeon Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/softeon-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Softeon WMS for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Softeon WMS tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Softeon WMS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Softeon WMS tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Softeon WMS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Soonr Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/soonr-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Soonr Workplace for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Soonr Workplace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Soonr Workplace for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Soonr Workplace tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Soonr Workplace for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Spedtrack Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/spedtrack-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SpedTrack for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SpedTrack tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SpedTrack for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SpedTrack tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SpedTrack for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Sso For Jama Connect Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/sso-for-jama-connect-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the SSO for Jama Connect┬« for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the SSO for Jama Connect┬« tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SSO for Jama Connect┬« for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the SSO for Jama Connect┬« tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the SSO for Jama Connect┬« for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Stackby Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/stackby-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Stackby for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Stackby tile in the My Apps, you should be automatically signed in to the Stackby for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Stackby tile in the My Apps, you should be automatically signed in to the Stackby for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Standard For Success Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/standard-for-success-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Standard for Success K-12 for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Standard for Success K-12 tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Standard for Success K-12 for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Standard for Success K-12 tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Standard for Success K-12 for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Starmind Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/starmind-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Starmind Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Starmind tile in the My Apps, this will redirect to Starmind Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Starmind tile in the My Apps, this will redirect to Starmind Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Stormboard Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/stormboard-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Stormboard for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Stormboard tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Stormboard for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Stormboard tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Stormboard for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Superannotate Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/superannotate-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SuperAnnotate Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SuperAnnotate tile in the My Apps, this will redirect to SuperAnnotate Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SuperAnnotate tile in the My Apps, this will redirect to SuperAnnotate Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Surfconext Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/surfconext-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SURFconext Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SURFconext tile in the My Apps, this will redirect to SURFconext Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SURFconext tile in the My Apps, this will redirect to SURFconext Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Surfsecureid Azure Mfa Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/surfsecureid-azure-mfa-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SURFsecureID - Azure MFA Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SURFsecureID - Azure MFA tile in the My Apps, this will redirect to SURFsecureID - Azure MFA Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SURFsecureID - Azure MFA tile in the My Apps, this will redirect to SURFsecureID - Azure MFA Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Swit Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/swit-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Swit Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Swit tile in the My Apps, this will redirect to Swit Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Swit tile in the My Apps, this will redirect to Swit Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Synchronet Click Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/synchronet-click-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to SynchroNet CLICK Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the SynchroNet CLICK tile in the My Apps, this will redirect to SynchroNet CLICK Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the SynchroNet CLICK tile in the My Apps, this will redirect to SynchroNet CLICK Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Syniverse Customer Portal Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/syniverse-customer-portal-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Syniverse Customer Portal for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Syniverse Customer Portal tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Syniverse Customer Portal for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Syniverse Customer Portal tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Syniverse Customer Portal for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Talon Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/talon-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Talon for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Talon tile in the My Apps, you should be automatically signed in to the Talon for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Talon tile in the My Apps, you should be automatically signed in to the Talon for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Tango Reserve Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tango-reserve-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Tango Reserve by AgilQuest (EU Instance) for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Tango Reserve by AgilQuest (EU Instance) tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Tango Reserve by AgilQuest (EU Instance) for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Tango Reserve by AgilQuest (EU Instance) tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Tango Reserve by AgilQuest (EU Instance) for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tanium Sso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tanium-sso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Tanium SSO for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Tanium SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Tanium SSO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Tanium SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Tanium SSO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Tasc Beta Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tasc-beta-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TASC (beta) for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TASC (beta) tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TASC (beta) for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TASC (beta) tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TASC (beta) for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Teamseer Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/teamseer-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TeamSeer Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TeamSeer tile in the My Apps, this will redirect to TeamSeer Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TeamSeer tile in the My Apps, this will redirect to TeamSeer Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Teamslide Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/teamslide-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TeamSlide Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TeamSlide tile in the My Apps, this will redirect to TeamSlide Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TeamSlide tile in the My Apps, this will redirect to TeamSlide Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Teamsticker By Communitio Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/teamsticker-by-communitio-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TeamSticker by Communitio Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TeamSticker by Communitio tile in the My Apps, this will redirect to TeamSticker by Communitio Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TeamSticker by Communitio tile in the My Apps, this will redirect to TeamSticker by Communitio Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tencent Cloud Idaas Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tencent-cloud-idaas-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TencentCloud IDaaS for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TencentCloud IDaaS tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TencentCloud IDaaS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TencentCloud IDaaS tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TencentCloud IDaaS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Terratrue Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/terratrue-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TerraTrue for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TerraTrue tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TerraTrue for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TerraTrue tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TerraTrue for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tesma Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tesma-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the tesma for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the tesma tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the tesma for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the tesma tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the tesma for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Testim Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/testim-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Testim for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Testim tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Testim for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Testim tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Testim for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Textline Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/textline-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Textline for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Textline tile in the My Apps, you should be automatically signed in to the Textline for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Textline tile in the My Apps, you should be automatically signed in to the Textline for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	The Funding Portal Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/the-funding-portal-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to The Funding Portal Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the The Funding Portal tile in the My Apps, this will redirect to The Funding Portal Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the The Funding Portal tile in the My Apps, this will redirect to The Funding Portal Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Theom Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/theom-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Theom Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Theom tile in the My Apps, this will redirect to Theom Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Theom tile in the My Apps, this will redirect to Theom Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Thirdlight Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/thirdlight-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to ThirdLight Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the ThirdLight tile in the My Apps, this will redirect to ThirdLight Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ThirdLight tile in the My Apps, this will redirect to ThirdLight Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Threatq Platform Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/threatq-platform-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to ThreatQ Platform Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the ThreatQ Platform tile in the My Apps, this will redirect to ThreatQ Platform Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the ThreatQ Platform tile in the My Apps, this will redirect to ThreatQ Platform Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Tidemark Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tidemark-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Tidemark Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Tidemark tile in the My Apps, this will redirect to Tidemark Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Tidemark tile in the My Apps, this will redirect to Tidemark Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tigergraph Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tigergraph-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TigerGraph for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TigerGraph tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TigerGraph for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TigerGraph tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TigerGraph for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Timelive Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/timelive-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TimeLive Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TimeLive tile in the My Apps, this will redirect to TimeLive Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TimeLive tile in the My Apps, this will redirect to TimeLive Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Timeoffmanager Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/timeoffmanager-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TimeOffManager for which you set up the SSO. -* You can use Microsoft My Apps. When you click the TimeOffManager tile in the My Apps, you should be automatically signed in to the TimeOffManager for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TimeOffManager tile in the My Apps, you should be automatically signed in to the TimeOffManager for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Timetabling Solutions Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/timetabling-solutions-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Timetabling Solutions Sign-On URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Timetabling Solutions tile in the My Apps, this will redirect to Timetabling Solutions Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Timetabling Solutions tile in the My Apps, this will redirect to Timetabling Solutions Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Timetrack Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/timetrack-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TimeTrack for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TimeTrack tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TimeTrack for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TimeTrack tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TimeTrack for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tinfoil Security Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tinfoil-security-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TINFOIL SECURITY for which you set up the SSO. -* You can use Microsoft My Apps. When you click the TINFOIL SECURITY tile in the My Apps, you should be automatically signed in to the TINFOIL SECURITY for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TINFOIL SECURITY tile in the My Apps, you should be automatically signed in to the TINFOIL SECURITY for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tivitz Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tivitz-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TiViTz Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TiViTz tile in the My Apps, this will redirect to TiViTz Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TiViTz tile in the My Apps, this will redirect to TiViTz Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tonicdm Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tonicdm-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TonicDM for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TonicDM tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TonicDM for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TonicDM tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TonicDM for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Torii Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/torii-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Torii for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Torii tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Torii for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Torii tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Torii for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tracker Software Technologies Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tracker-software-technologies-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Tracker Software Technologies for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Tracker Software Technologies tile in the My Apps, you should be automatically signed in to the Tracker Software Technologies for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Tracker Software Technologies tile in the My Apps, you should be automatically signed in to the Tracker Software Technologies for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Trackvia Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/trackvia-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TrackVia for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the TrackVia tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TrackVia for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the TrackVia tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the TrackVia for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Training Platform Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/training-platform-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Training Platform for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Training Platform tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Training Platform for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Training Platform tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Training Platform for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tranxfer Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tranxfer-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Tranxfer Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Tranxfer tile in the My Apps, this will redirect to Tranxfer Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Tranxfer tile in the My Apps, this will redirect to Tranxfer Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Trelica Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/trelica-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Trelica for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Trelica tile in the My Apps, you should be automatically signed in to the Trelica for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Trelica tile in the My Apps, you should be automatically signed in to the Trelica for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tripwire Enterprise Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tripwire-enterprise-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Tripwire Enterprise for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Tripwire Enterprise tile in the My Apps, you should be automatically signed in to the Tripwire Enterprise for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Tripwire Enterprise tile in the My Apps, you should be automatically signed in to the Tripwire Enterprise for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Trunarrative Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/trunarrative-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to TruNarrative Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the TruNarrative tile in the My Apps, this will redirect to TruNarrative Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TruNarrative tile in the My Apps, this will redirect to TruNarrative Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Tvu Service Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/tvu-service-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the TVU Service for which you set up the SSO. -* You can use Microsoft My Apps. When you click the TVU Service tile in the My Apps, you should be automatically signed in to the TVU Service for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the TVU Service tile in the My Apps, you should be automatically signed in to the TVU Service for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Twic Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/twic-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Twic for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Twic tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Twic for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Twic tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Twic for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Uber Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/uber-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Uber for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Uber tile in the My Apps, you should be automatically signed in to the Uber for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Uber tile in the My Apps, you should be automatically signed in to the Uber for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Udemy Business Saml Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/udemy-business-saml-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Udemy Business SAML Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Udemy Business SAML tile in the My Apps, this will redirect to Udemy Business SAML Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Udemy Business SAML tile in the My Apps, this will redirect to Udemy Business SAML Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Unite Us Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/unite-us-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Unite Us for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Unite Us tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Unite Us for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Unite Us tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Unite Us for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Us Bank Prepaid Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/us-bank-prepaid-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the U.S. Bank Prepaid for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the U.S. Bank Prepaid tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the U.S. Bank Prepaid for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the U.S. Bank Prepaid tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the U.S. Bank Prepaid for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Userecho Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/userecho-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to UserEcho Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the UserEcho tile in the My Apps, this will redirect to UserEcho Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the UserEcho tile in the My Apps, this will redirect to UserEcho Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Usertesting Saml Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/usertesting-saml-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the UserTesting for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the UserTesting tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the UserTesting for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the UserTesting tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the UserTesting for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Userzoom Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/userzoom-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the UserZoom for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the UserZoom tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the UserZoom for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the UserZoom tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the UserZoom for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	V Client Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/v-client-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the V-Client for which you set up the SSO. -* You can use Microsoft My Apps. When you click the V-Client tile in the My Apps, you should be automatically signed in to the V-Client for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the V-Client tile in the My Apps, you should be automatically signed in to the V-Client for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Valence Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/valence-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Valence Security Platform for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Valence Security Platform tile in the My Apps, you should be automatically signed in to the Valence Security Platform for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Valence Security Platform tile in the My Apps, you should be automatically signed in to the Valence Security Platform for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Valid8me Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/valid8me-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the valid8Me for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the valid8Me tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the valid8Me for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the valid8Me tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the valid8Me for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vault Platform Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vault-platform-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Vault Platform for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Vault Platform tile in the My Apps, you should be automatically signed in to the Vault Platform for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Vault Platform tile in the My Apps, you should be automatically signed in to the Vault Platform for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vbrick Rev Cloud Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vbrick-rev-cloud-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Vbrick Rev Cloud Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Vbrick Rev Cloud tile in the My Apps, this will redirect to Vbrick Rev Cloud Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Vbrick Rev Cloud tile in the My Apps, this will redirect to Vbrick Rev Cloud Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Vecos Releezme Locker Management System Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vecos-releezme-locker-management-system-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to VECOS Releezme Locker management system Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the VECOS Releezme Locker management system tile in the My Apps, this will redirect to VECOS Releezme Locker management system Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the VECOS Releezme Locker management system tile in the My Apps, this will redirect to VECOS Releezme Locker management system Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Veda Cloud Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/veda-cloud-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to VEDA Cloud Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the VEDA Cloud tile in the My Apps, this will redirect to VEDA Cloud Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the VEDA Cloud tile in the My Apps, this will redirect to VEDA Cloud Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Venafi Control Plane Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/venafi-control-plane-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Venafi Control Plane - Datacenter for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Venafi Control Plane - Datacenter tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Venafi Control Plane - Datacenter for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Venafi Control Plane - Datacenter tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Venafi Control Plane - Datacenter for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Vera Suite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vera-suite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Vera Suite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Vera Suite tile in the My Apps, this will redirect to Vera Suite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Vera Suite tile in the My Apps, this will redirect to Vera Suite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Vergesense Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vergesense-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the VergeSense for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the VergeSense tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the VergeSense for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the VergeSense tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the VergeSense for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Verme Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/verme-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Verme for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Verme tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Verme for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Verme tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Verme for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Veza Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/veza-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Veza for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Veza tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Veza for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Veza tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Veza for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vibehcm Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vibehcm-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Vibe HCM for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Vibe HCM tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Vibe HCM for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Vibe HCM tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Vibe HCM for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vida Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vida-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to VIDA Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the VIDA tile in the My Apps, this will redirect to VIDA Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the VIDA tile in the My Apps, this will redirect to VIDA Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Virtual Risk Manager Usa Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/virtual-risk-manager-usa-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Virtual Risk Manager - USA for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Virtual Risk Manager - USA tile in the My Apps, you should be automatically signed in to the Virtual Risk Manager - USA for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Virtual Risk Manager - USA tile in the My Apps, you should be automatically signed in to the Virtual Risk Manager - USA for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Visibly Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/visibly-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Visibly Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Visibly tile in the My Apps, this will redirect to Visibly Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Visibly tile in the My Apps, this will redirect to Visibly Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Visitly Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/visitly-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click Test this application in Azure portal and you should be automatically signed in to the Visitly for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Visitly tile in the My Apps, you should be automatically signed in to the Visitly for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Visitly tile in the My Apps, you should be automatically signed in to the Visitly for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Visitorg Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/visitorg-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Visit.org for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Visit.org tile in the My Apps, you should be automatically signed in to the Visit.org for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Visit.org tile in the My Apps, you should be automatically signed in to the Visit.org for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vmware Identity Service Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vmware-identity-service-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the VMware Identity Service for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the VMware Identity Service tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the VMware Identity Service for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the VMware Identity Service tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the VMware Identity Service for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Vocoli Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vocoli-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Vocoli for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Vocoli tile in the My Apps, you should be automatically signed in to the Vocoli for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Vocoli tile in the My Apps, you should be automatically signed in to the Vocoli for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vxmaintain Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vxmaintain-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the vxMaintain for which you set up the SSO. -* You can use Microsoft My Apps. When you click the vxMaintain tile in the My Apps, you should be automatically signed in to the vxMaintain for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the vxMaintain tile in the My Apps, you should be automatically signed in to the vxMaintain for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Vyond Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/vyond-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Vyond for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Vyond tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Vyond for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Vyond tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Vyond for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Wan Sign Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wan-sign-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the WAN-Sign for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the WAN-Sign tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WAN-Sign for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the WAN-Sign tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WAN-Sign for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Watch By Colors Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/watch-by-colors-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Watch by Colors for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Watch by Colors tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Watch by Colors for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Watch by Colors tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Watch by Colors for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Wayleadr Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wayleadr-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Wayleadr for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Wayleadr tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Wayleadr for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Wayleadr tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Wayleadr for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Waywedo Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/waywedo-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Way We Do Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Way We Do tile in the My Apps, this will redirect to Way We Do Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Way We Do tile in the My Apps, this will redirect to Way We Do Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Webce Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/webce-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to WebCE Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the WebCE tile in the My Apps, this will redirect to WebCE Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the WebCE tile in the My Apps, this will redirect to WebCE Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Webtma Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/webtma-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the WebTMA for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the WebTMA tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WebTMA for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the WebTMA tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WebTMA for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Wedo Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wedo-tutorial.md	In this section, you test your Azure AD single sign-on configuration with the fo * Click Test this application in Azure portal and you should be automatically signed in to the WEDO for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the WEDO tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WEDO for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the WEDO tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WEDO for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Weekdone Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/weekdone-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Weekdone for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Weekdone tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Weekdone for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Weekdone tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Weekdone for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Whos On Location Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/whos-on-location-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to WhosOnLocation Sign-On URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the WhosOnLocation tile in the My Apps, this will redirect to WhosOnLocation Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the WhosOnLocation tile in the My Apps, this will redirect to WhosOnLocation Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Whosoff Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/whosoff-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the WhosOff for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the WhosOff tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WhosOff for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the WhosOff tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the WhosOff for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Wikispaces Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wikispaces-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Wikispaces Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Wikispaces tile in the My Apps, this will redirect to Wikispaces Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Wikispaces tile in the My Apps, this will redirect to Wikispaces Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Windchill Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/windchill-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow 1. Click on Test this application in Azure portal and you should be automatically signed in to the Windchill for which you set up the SSO. -1. You can also use Microsoft My Apps to test the application in any mode. When you click the Windchill tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Windchill for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +1. You can also use Microsoft My Apps to test the application in any mode. When you click the Windchill tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Windchill for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Wisdom By Invictus Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wisdom-by-invictus-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Wisdom by Invictus for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Wisdom by Invictus tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Wisdom by Invictus for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Wisdom by Invictus tile in the My Apps, if configured in SP mode you would be redirected to the application sign-on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Wisdom by Invictus for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Wistia Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wistia-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Wistia Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Wistia tile in the My Apps, this will redirect to Wistia Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Wistia tile in the My Apps, this will redirect to Wistia Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Wiz Sso Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/wiz-sso-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Wiz SSO Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Wiz SSO tile in the My Apps, this will redirect to Wiz SSO Sign-On URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Wiz SSO tile in the My Apps, this will redirect to Wiz SSO Sign-On URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workgrid Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workgrid-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Workgrid Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Workgrid tile in the My Apps, this will redirect to Workgrid Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Workgrid tile in the My Apps, this will redirect to Workgrid Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workhub Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workhub-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to workhub Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the workhub tile in the My Apps, this will redirect to workhub Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the workhub tile in the My Apps, this will redirect to workhub Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workpath Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workpath-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Workpath for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Workpath tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Workpath for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Workpath tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Workpath for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workrite Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workrite-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Workrite Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Workrite tile in the My Apps, this will redirect to Workrite Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Workrite tile in the My Apps, this will redirect to Workrite Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workteam Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workteam-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Workteam for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the Workteam tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Workteam for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the Workteam tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Workteam for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Workware Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/workware-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Workware for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Workware tile in the My Apps, you should be automatically signed in to the Workware for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Workware tile in the My Apps, you should be automatically signed in to the Workware for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Worthix App Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/worthix-app-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Worthix App for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Worthix App tile in the My Apps, you should be automatically signed in to the Worthix App for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Worthix App tile in the My Apps, you should be automatically signed in to the Worthix App for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Xcarrier Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/xcarrier-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the xCarrier┬« for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the xCarrier┬« tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the xCarrier┬« for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the xCarrier┬« tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the xCarrier┬« for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	You At College Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/you-at-college-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to YOU at College Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you select the YOU at College tile in the My Apps, this will redirect to YOU at College Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you select the YOU at College tile in the My Apps, this will redirect to YOU at College Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Additional resources
active-directory	Yuhu Property Management Platform Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/yuhu-property-management-platform-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Yuhu Property Management Platform Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Yuhu Property Management Platform tile in the My Apps, this will redirect to Yuhu Property Management Platform Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Yuhu Property Management Platform tile in the My Apps, this will redirect to Yuhu Property Management Platform Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zdiscovery Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zdiscovery-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ZDiscovery for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ZDiscovery tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ZDiscovery for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ZDiscovery tile in the My Apps, if configured in SP mode you would be redirected to the application Sign-On page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ZDiscovery for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zengine Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zengine-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zengine Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zengine tile in the My Apps, this will redirect to Zengine Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zengine tile in the My Apps, this will redirect to Zengine Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zenqms Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zenqms-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the ZenQMS for which you set up the SSO. -You can also use Microsoft My Apps to test the application in any mode. When you click the ZenQMS tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ZenQMS for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +You can also use Microsoft My Apps to test the application in any mode. When you click the ZenQMS tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the ZenQMS for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zero Networks Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zero-networks-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zero Networks Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zero Networks tile in the My Apps, this will redirect to Zero Networks Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zero Networks tile in the My Apps, this will redirect to Zero Networks Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps).
active-directory	Zest Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zest-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Click on Test this application in Azure portal and you should be automatically signed in to the Zest for which you set up the SSO. -* You can use Microsoft My Apps. When you click the Zest tile in the My Apps, you should be automatically signed in to the Zest for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zest tile in the My Apps, you should be automatically signed in to the Zest for which you set up the SSO. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zola Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zola-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zola Sign on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zola tile in the My Apps, this will redirect to Zola Sign on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zola tile in the My Apps, this will redirect to Zola Sign on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zscaler Beta Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zscaler-beta-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zscaler Beta Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zscaler Beta tile in the My Apps, this will redirect to Zscaler Beta Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zscaler Beta tile in the My Apps, this will redirect to Zscaler Beta Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zscaler Two Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zscaler-two-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zscaler Two Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zscaler Two tile in the My Apps, this will redirect to Zscaler Two Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zscaler Two tile in the My Apps, this will redirect to Zscaler Two Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zscaler Zscloud Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zscaler-zscloud-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zscaler ZSCloud Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zscaler ZSCloud tile in the My Apps, this will redirect to Zscaler ZSCloud Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zscaler ZSCloud tile in the My Apps, this will redirect to Zscaler ZSCloud Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Zwayam Tutorial	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/saas-apps/zwayam-tutorial.md	In this section, you test your Azure AD single sign-on configuration with follow * Go to Zwayam Sign-on URL directly and initiate the login flow from there. -* You can use Microsoft My Apps. When you click the Zwayam tile in the My Apps, this will redirect to Zwayam Sign-on URL. For more information about the My Apps, see [Introduction to the My Apps](../user-help/my-apps-portal-end-user-access.md). +* You can use Microsoft My Apps. When you click the Zwayam tile in the My Apps, this will redirect to Zwayam Sign-on URL. For more information, see [Azure AD My Apps](/azure/active-directory/manage-apps/end-user-experiences#azure-ad-my-apps). ## Next steps
active-directory	Pci Dss Guidance	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/active-directory/standards/pci-dss-guidance.md	# Azure Active Directory PCI-DSS guidance -The Payment Card Industry Security Standards Council (PCI SSC) is responsible for developing and promoting data security standards and resources, including the Payment Card Industry Data Security Standard (PCI-DSS), to ensure the security of payment transactions. To achieve PCI compliance, organizations using Azure Active Directory (Azure AD) can refer to guidance in this document. However, it is the responsibility of the organizations to ensure their PCI compliance. Their IT teams, SecOps teams, and Solutions Architects are responsible for creating and maintaining secure systems, products, and networks that handle, process, and store payment card information. +The Payment Card Industry Security Standards Council (PCI SSC) is responsible for developing and promoting data security standards and resources, including the Payment Card Industry Data Security Standard (PCI-DSS), to ensure the security of payment transactions. To achieve PCI compliance, organizations using Azure Active Directory (Azure AD) can refer to guidance in this document. However, it's the responsibility of the organizations to ensure their PCI compliance. Their IT teams, SecOps teams, and Solutions Architects are responsible for creating and maintaining secure systems, products, and networks that handle, process, and store payment card information. -While Azure AD helps meet some PCI-DSS control requirements, and provides modern identity and access protocols for cardholder data environment (CDE) resources, it should not be the sole mechanism for protecting cardholder data. Therefore, review this document set and all PCI-DSS requirements to establish a comprehensive security program that preserves customer trust. For a complete list of requirements, please visit the official PCI Security Standards Council website at pcisecuritystandards.org: [Official PCI Security Standards Council Site](https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf) +While Azure AD helps meet some PCI-DSS control requirements, and provides modern identity and access protocols for cardholder data environment (CDE) resources, it shouldn't be the sole mechanism for protecting cardholder data. Therefore, review this document set and all PCI-DSS requirements to establish a comprehensive security program that preserves customer trust. For a complete list of requirements, visit the official PCI Security Standards Council website at pcisecuritystandards.org: [Official PCI Security Standards Council Site](https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf) ## PCI requirements for controls -The global PCI-DSS v4.0 establishes a baseline of technical and operational standards for protecting account data. It ΓÇ£was developed to encourage and enhance payment card account data security and facilitate the broad adoption of consistent data security measures, globally. It provides a baseline of technical and operational requirements designed to protect account data. While specifically designed to focus on environments with payment card account data, PCI-DSS can also be used to protect against threats and secure other elements in the payment ecosystem.ΓÇ¥ +The global PCI-DSS v4.0 establishes a baseline of technical and operational standards for protecting account data. It "was developed to encourage and enhance payment card account data security and facilitate the broad adoption of consistent data security measures, globally. It provides a baseline of technical and operational requirements designed to protect account data. While designed to focus on environments with payment card account data, PCI-DSS can also be used to protect against threats and secure other elements in the payment ecosystem." ## Azure AD configuration and PCI-DSS PCI-DSS requirements 3, 4, 9, and 12 aren't addressed or met by \|PCI Data Security Standard - High Level Overview\|Azure AD recommended PCI-DSS controls\| \|-\|-\| -\|Build and Maintain Secure Network and Systems\|[1. Install and Maintain Network Security Controls]() </br> [2. Apply Secure Configurations to All System Components]()\| +\|Build and Maintain Secure Network and Systems\|[1. Install and Maintain Network Security Controls](pci-requirement-1.md) </br> [2. Apply Secure Configurations to All System Components](pci-requirement-2.md)\| \|Protect Account Data\|3. Protect Stored Account Data </br> 4. Protect Cardholder Data with Strong Cryptography During Transmission Over Public Networks\| -\|Maintain a Vulnerability Management Program\|[5. Protect All Systems and Networks from Malicious Software]() </br> [6. Develop and Maintain Secure Systems and Software]()\| -\|Implement Strong Access Control Measures\|[7. Restrict Access to System Components and Cardholder Data by Business Need to Know]() </br> [8. Identify and Authenticate Access to System Components]() </br> 9. Restrict Physical Access to System Components and Cardholder Data\| -\|Regularly Monitor and Test Networks\|[10. Log and Monitor All Access to System Components and Cardholder Data]() </br> [11. Test Security of Systems and Networks Regularly]()\| +\|Maintain a Vulnerability Management Program\|[5. Protect All Systems and Networks from Malicious Software](pci-requirement-5.md) </br> [6. Develop and Maintain Secure Systems and Software](pci-requirement-6.md)\| +\|Implement Strong Access Control Measures\|[7. Restrict Access to System Components and Cardholder Data by Business Need to Know](pci-requirement-7.md) </br> [8. Identify and Authenticate Access to System Components](pci-requirement-8.md) </br> 9. Restrict Physical Access to System Components and Cardholder Data\| +\|Regularly Monitor and Test Networks\|[10. Log and Monitor All Access to System Components and Cardholder Data](pci-requirement-10.md) </br> [11. Test Security of Systems and Networks Regularly](pci-requirement-11.md)\| \|Maintain an Information Security Policy\|12. Support Information Security with Organizational Policies and Programs\| ## PCI-DSS applicability CHD consists of: SAD consists of security-related information used to authenticate cardholders and/or authorize payment card transactions. SAD includes, but isn't limited to: * Full track data - magnetic stripe or chip equivalent -* Card verification codes/values - also referred to as the card validation code (CVC), or value (CVV). ItΓÇÖs the three- or four-digit value on the front or back of the payment card. ItΓÇÖs also referred to as CAV2, CVC2, CVN2, CVV2 or CID, determined by the participating payment brands (PPB). +* Card verification codes/values - also referred to as the card validation code (CVC), or value (CVV). It's the three- or four-digit value on the front or back of the payment card. It's also referred to as CAV2, CVC2, CVN2, CVV2 or CID, determined by the participating payment brands (PPB). * PIN - personal identification number * PIN blocks - an encrypted representation of the PIN used in a debit or credit card transaction. It ensures the secure transmission of sensitive information during a transaction Protecting the CDE is essential to the security and confidentiality of customer PCI audit scope relates to the systems, networks, and processes in the storage, processing, or transmission of CHD and/or SAD. If Account Data is stored, processed, or transmitted in a cloud environment, PCI-DSS applies to that environment and compliance typically involves validation of the cloud environment and the usage of it. There are five fundamental elements in scope for a PCI audit: -* Cardholder data environment (CDE) - the area where CHD, and/or SAD, is stored, processed, or transmitted. It includes an organizationΓÇÖs components that touch CHD, such as networks, and network components, databases, servers, applications, and payment terminals. +* Cardholder data environment (CDE) - the area where CHD, and/or SAD, is stored, processed, or transmitted. It includes an organization's components that touch CHD, such as networks, and network components, databases, servers, applications, and payment terminals. * People - with access to the CDE, such as employees, contractors, and third-party service providers, are in the scope of a PCI audit. * Processes - that involve CHD, such as authorization, authentication, encryption and storage of account data in any format, are within the scope of a PCI audit. * Technology - that processes, stores, or transmits CHD, including hardware such as printers, and multi-function devices that scan, print and fax, end-user devices such as computers, laptops workstations, administrative workstations, tablets and mobile devices, software, and other IT systems, are in the scope of a PCI audit. -* System components ΓÇô that might not store, process, or transmit CHD/SAD but have unrestricted connectivity to system components that store, process, or transmit CHD/SAD, or that could effect the security of the CDE. +* System components ΓÇô that might not store, process, or transmit CHD/SAD but have unrestricted connectivity to system components that store, process, or transmit CHD/SAD, or that could affect the security of the CDE. If PCI scope is minimized, organizations can effectively reduce the effects of security incidents and lower the risk of data breaches. Segmentation can be a valuable strategy for reducing the size of the PCI CDE, resulting in reduced compliance costs and overall benefits for the organization including but not limited to: If PCI scope is minimized, organizations can effectively reduce the effects of s ## Strategies to reduce PCI audit scope -An organizationΓÇÖs definition of its CDE determines PCI audit scope. Organizations document and communicate this definition to the PCI-DSS Qualified Security Assessor (QSA) performing the audit. The QSA assesses controls for the CDE to determine compliance. +An organization's definition of its CDE determines PCI audit scope. Organizations document and communicate this definition to the PCI-DSS Qualified Security Assessor (QSA) performing the audit. The QSA assesses controls for the CDE to determine compliance. Adherence to PCI standards and use of effective risk mitigation helps businesses protect customer personal and financial data, which maintains trust in their operations. The following section outlines strategies to reduce risk in PCI audit scope. ### Tokenization With ongoing processes, organizations respond effectively to changes in the regu ### Implement strong security for shared infrastructure -Typically, web services such as Azure, have a shared infrastructure wherein customer data might be stored on the same physical server or data storage device. This scenario creates the risk of unauthorized customers accessing data they donΓÇÖt own, and the risk of malicious actors targeting the shared infrastructure. Azure AD security features help mitigate risks associated with shared infrastructure: +Typically, web services such as Azure, have a shared infrastructure wherein customer data might be stored on the same physical server or data storage device. This scenario creates the risk of unauthorized customers accessing data they don't own, and the risk of malicious actors targeting the shared infrastructure. Azure AD security features help mitigate risks associated with shared infrastructure: * User authentication to network access technologies that support modern authentication protocols: virtual private network (VPN), remote desktop, and network access points. * Access control policies that enforce strong authentication methods and device compliance based on signals such as user context, device, location, and risk. Implement accurate logging and monitoring to detect, and respond to, security in Learn more: -ΓÇó [What are Azure AD reports?](../reports-monitoring/overview-reports.md) -ΓÇó [Azure AD built-in roles](../roles/permissions-reference.md) +* [What are Azure AD reports?](../reports-monitoring/overview-reports.md) +* [Azure AD built-in roles](../roles/permissions-reference.md) ### Multi-application environments: host outside the CDE
ai-services	Background Removal	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-services/computer-vision/how-to/background-removal.md	Start by creating a [VisionServiceOptions](/python/api/azure-ai-vision/azure.ai. [!code-python[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/python/image-analysis/how-to/main.py?name=vision_service_options)] +#### [Java](#tab/java) + +Start by creating a [VisionServiceOptions](/java/api/com.azure.ai.vision.common.visionserviceoptions) object using one of the constructors. For example: + +[!code-java[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/java/image-analysis/how-to/ImageAnalysis.java?name=vision_service_options)] + #### [C++](#tab/cpp) At the start of your code, use one of the static constructor methods [VisionServiceOptions::FromEndpoint](/cpp/cognitive-services/vision/service-visionserviceoptions#fromendpoint-1) to create a VisionServiceOptions object. For example: The code in this guide uses remote images referenced by URL. You may want to try Create a new VisionSource object from the URL of the image you want to analyze, using the static constructor [VisionSource.FromUrl](/dotnet/api/azure.ai.vision.common.visionsource.fromurl). -VisionSource implements IDisposable, therefore create the object with a using statement or explicitly call Dispose method after analysis completes. - [!code-csharp[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/csharp/image-analysis/how-to/program.cs?name=vision_source)] +VisionSource implements IDisposable, therefore create the object with a using statement or explicitly call Dispose method after analysis completes. + > [!TIP] -> You can also analyze a local image by passing in the full-path image file name (see [VisionSource.FromFile](/dotnet/api/azure.ai.vision.common.visionsource.fromfile)), or by copying the image into the SDK's input buffer (see [VisionSource.FromImageSourceBuffer](/dotnet/api/azure.ai.vision.common.visionsource.fromimagesourcebuffer)) +> You can also analyze a local image by passing in the full-path image file name (see [VisionSource.FromFile](/dotnet/api/azure.ai.vision.common.visionsource.fromfile)), or by copying the image into the SDK's input buffer (see [VisionSource.FromImageSourceBuffer](/dotnet/api/azure.ai.vision.common.visionsource.fromimagesourcebuffer)). For more details, see [Call the Analyze API](./call-analyze-image-40.md?pivots=programming-language-csharp#select-the-image-to-analyze). #### [Python](#tab/python) In your script, create a new [VisionSource](/python/api/azure-ai-vision/azure.ai [!code-python[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/python/image-analysis/how-to/main.py?name=vision_source)] > [!TIP] -> You can also analyze a local image by passing in the full-path image file name to the VisionSource constructor instead of the image URL (see argument name filename). Alternatively, you can analyze an image in a memory buffer by constructing VisionSource using the argument image_source_buffer. +> You can also analyze a local image by passing in the full-path image file name to the VisionSource constructor instead of the image URL (see argument name filename). Alternatively, you can analyze an image in a memory buffer by constructing VisionSource using the argument image_source_buffer. For more details, see [Call the Analyze API](./call-analyze-image-40.md?pivots=programming-language-python#select-the-image-to-analyze). + +#### [Java](#tab/java) + +Create a new VisionSource object from the URL of the image you want to analyze, using the static constructor [VisionSource.fromUrl](/java/api/com.azure.ai.vision.common.visionsource#com-azure-ai-vision-common-visionsource-fromurl(java-net-url)). + +[!code-java[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/java/image-analysis/how-to/ImageAnalysis.java?name=vision_source)] + +VisionSource implements AutoCloseable, therefore create the object in a try-with-resources block, or explicitly call the close method on this object when you're done analyzing the image. + +> [!TIP] +> You can also analyze a local image by passing in the full-path image file name (see [VisionSource.fromFile](/jav?pivots=programming-language-java#select-the-image-to-analyze). #### [C++](#tab/cpp) Create a new VisionSource object from the URL of the image you want to analy [!code-cpp[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/cpp/image-analysis/how-to/how-to.cpp?name=vision_source)] > [!TIP] -> You can also analyze a local image by passing in the full-path image file name (see [VisionSource::FromFile](/cpp/cognitive-services/vision/input-visionsource#fromfile)), or by copying the image into the SDK's input buffer (see [VisionSource::FromImageSourceBuffer](/cpp/cognitive-services/vision/input-visionsource#fromimagesourcebuffer)). +> You can also analyze a local image by passing in the full-path image file name (see [VisionSource::FromFile](/cpp/cognitive-services/vision/input-visionsource#fromfile)), or by copying the image into the SDK's input buffer (see [VisionSource::FromImageSourceBuffer](/cpp/cognitive-services/vision/input-visionsource#fromimagesourcebuffer)). For more details, see [Call the Analyze API](./call-analyze-image-40.md?pivots=programming-language-cpp#select-the-image-to-analyze). #### [REST API](#tab/rest) To analyze a local image, you'd put the binary image data in the HTTP request bo ### [C#](#tab/csharp) -<!-- TODO: After C# ref-docs get published, add link to SegmentationMode (/dotnet/api/azure.ai.vision.imageanalysis.imageanalysisoptions.segmentationmode) & ImageSegmentationMode (/dotnet/api/azure.ai.vision.imageanalysis.imagesegmentationmode) --> - -Create a new [ImageAnalysisOptions](/dotnet/api/azure.ai.vision.imageanalysis.imageanalysisoptions) object and set the property `SegmentationMode`. This property must be set if you want to do segmentation. See `ImageSegmentationMode` for supported values. +Create a new [ImageAnalysisOptions](/dotnet/api/azure.ai.vision.imageanalysis.imageanalysisoptions) object and set the property [SegmentationMode](/dotnet/api/azure.ai.vision.imageanalysis.imageanalysisoptions.segmentationmode#azure-ai-vision-imageanalysis-imageanalysisoptions-segmentationmode). This property must be set if you want to do segmentation. See [ImageSegmentationMode](/dotnet/api/azure.ai.vision.imageanalysis.imagesegmentationmode) for supported values. [!code-csharp[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/csharp/image-analysis/segmentation/Program.cs?name=segmentation_mode)] ### [Python](#tab/python) -<!-- TODO: Where Python ref-docs get published, add link to SegmentationMode (/python/api/azure-ai-vision/azure.ai.vision.imageanalysisoptions#azure-ai-vision-imageanalysisoptions-segmentation-mode) & ImageSegmentationMode (/python/api/azure-ai-vision/azure.ai.vision.enums.imagesegmentationmode)> --> - -Create a new [ImageAnalysisOptions](/python/api/azure-ai-vision/azure.ai.vision.imageanalysisoptions) object and set the property `segmentation_mode`. This property must be set if you want to do segmentation. See `ImageSegmentationMode` for supported values. +Create a new [ImageAnalysisOptions](/python/api/azure-ai-vision/azure.ai.vision.imageanalysisoptions) object and set the property [segmentation_mode](/python/api/azure-ai-vision/azure.ai.vision.imageanalysisoptions#azure-ai-vision-imageanalysisoptions-segmentation-mode). This property must be set if you want to do segmentation. See [ImageSegmentationMode](/python/api/azure-ai-vision/azure.ai.vision.enums.imagesegmentationmode) for supported values. [!code-python[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/python/image-analysis/segmentation/main.py?name=segmentation_mode)] +### [Java](#tab/java) + +Create a new [ImageAnalysisOptions](/java/api/com.azure.ai.vision.imageanalysis.imageanalysisoptions) object and call the [setSegmentationMode](/java/api/com.azure.ai.vision.imageanalysis.imageanalysisoptions#com-azure-ai-vision-imageanalysis-imageanalysisoptions-setsegmentationmode()) method. You must call this method if you want to do segmentation. See [ImageSegmentationMode](/java/api/com.azure.ai.vision.imageanalysis.imagesegmentationmode) for supported values. + +[!code-java[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/java/image-analysis/segmentation/ImageAnalysis.java?name=segmentation_mode)] + ### [C++](#tab/cpp) Create a new [ImageAnalysisOptions](/cpp/cognitive-services/vision/imageanalysis-imageanalysisoptions) object and call the [SetSegmentationMode](/cpp/cognitive-services/vision/imageanalysis-imageanalysisoptions#setsegmentationmode) method. You must call this method if you want to do segmentation. See [ImageSegmentationMode](/cpp/cognitive-services/vision/azure-ai-vision-imageanalysis-namespace#enum-imagesegmentationmode) for supported values. This section shows you how to make the API call and parse the results. The following code calls the Image Analysis API and saves the resulting segmented image to a file named output.png. It also displays some metadata about the segmented image. -SegmentationResult implements IDisposable, therefore create the object with a using statement or explicitly call Dispose method after analysis completes. - [!code-csharp[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/csharp/image-analysis/segmentation/Program.cs?name=segment)] +SegmentationResult implements IDisposable, therefore create the object with a using statement or explicitly call Dispose method after analysis completes. + #### [Python](#tab/python) The following code calls the Image Analysis API and saves the resulting segmented image to a file named output.png. It also displays some metadata about the segmented image. [!code-python[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/python/image-analysis/segmentation/main.py?name=segment)] +#### [Java](#tab/java) + +The following code calls the Image Analysis API and saves the resulting segmented image to a file named output.png. It also displays some metadata about the segmented image. + +[!code-java[](~/azure-ai-vision-sdk/docs/learn.microsoft.com/java/image-analysis/segmentation/ImageAnalysis.java?name=segment)] + +SegmentationResult implements AutoCloseable, therefore create the object in a try-with-resources block, or explicitly call the close method on this object when you're done analyzing the image. + #### [C++](#tab/cpp) The following code calls the Image Analysis API and saves the resulting segmented image to a file named output.png. It also displays some metadata about the segmented image.
ai-services	Call Analyze Image 40	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-services/computer-vision/how-to/call-analyze-image-40.md	This article demonstrates how to call the Image Analysis 4.0 API to return infor ::: zone-end +++ ::: zone pivot="programming-language-rest-api" [!INCLUDE [REST API](../includes/how-to-guides/analyze-image-40-rest.md)]
ai-services	Image Analysis Client Library 40	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-services/computer-vision/quickstarts-sdk/image-analysis-client-library-40.md	Get started with the Image Analysis 4.0 REST API or client SDK to set up a basic ::: zone-end +++ ::: zone pivot="programming-language-rest-api" [!INCLUDE [REST API quickstart](../includes/image-analysis-curl-quickstart-40.md)]
ai-services	Install Sdk	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-services/computer-vision/sdk/install-sdk.md	Last updated 08/01/2023 -zone_pivot_groups: programming-languages-vision-40-sdk +zone_pivot_groups: programming-languages-vision-40-sdk # Install the Vision SDK zone_pivot_groups: programming-languages-vision-40-sdk [!INCLUDE [Python include](../includes/setup-sdk/python.md)] ::: zone-end + ## Next steps Follow the [Image Analysis quickstart](../quickstarts-sdk/image-analysis-client-library-40.md) to get started.
ai-services	Overview Sdk	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/ai-services/computer-vision/sdk/overview-sdk.md	The Vision SDK supports the following languages and platforms: \| C# <sup>1</sup> \| [quickstart](../quickstarts-sdk/image-analysis-client-library-40.md?pivots=programming-language-csharp) \| [reference](/dotnet/api/azure.ai.vision.imageanalysis) \| Windows, UWP, Linux \| \| C++ <sup>2</sup> \| [quickstart](../quickstarts-sdk/image-analysis-client-library-40.md?pivots=programming-language-cpp) \| [reference](/cpp/cognitive-services/vision) \| Windows, Linux \| \| Python \| [quickstart](../quickstarts-sdk/image-analysis-client-library-40.md?pivots=programming-language-python) \| [reference](/python/api/azure-ai-vision) \| Windows, Linux \| +\| Java \| [quickstart](../quickstarts-sdk/image-analysis-client-library-40.md?pivots=programming-language-java) \| [reference](/java/api/com.azure.ai.vision.imageanalysis) \| Windows, Linux \| + <sup>1 The Vision SDK for C# is based on .NET Standard 2.0. See [.NET Standard](/dotnet/standard/net-standard?tabs=net-standard-2-0#net-implementation-support) documentation.</sup>
aks	Azure Csi Files Storage Provision	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/azure-csi-files-storage-provision.md	description: Learn how to create a static or dynamic persistent volume with Azure Files for use with multiple concurrent pods in Azure Kubernetes Service (AKS) Previously updated : 08/16/2023 Last updated : 09/18/2023 # Create and use a volume with Azure Files in Azure Kubernetes Service (AKS) This section provides guidance for cluster administrators who want to provision \|Name \| Meaning \| Available Value \| Mandatory \| Default value \| \| \| \| \| -\|skuName \| Azure Files storage account type (alias: `storageAccountType`)\| `Standard_LRS`, `Standard_ZRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_RAGZRS`,`Premium_LRS`, `Premium_ZRS` \| No \| `StandardSSD_LRS`<br> Minimum file share size for Premium account type is 100 GB.<br> ZRS account type is supported in limited regions.<br> NFS file share only supports Premium account type.\| -\|protocol \| Specify file share protocol. \| `smb`, `nfs` \| No \| `smb` \| -\|location \| Specify the Azure region of the Azure storage account.\| For example, `eastus`. \| No \| If empty, driver uses the same location name as current AKS cluster.\| -\|resourceGroup \| Specify the resource group for the Azure Disks.\| Existing resource group name \| No \| If empty, driver uses the same resource group name as current AKS cluster.\| -\|shareName \| Specify Azure file share name. \| Existing or new Azure file share name. \| No \| If empty, driver generates an Azure file share name. \| -\|shareNamePrefix \| Specify Azure file share name prefix created by driver. \| Share name can only contain lowercase letters, numbers, hyphens, and length should be fewer than 21 characters. \| No \| -\|folderName \| Specify folder name in Azure file share. \| Existing folder name in Azure file share. \| No \| If folder name doesn't exist in file share, the mount fails. \| -\|shareAccessTier \| [Access tier for file share][storage-tiers] \| General purpose v2 account can choose between `TransactionOptimized` (default), `Hot`, and `Cool`. Premium storage account type for file shares only. \| No \| Empty. Use default setting for different storage account types.\| \|accountAccessTier \| [Access tier for storage account][access-tiers-overview] \| Standard account can choose `Hot` or `Cool`, and Premium account can only choose `Premium`. \| No \| Empty. Use default setting for different storage account types. \| -\|server \| Specify Azure storage account server address. \| Existing server address, for example `accountname.privatelink.file.core.windows.net`. \| No \| If empty, driver uses default `accountname.file.core.windows.net` or other sovereign cloud account address. \| -\|disableDeleteRetentionPolicy \| Specify whether disable DeleteRetentionPolicy for storage account created by driver. \| `true` or `false` \| No \| `false` \| +\|accountQuota \| Limits the quota for an account. You can specify a maximum quota in GB (102400GB by default). If the account exceeds the specified quota, the driver skips selecting the account. \|\|No \|`102400` \| \|allowBlobPublicAccess \| Allow or disallow public access to all blobs or containers for storage account created by driver. \| `true` or `false` \| No \| `false` \| +\|disableDeleteRetentionPolicy \| Specify whether disable DeleteRetentionPolicy for storage account created by driver. \| `true` or `false` \| No \| `false` \| +\|enableLargeFileShares \|Specify whether to use a storage account with large file shares enabled or not. If this flag is set to `true` and a storage account with large file shares enabled doesn't exist, a new storage account with large file shares enabled is created. This flag should be used with the Standard sku as the storage accounts created with Premium sku have `largeFileShares` option enabled by default. \|`true` or `false` \|No \|false \| +\|folderName \| Specify folder name in Azure file share. \| Existing folder name in Azure file share. \| No \| If folder name doesn't exist in file share, the mount fails. \| +\|getLatestAccount \|Determins whether to get the latest account key based on the creation time. This driver gets the first key by default. \|`true` or `false` \|No \|`false` \| +\|location \| Specify the Azure region of the Azure storage account.\| For example, `eastus`. \| No \| If empty, driver uses the same location name as current AKS cluster.\| +\|matchTags \| Match tags when driver tries to find a suitable storage account. \| `true` or `false` \| No \| `false` \| \|networkEndpointType \| Specify network endpoint type for the storage account created by driver. If `privateEndpoint` is specified, a private endpoint is created for the storage account. For other cases, a service endpoint is created by default. \| "",`privateEndpoint`\| No \| "" \| +\|protocol \| Specify file share protocol. \| `smb`, `nfs` \| No \| `smb` \| \|requireInfraEncryption \| Specify whether or not the service applies a secondary layer of encryption with platform managed keys for data at rest for storage account created by driver. \| `true` or `false` \| No \| `false` \| +\|resourceGroup \| Specify the resource group for the Azure Disks.\| Existing resource group name \| No \| If empty, driver uses the same resource group name as current AKS cluster.\| +\|selectRandomMatchingAccount \| Determines whether to randomly select a matching account. By default, the driver always selects the first matching account in alphabetical order (Note: This driver uses account search cache, which results in uneven distribution of file creation across multiple accounts). \| `true` or `false` \|No \| `false` \| +\|server \| Specify Azure storage account server address. \| Existing server address, for example `accountname.privatelink.file.core.windows.net`. \| No \| If empty, driver uses default `accountname.file.core.windows.net` or other sovereign cloud account address. \| +\|shareAccessTier \| [Access tier for file share][storage-tiers] \| General purpose v2 account can choose between `TransactionOptimized` (default), `Hot`, and `Cool`. Premium storage account type for file shares only. \| No \| Empty. Use default setting for different storage account types.\| +\|shareName \| Specify Azure file share name. \| Existing or new Azure file share name. \| No \| If empty, driver generates an Azure file share name. \| +\|shareNamePrefix \| Specify Azure file share name prefix created by driver. \| Share name can only contain lowercase letters, numbers, hyphens, and length should be fewer than 21 characters. \| No \| +\|skuName \| Azure Files storage account type (alias: `storageAccountType`)\| `Standard_LRS`, `Standard_ZRS`, `Standard_GRS`, `Standard_RAGRS`, `Standard_RAGZRS`,`Premium_LRS`, `Premium_ZRS` \| No \| `StandardSSD_LRS`<br> Minimum file share size for Premium account type is 100 GB.<br> ZRS account type is supported in limited regions.<br> NFS file share only supports Premium account type.\| \|storageEndpointSuffix \| Specify Azure storage endpoint suffix. \| `core.windows.net`, `core.chinacloudapi.cn`, etc. \| No \| If empty, driver uses default storage endpoint suffix according to cloud environment. For example, `core.windows.net`. \| \|tags \| [Tags][tag-resources] are created in new storage account. \| Tag format: 'foo=aaa,bar=bbb' \| No \| "" \| -\|matchTags \| Match tags when driver tries to find a suitable storage account. \| `true` or `false` \| No \| `false` \| \| \| Following parameters are only for SMB protocol \| \| \| \|subscriptionID \| Specify Azure subscription ID where Azure file share is created. \| Azure subscription ID \| No \| If not empty, `resourceGroup` must be provided. \| \|storeAccountKey \| Specify whether to store account key to Kubernetes secret. \| `true` or `false`<br>`false` means driver uses kubelet identity to get account key. \| No \| `true` \| This section provides guidance for cluster administrators who want to provision \|secretNamespace \| Specify the namespace of secret to store account key. <br><br> Note: <br> If `secretNamespace` isn't specified, the secret is created in the same namespace as the pod. \| `default`,`kube-system`, etc. \| No \| PVC namespace, for example `csi.storage.k8s.io/pvc/namespace` \| \|useDataPlaneAPI \| Specify whether to use [data plane API][data-plane-api] for file share create/delete/resize, which could solve the SRP API throttling issue because the data plane API has almost no limit, while it would fail when there's firewall or Vnet settings on storage account. \| `true` or `false` \| No \| `false` \| \| \| Following parameters are only for NFS protocol \| \| \| -\|rootSquashType \| Specify root squashing behavior on the share. The default is `NoRootSquash` \| `AllSquash`, `NoRootSquash`, `RootSquash` \| No \| \|mountPermissions \| Mounted folder permissions. The default is `0777`. If set to `0`, driver doesn't perform `chmod` after mount \| `0777` \| No \| +\|rootSquashType \| Specify root squashing behavior on the share. The default is `NoRootSquash` \| `AllSquash`, `NoRootSquash`, `RootSquash` \| No \| \| \| Following parameters are only for VNet setting. For example, NFS, private end point \| \| \| -\|vnetResourceGroup \| Specify VNet resource group where virtual network is defined. \| Existing resource group name. \| No \| If empty, driver uses the `vnetResourceGroup` value in Azure cloud config file. \| -\|vnetName \| Virtual network name \| Existing virtual network name. \| No \| If empty, driver uses the `vnetName` value in Azure cloud config file. \| -\|subnetName \| Subnet name \| Existing subnet name of the agent node. \| No \| If empty, driver uses the `subnetName` value in Azure cloud config file. \| \|fsGroupChangePolicy \| Indicates how the driver changes volume's ownership. Pod `securityContext.fsGroupChangePolicy` is ignored. \| `OnRootMismatch` (default), `Always`, `None` \| No \| `OnRootMismatch`\| +\|subnetName \| Subnet name \| Existing subnet name of the agent node. \| No \| If empty, driver uses the `subnetName` value in Azure cloud config file. \| +\|vnetName \| Virtual network name \| Existing virtual network name. \| No \| If empty, driver uses the `vnetName` value in Azure cloud config file. \| +\|vnetResourceGroup \| Specify VNet resource group where virtual network is defined. \| Existing resource group name. \| No \| If empty, driver uses the `vnetResourceGroup` value in Azure cloud config file. \| ### Create a storage class
aks	Cluster Autoscaler	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/cluster-autoscaler.md	To adjust to changing application demands, such as between workdays and evenings ![The cluster autoscaler and horizontal pod autoscaler often work together to support the required application demands](media/autoscaler/cluster-autoscaler.png) -Both the horizontal pod autoscaler and cluster autoscaler can decrease the number of pods and nodes as needed. The cluster autoscaler decreases the number of nodes when there has been unused capacity for a period of time. Any pods on a node to be removed by the cluster autoscaler are safely scheduled elsewhere in the cluster. +Both the horizontal pod autoscaler and cluster autoscaler can decrease the number of pods and nodes as needed. The cluster autoscaler decreases the number of nodes when there has been unused capacity after a period of time. Any pods on a node removed by the cluster autoscaler are safely scheduled elsewhere in the cluster. -If the current node pool size is lower than the specified minimum or greater than the specified maximum when you enable autoscaling, the autoscaler waits to take effect until a new node is needed in the node pool or until a node can be safely deleted from the node pool. For more information, see [How does scale-down work?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-scale-down-work) +With autoscaling enabled, when the node pool size is lower than the minimum or greater than the maximum it applies the scaling rules. Next, the autoscaler waits to take effect until a new node is needed in the node pool or until a node may be safely deleted from the current node pool. For more information, see [How does scale-down work?](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-scale-down-work) The cluster autoscaler may be unable to scale down if pods can't move, such as in the following situations: -* A pod is directly created and isn't backed by a controller object, such as a deployment or replica set. +* A directly created pod not backed by a controller object, such as a deployment or replica set. * A pod disruption budget (PDB) is too restrictive and doesn't allow the number of pods to fall below a certain threshold. * A pod uses node selectors or anti-affinity that can't be honored if scheduled on a different node. You can re-enable the cluster autoscaler on an existing cluster using the [`az a > [!IMPORTANT] > If you have multiple node pools in your AKS cluster, skip to the [autoscale with multiple agent pools section](#use-the-cluster-autoscaler-with-multiple-node-pools-enabled). Clusters with multiple agent pools require the `az aks nodepool` command instead of `az aks`. -In the previous step to create an AKS cluster or update an existing node pool, the cluster autoscaler minimum node count was set to one and the maximum node count was set to three. As your application demands change, you may need to adjust the cluster autoscaler node count. +In our example to enable cluster autoscaling, your cluster autoscaler's minimum node count was set to one and maximum node count was set to three. As your application demands change, you need to adjust the cluster autoscaler node count to scale efficiently. * Change the node count using the [`az aks update`][az-aks-update] command and update the cluster autoscaler using the `--update-cluster-autoscaler` parameter and specifying your updated node `--min-count` and `--max-count`. Monitor the performance of your applications and services, and adjust the cluste You can also configure more granular details of the cluster autoscaler by changing the default values in the cluster-wide autoscaler profile. For example, a scale down event happens after nodes are under-utilized after 10 minutes. If you have workloads that run every 15 minutes, you may want to change the autoscaler profile to scale down under-utilized nodes after 15 or 20 minutes. When you enable the cluster autoscaler, a default profile is used unless you specify different settings. The cluster autoscaler profile has the following settings you can update: +* Example profile update that scales after 15 minutes and changes after 10 minutes of idle use. + + ```azurecli-interactive + az aks update \ + -g learn-aks-cluster-scalability \ + -n learn-aks-cluster-scalability \ + --cluster-autoscaler-profile scan-interval=5s \ + scale-down-unready-time=10m \ + scale-down-delay-after-add=15m + ``` + \| Setting \| Description \| Default value \| \|-\|\|\| \| scan-interval \| How often cluster is reevaluated for scale up or down \| 10 seconds \| You can also configure more granular details of the cluster autoscaler by changi \| scale-down-delay-after-failure \| How long after scale down failure that scale down evaluation resumes \| 3 minutes \| \| scale-down-unneeded-time \| How long a node should be unneeded before it's eligible for scale down \| 10 minutes \| \| scale-down-unready-time \| How long an unready node should be unneeded before it's eligible for scale down \| 20 minutes \| -\| scale-down-utilization-threshold \| Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down \| 0.5 \| +\| scale-down-utilization-threshold \| Node utilization level, defined as sum of requested resources divided by capacity, in which a node can be considered for scale down \| 0.5 \| \| max-graceful-termination-sec \| Maximum number of seconds the cluster autoscaler waits for pod termination when trying to scale down a node \| 600 seconds \| \| balance-similar-node-groups \| Detects similar node pools and balances the number of nodes between them \| false \| \| expander \| Type of node pool [expander](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-expanders) to be used in scale up. Possible values: `most-pods`, `random`, `least-waste`, `priority` \| random \|
aks	Gpu Cluster	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/gpu-cluster.md	You can deploy a DaemonSet for the NVIDIA device plugin, which runs a pod on eac value: "gpu" effect: "NoSchedule" containers: - - image: mcr.microsoft.com/oss/nvidia/k8s-device-plugin:1.11 + - image: mcr.microsoft.com/oss/nvidia/k8s-device-plugin:v0.14.1 name: nvidia-device-plugin-ctr securityContext: allowPrivilegeEscalation: false
aks	Http Proxy	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/aks/http-proxy.md	Previously updated : 02/01/2023 Last updated : 09/18/2023 Some more complex solutions may require creating a chain of trust to establish s The following scenarios are not supported: - Different proxy configurations per node pool-- Updating HTTP/HTTPS proxy settings post cluster creation - User/Password authentication - Custom CAs for API server communication - Windows-based clusters In your template, provide values for httpProxy, httpsProxy, and noProxy. I ## Updating Proxy configurations -Values for httpProxy, and httpsProxy can't be changed after cluster creation. However, the values for trustedCa and NoProxy can be changed and applied to the cluster with the [az aks update][az-aks-update] command. An aks update for NoProxy will automatically inject new environment variables into pods with the new NoProxy values. Pods must be rotated for the apps to pick it up. For components under kubernetes, like containerd and the node itself, this won't take effect until a node image upgrade is performed. +> [!NOTE] +> If switching to a new proxy, the new proxy must already exist for the update to be successful. Then, after the upgrade is completed the old proxy can be deleted. + +Values for httpProxy, httpsProxy, trustedCa and NoProxy can be changed and applied to the cluster with the [az aks update][az-aks-update] command. An aks update for httpProxy, httpsProxy, and/or NoProxy will automatically inject new environment variables into pods with the new httpProxy, httpsProxy, or NoProxy values. Pods must be rotated for the apps to pick it up. For components under kubernetes, like containerd and the node itself, this won't take effect until a node image upgrade is performed. For example, assuming a new file has been created with the base64 encoded string of the new CA cert called aks-proxy-config-2.json, the following action updates the cluster. Or, you need to add new endpoint urls for your applications to No Proxy:
app-service	Configure Vnet Integration Enable	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/configure-vnet-integration-enable.md	If the virtual network is in a different subscription than the app, you must ens ## Configure in the Azure portal -1. Go to Networking in the App Service portal. Under Outbound Traffic, select VNet integration. +1. Go to Networking in the App Service portal. Under Outbound traffic configuration, select Virtual network integration. -1. Select Add VNet. +1. Select Add virtual network integration. - :::image type="content" source="./media/configure-vnet-integration-enable/vnetint-app.png" alt-text="Screenshot that shows selecting VNet integration."::: + :::image type="content" source="./media/configure-vnet-integration-enable/vnetint-app.png" alt-text="Screenshot that shows selecting Virtual network integration."::: 1. The dropdown list contains all the virtual networks in your subscription in the same region. Select an empty pre-existing subnet or create a new subnet.
app-service	Configure Vnet Integration Routing	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/configure-vnet-integration-routing.md	Last updated 10/20/2021 # Manage Azure App Service virtual network integration routing -Through application routing or configuration routing options, you can configure what traffic will be sent through the virtual network integration. See the [overview section](./overview-vnet-integration.md#routes) for more details. +Through application routing or configuration routing options, you can configure what traffic is sent through the virtual network integration. For more information, see the [overview section](./overview-vnet-integration.md#routes). ## Prerequisites Your app is already integrated using the regional virtual network integration fe ## Configure application routing -Application routing defines what traffic is routed from your app and into the virtual network. We recommend that you use the Route All site setting to enable routing of all traffic. Using the configuration setting allows you to audit the behavior with [a built-in policy](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F33228571-70a4-4fa1-8ca1-26d0aba8d6ef). The existing `WEBSITE_VNET_ROUTE_ALL` app setting can still be used, and you can enable all traffic routing with either setting. +Application routing defines what traffic is routed from your app and into the virtual network. We recommend that you use the `vnetRouteAllEnabled` site setting to enable routing of all traffic. Using the configuration setting allows you to audit the behavior with [a built-in policy](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F33228571-70a4-4fa1-8ca1-26d0aba8d6ef). The existing `WEBSITE_VNET_ROUTE_ALL` app setting can still be used, and you can enable all traffic routing with either setting. ### Configure in the Azure portal -Follow these steps to disable Route All in your app through the portal. +Follow these steps to disable outbound internet traffic routing in your app through the portal. -1. Go to Networking > VNet integration in your app portal. -1. Set Route All to Disabled. +1. Go to Networking > Virtual network integration in your app portal. +1. Uncheck the Outbound internet traffic setting. - :::image type="content" source="./media/configure-vnet-integration-routing/vnetint-route-all-disabling.png" alt-text="Screenshot that shows disabling Route All."::: + :::image type="content" source="./media/configure-vnet-integration-routing/vnetint-route-all-disabling.png" alt-text="Screenshot that shows disabling outbound internet traffic."::: -1. Select Yes to confirm. +1. Select Apply to confirm. ### Configure with the Azure CLI -You can also configure Route All by using the Azure CLI. +You can also configure Outbound internet traffic by using the Azure CLI. ```azurecli-interactive -az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetRouteAllEnabled [true\|false] +az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetRouteAllEnabled=[true\|false] ``` ## Configure configuration routing -When you're using virtual network integration, you can configure how parts of the configuration traffic are managed. By default, configuration traffic will go directly over the public route, but for the mentioned individual components, you can actively configure it to be routed through the virtual network integration. +When you're using virtual network integration, you can configure how parts of the configuration traffic are managed. By default, configuration traffic goes directly over the public route, but for the mentioned individual components, you can actively configure it to be routed through the virtual network integration. ### Container image pull Routing container image pull over virtual network integration can be configured using the Azure CLI. ```azurecli-interactive -az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetImagePullEnabled [true\|false] +az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetImagePullEnabled=[true\|false] ``` We recommend that you use the site property to enable routing image pull traffic through the virtual network integration. Using the configuration setting allows you to audit the behavior with Azure Policy. The existing `WEBSITE_PULL_IMAGE_OVER_VNET` app setting with the value `true` can still be used, and you can enable routing through the virtual network with either setting. We recommend that you use the site property to enable routing image pull traffic Routing content share over virtual network integration can be configured using the Azure CLI. In addition to enabling the feature, you must also ensure that any firewall or Network Security Group configured on traffic from the subnet allow traffic to port 443 and 445. ```azurecli-interactive -az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetContentShareEnabled [true\|false] +az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetContentShareEnabled=[true\|false] ``` We recommend that you use the site property to enable content share traffic through the virtual network integration. Using the configuration setting allows you to audit the behavior with Azure Policy. The existing `WEBSITE_CONTENTOVERVNET` app setting with the value `1` can still be used, and you can enable routing through the virtual network with either setting. +### Backup/restore + +Routing backup traffic over virtual network integration can be configured using the Azure CLI. Database backup isn't supported over the virtual network integration. + +```azurecli-interactive +az resource update --resource-group <group-name> --name <app-name> --resource-type "Microsoft.Web/sites" --set properties.vnetBackupRestoreEnabled=[true\|false] +``` + ## Next steps - [Enable virtual network integration](./configure-vnet-integration-enable.md)
app-service	Overview Vnet Integration	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/app-service/overview-vnet-integration.md	For Windows App Service plans, the virtual network integration feature supports Virtual network integration depends on a dedicated subnet. When you create a subnet, the Azure subnet consumes five IPs from the start. One address is used from the integration subnet for each App Service plan instance. If you scale your app to four instances, then four addresses are used. -When you scale up/down in size or in/out in number of instances, the required address space is doubled for a short period of time. This is because the scale operation adds the same number of new instances and then deletes the existing instances. The scale operation affects the real, available supported instances for a given subnet size. Platform upgrades need free IP addresses to ensure upgrades can happen without interruptions to outbound traffic. Finally, after scale up, down, or in operations complete, there might be a short period of time before IP addresses are released. +When you scale up/down in size or in/out in number of instances, the required address space is doubled for a short period of time. The scale operation adds the same number of new instances and then deletes the existing instances. The scale operation affects the real, available supported instances for a given subnet size. Platform upgrades need free IP addresses to ensure upgrades can happen without interruptions to outbound traffic. Finally, after scale up, down, or in operations complete, there might be a short period of time before IP addresses are released. Because subnet size can't be changed after assignment, use a subnet that's large enough to accommodate whatever scale your app might reach. You should also reserve IP addresses for platform upgrades. To avoid any issues with subnet capacity, use a `/26` with 64 addresses. When you're creating subnets in Azure portal as part of integrating with the virtual network, a minimum size of /27 is required. If the subnet already exists before integrating through the portal, you can use a /28 subnet. Through application routing or configuration routing options, you can configure ### Application routing -Application routing applies to traffic that is sent from your app after it has been started. See [configuration routing](#configuration-routing) for traffic during startup. When you configure application routing, you can either route all traffic or only private traffic (also known as [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918#section-3) traffic) into your virtual network. You configure this behavior through the Route All setting. If Route All is disabled, your app only routes private traffic into your virtual network. If you want to route all your outbound app traffic into your virtual network, make sure that Route All is enabled. +Application routing applies to traffic that is sent from your app after it has been started. See [configuration routing](#configuration-routing) for traffic during startup. When you configure application routing, you can either route all traffic or only private traffic (also known as [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918#section-3) traffic) into your virtual network. You configure this behavior through the outbound internet traffic setting. If outbound internet traffic routing is disabled, your app only routes private traffic into your virtual network. If you want to route all your outbound app traffic into your virtual network, make sure that outbound internet traffic is enabled. * Only traffic configured in application or configuration routing is subject to the NSGs and UDRs that are applied to your integration subnet. -* When Route All is enabled, the source address for your outbound public traffic from your app is still one of the IP addresses that are listed in your app properties. If you route your traffic through a firewall or a NAT gateway, the source IP address originates from this service. +* When outbound internet traffic routing is enabled, the source address for your outbound traffic from your app is still one of the IP addresses that are listed in your app properties. If you route your traffic through a firewall or a NAT gateway, the source IP address originates from this service. Learn [how to configure application routing](./configure-vnet-integration-routing.md#configure-application-routing). In addition to configuring the routing, you must also ensure that any firewall o #### Container image pull -When using custom containers, you can pull the container over the virtual network integration. To route the container pull traffic through the virtual network integration, you must ensure that the routing setting is configured. Learn [how to configure image pull routing](./configure-vnet-integration-routing.md#container-image-pull). +When using custom containers, you can pull the container over the virtual network integration. To route the container pull traffic through the virtual network integration, you must ensure that the routing setting is configured. Learn [how to configure image pull routing](./configure-vnet-integration-routing.md#container-image-pull). + +#### Backup/restore + +App Service has built-in backup/restore, but if you want to back up to your own storage account, you can use the custom backup/restore feature. If you want to route the traffic to the storage account through the virtual network integration, you must configure the route setting. Database backup isn't supported over the virtual network integration. #### App settings using Key Vault references App settings using Key Vault references attempt to get secrets over the public route. If the Key Vault is blocking public traffic and the app is using virtual network integration, an attempt is made to get the secrets through the virtual network integration. > [!NOTE] -> * Backup/restore to private storage accounts is currently not supported. > * Configure SSL/TLS certificates from private Key Vaults is currently not supported. > * App Service Logs to private storage accounts is currently not supported. We recommend using Diagnostics Logging and allowing Trusted Services for the storage account. You can use route tables to route outbound traffic from your app without restric Route tables and network security groups only apply to traffic routed through the virtual network integration. See [application routing](#application-routing) and [configuration routing](#configuration-routing) for details. Routes don't apply to replies from inbound app requests and inbound rules in an NSG don't apply to your app. Virtual network integration affects only outbound traffic from your app. To control inbound traffic to your app, use the [access restrictions](./overview-access-restrictions.md) feature or [private endpoints](./networking/private-endpoint.md). -When configuring network security groups or route tables that applies to outbound traffic, you must make sure you consider your application dependencies. Application dependencies include endpoints that your app needs during runtime. Besides APIs and services the app is calling, these endpoints could also be derived endpoints like certificate revocation list (CRL) check endpoints and identity/authentication endpoint, for example Azure Active Directory. If you're using [continuous deployment in App Service](./deploy-continuous-deployment.md), you might also need to allow endpoints depending on type and language. Specifically for [Linux continuous deployment](https://github.com/microsoft/Oryx/blob/main/doc/hosts/appservice.md#network-dependencies), you need to allow `oryx-cdn.microsoft.io:443`. For Python you additionally need to allow `files.pythonhosted.org`, `pypi.org`. +When configuring network security groups or route tables that applies to outbound traffic, you must make sure you consider your application dependencies. Application dependencies include endpoints that your app needs during runtime. Besides APIs and services the app is calling, these endpoints could also be derived endpoints like certificate revocation list (CRL) check endpoints and identity/authentication endpoint, for example Microsoft Entra ID. If you're using [continuous deployment in App Service](./deploy-continuous-deployment.md), you might also need to allow endpoints depending on type and language. Specifically for [Linux continuous deployment](https://github.com/microsoft/Oryx/blob/main/doc/hosts/appservice.md#network-dependencies), you need to allow `oryx-cdn.microsoft.io:443`. For Python you additionally need to allow `files.pythonhosted.org`, `pypi.org`. When you want to route outbound traffic on-premises, you can use a route table to send outbound traffic to your Azure ExpressRoute gateway. If you do route traffic to a gateway, set routes in the external network to send any replies back. Border Gateway Protocol (BGP) routes also affect your app traffic. If you have BGP routes from something like an ExpressRoute gateway, your app outbound traffic is affected. Similar to user-defined routes, BGP routes affect traffic according to your routing scope setting. After your app integrates with your virtual network, it uses the same DNS server There are some limitations with using virtual network integration: * The feature is available from all App Service deployments in Premium v2 and Premium v3. It's also available in Basic and Standard tier but only from newer App Service deployments. If you're on an older deployment, you can only use the feature from a Premium v2 App Service plan. If you want to make sure you can use the feature in a Basic or Standard App Service plan, create your app in a Premium v3 App Service plan. Those plans are only supported on our newest deployments. You can scale down if you want after the plan is created. -* The feature can't be used by Isolated plan apps that are in an App Service Environment. +* The feature isn't available for Isolated plan apps in an App Service Environment. * You can't reach resources across peering connections with classic virtual networks. * The feature requires an unused subnet that's an IPv4 `/28` block or larger in an Azure Resource Manager virtual network. * The app and the virtual network must be in the same region.
automation	Automation Hrw Run Runbooks	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-hrw-run-runbooks.md	Title: Run Azure Automation runbooks on a Hybrid Runbook Worker description: This article describes how to run runbooks on machines in your local datacenter or other cloud provider with the Hybrid Runbook Worker. Previously updated : 03/27/2023 Last updated : 09/17/2023 # Run Automation runbooks on a Hybrid Runbook Worker > [!IMPORTANT] -> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). > - Azure Automation Run As Account will retire on September 30, 2023 and will be replaced with Managed Identities. Before that date, you'll need to start migrating your runbooks to use [managed identities](automation-security-overview.md#managed-identities). For more information, see [migrating from an existing Run As accounts to managed identity](migrate-run-as-accounts-managed-identity.md#sample-scripts) to start migrating the runbooks from Run As account to managed identities before September 30, 2023.
automation	Automation Hybrid Runbook Worker	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-hybrid-runbook-worker.md	Title: Azure Automation Hybrid Runbook Worker overview description: Know about Hybrid Runbook Worker. How to install and run the runbooks on machines in your local datacenter or cloud provider. Previously updated : 04/20/2023 Last updated : 09/17/2023 # Automation Hybrid Runbook Worker overview > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). Runbooks in Azure Automation might not have access to resources in other clouds or in your on-premises environment because they run on the Azure cloud platform. You can use the Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on the machine hosting the role and against resources in the environment to manage those local resources. Runbooks are stored and managed in Azure Automation and then delivered to one or more assigned machines.
automation	Automation Linux Hrw Install	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-linux-hrw-install.md	description: This article tells how to install an agent-based Hybrid Runbook Wo Previously updated : 04/12/2023 Last updated : 09/17/2023 # Deploy an agent-based Linux Hybrid Runbook Worker in Automation > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). You can use the user Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on the Azure or non-Azure machine, including servers registered with [Azure Arc-enabled servers](../azure-arc/servers/overview.md). From the machine or server that's hosting the role, you can run runbooks directly it and against resources in the environment to manage those local resources.
automation	Automation Windows Hrw Install	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/automation-windows-hrw-install.md	Title: Deploy an agent-based Windows Hybrid Runbook Worker in Automation description: This article tells how to deploy an agent-based Hybrid Runbook Worker that you can use to run runbooks on Windows-based machines in your local datacenter or cloud environment. Previously updated : 04/01/2023 Last updated : 09/17/2023 # Deploy an agent-based Windows Hybrid Runbook Worker in Automation > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). You can use the user Hybrid Runbook Worker feature of Azure Automation to run runbooks directly on an Azure or non-Azure machine, including servers registered with [Azure Arc-enabled servers](../azure-arc/servers/overview.md). From the machine or server that's hosting the role, you can run runbooks directly against it and against resources in the environment to manage those local resources.
automation	Enforce Job Execution Hybrid Worker	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/enforce-job-execution-hybrid-worker.md	Title: Enforce job execution on Azure Automation Hybrid Runbook Worker description: This article tells how to use a custom Azure Policy definition to enforce job execution on an Azure Automation Hybrid Runbook Worker. Previously updated : 03/15/2023 Last updated : 09/17/2023 # Use Azure Policy to enforce job execution on Hybrid Runbook Worker > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). Starting a runbook on a Hybrid Runbook Worker uses a Run on option that allows you to specify the name of a Hybrid Runbook Worker group when initiating from the Azure portal, with the Azure PowerShell, or REST API. When a group is specified, one of the workers in that group retrieves and runs the runbook. If your runbook does not specify this option, Azure Automation runs the runbook in the Azure sandbox.
automation	Migrate Existing Agent Based Hybrid Worker To Extension Based Workers	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md	Title: Migrate an existing agent-based hybrid workers to extension-based-workers description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers. Previously updated : 04/11/2023 Last updated : 09/17/2023 #Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers. # Migrate the existing agent-based hybrid workers to extension-based hybrid workers > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). This article describes the benefits of Extension-based User Hybrid Runbook Worker and how to migrate existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers.
automation	Hybrid Runbook Worker	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/troubleshoot/hybrid-runbook-worker.md	Title: Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation description: This article tells how to troubleshoot and resolve issues that arise with Azure Automation agent-based Hybrid Runbook Workers. Previously updated : 04/26/2023 Last updated : 09/17/2023 # Troubleshoot agent-based Hybrid Runbook Worker issues in Automation > [!IMPORTANT] -> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 October 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](../migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md) +> Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) will retire on 31 August 2024 and wouldn't be supported after that date. You must complete migrating existing Agent-based User Hybrid Runbook Workers to Extension-based Workers before 31 August 2024. Moreover, starting 1 November 2023, creating new Agent-based Hybrid Workers wouldn't be possible. [Learn more](../migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md) This article provides information on troubleshooting and resolving issues with Azure Automation agent-based Hybrid Runbook Workers. For troubleshooting extension-based workers, see [Troubleshoot extension-based Hybrid Runbook Worker issues in Automation](./extension-based-hybrid-runbook-worker.md). For general information, see [Hybrid Runbook Worker overview](../automation-hybrid-runbook-worker.md).
automation	Whats New	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/automation/whats-new.md	description: Significant updates to Azure Automation updated each month. Previously updated : 05/10/2023 Last updated : 09/17/2023 Azure Automation has expanded Public preview support for PowerShell 7.2 and Pyth Type: Plan for change -On 31 August 2024, Azure Automation will [retire](https://azure.microsoft.com/updates/retirement-azure-automation-agent-user-hybrid-worker/) Agent-based User Hybrid Runbook Worker ([Windows](automation-windows-hrw-install.md) and [Linux](automation-linux-hrw-install.md)). You must migrate all Agent-based User Hybrid Workers to [Extension-based User Hybrid Runbook Worker](extension-based-hybrid-runbook-worker-install.md) (Windows and Linux) before the deprecation date. Moreover, starting 1 October 2023, creating new Agent-based User Hybrid Runbook Worker will not be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). +On 31 August 2024, Azure Automation will [retire](https://azure.microsoft.com/updates/retirement-azure-automation-agent-user-hybrid-worker/) Agent-based User Hybrid Runbook Worker ([Windows](automation-windows-hrw-install.md) and [Linux](automation-linux-hrw-install.md)). You must migrate all Agent-based User Hybrid Workers to [Extension-based User Hybrid Runbook Worker](extension-based-hybrid-runbook-worker-install.md) (Windows and Linux) before the deprecation date. Moreover, starting 1 November 2023, creating new Agent-based User Hybrid Runbook Worker will not be possible. [Learn more](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md). ## January 2023
azure-app-configuration	Cli Samples	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/cli-samples.md	Title: Azure CLI samples - Azure App Configuration description: Information about sample scripts provided for Azure App Configuration--++ Last updated 08/09/2022
azure-app-configuration	Concept Customer Managed Keys	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-customer-managed-keys.md	Title: Use customer-managed keys to encrypt your configuration data description: Encrypt your configuration data using customer-managed keys--++ Last updated 08/30/2022
azure-app-configuration	Concept Enable Rbac	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-enable-rbac.md	Title: Authorize access to Azure App Configuration using Azure Active Directory description: Enable Azure RBAC to authorize access to your Azure App Configuration instance--++ Last updated 05/26/2020
azure-app-configuration	Concept Feature Management	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-feature-management.md	Title: Understand feature management using Azure App Configuration description: Turn features on and off using Azure App Configuration --++
azure-app-configuration	Concept Geo Replication	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-geo-replication.md	Title: Geo-replication in Azure App Configuration description: Details of the geo-replication feature in Azure App Configuration. --++
azure-app-configuration	Concept Github Action	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-github-action.md	Title: Sync your GitHub repository to App Configuration description: Use GitHub Actions to automatically update your App Configuration instance when you update your GitHub repository.--++ Last updated 05/28/2020
azure-app-configuration	Concept Key Value	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-key-value.md	Title: Understand Azure App Configuration key-value store description: Understand key-value storage in Azure App Configuration, which stores configuration data as key-values. Key-values are a representation of application settings.--++ Last updated 09/14/2022
azure-app-configuration	Concept Point Time Snapshot	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-point-time-snapshot.md	Title: Retrieve key-values from a point-in-time description: Retrieve old key-values using point-in-time revisions in Azure App Configuration, which maintains a record of changes to key-values. --++ Last updated 05/24/2023
azure-app-configuration	Concept Private Endpoint	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/concept-private-endpoint.md	Title: Using private endpoints for Azure App Configuration description: Secure your App Configuration store using private endpoints --++ Last updated 07/15/2020
azure-app-configuration	Enable Dynamic Configuration Dotnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet-core.md	description: In this tutorial, you learn how to dynamically update the configuration data for .NET apps documentationcenter: ''-+ editor: '' ms.devlang: csharp Last updated 07/11/2023-+ #Customer intent: I want to dynamically update my app to use the latest configuration data in App Configuration. # Tutorial: Use dynamic configuration in a .NET app
azure-app-configuration	Enable Dynamic Configuration Dotnet	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/enable-dynamic-configuration-dotnet.md	Title: '.NET Framework Tutorial: dynamic configuration in Azure App Configuration' description: In this tutorial, you learn how to dynamically update the configuration data for .NET Framework apps using Azure App Configuration. -+ ms.devlang: csharp Last updated 03/20/2023-+ #Customer intent: I want to dynamically update my .NET Framework app to use the latest configuration data in App Configuration. # Tutorial: Use dynamic configuration in a .NET Framework app
azure-app-configuration	Howto App Configuration Event	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-app-configuration-event.md	Title: Use Event Grid for App Configuration data change notifications description: Learn how to use Azure App Configuration event subscriptions to send key-value modification events to a web endpoint -+ ms.assetid: ms.devlang: csharp Last updated 03/04/2020-+
azure-app-configuration	Howto Disable Public Access	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-disable-public-access.md	Title: How to disable public access in Azure App Configuration description: How to disable public access to your Azure App Configuration store.--++ Last updated 07/12/2022
azure-app-configuration	Howto Feature Filters Aspnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-feature-filters-aspnet-core.md	description: Learn how to use feature filters to enable conditional feature flag ms.devlang: csharp --++ Last updated 3/9/2020
azure-app-configuration	Howto Import Export Data	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-import-export-data.md	Title: Import or export data with Azure App Configuration description: Learn how to import or export configuration data to or from Azure App Configuration. Exchange data between your App Configuration store and code project. -+ Last updated 08/24/2022-+ # Import or export configuration data
azure-app-configuration	Howto Integrate Azure Managed Service Identity	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-integrate-azure-managed-service-identity.md	Title: Use managed identities to access App Configuration description: Authenticate to Azure App Configuration using managed identities--++
azure-app-configuration	Howto Labels Aspnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-labels-aspnet-core.md	description: This article describes how to use labels to retrieve app configuration values for the environment in which the app is currently running. ms.devlang: csharp-+ Last updated 07/11/2023-+ # Use labels to provide per-environment configuration values.
azure-app-configuration	Howto Move Resource Between Regions	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-move-resource-between-regions.md	Title: Move an App Configuration store to another region description: Learn how to move an App Configuration store to a different region. --++ Last updated 03/27/2023
azure-app-configuration	Howto Set Up Private Access	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-set-up-private-access.md	Title: How to set up private access to an Azure App Configuration store description: How to set up private access to an Azure App Configuration store in the Azure portal and in the CLI.--++ Last updated 07/12/2022
azure-app-configuration	Howto Targetingfilter Aspnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/howto-targetingfilter-aspnet-core.md	description: Learn how to enable staged rollout of features for targeted audiences ms.devlang: csharp--++ Last updated 11/20/2020
azure-app-configuration	Integrate Ci Cd Pipeline	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/integrate-ci-cd-pipeline.md	Title: Integrate Azure App Configuration using a continuous integration and delivery pipeline description: Learn to implement continuous integration and delivery using Azure App Configuration -+ Last updated 08/30/2022-+ # Customer intent: I want to use Azure App Configuration data in my CI/CD pipeline.
azure-app-configuration	Integrate Kubernetes Deployment Helm	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md	Title: Integrate Azure App Configuration with Kubernetes Deployment using Helm description: Learn how to use dynamic configurations in Kubernetes deployment with Helm. -+ Last updated 03/27/2023-+ #Customer intent: I want to use Azure App Configuration data in Kubernetes deployment with Helm.
azure-app-configuration	Manage Feature Flags	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/manage-feature-flags.md	description: In this tutorial, you learn how to manage feature flags separately from your application by using Azure App Configuration. documentationcenter: ''-+ editor: '' ms.assetid: ms.devlang: csharp Last updated 04/05/2022-+ #Customer intent: I want to control feature availability in my app by using App Configuration.
azure-app-configuration	Monitor App Configuration Reference	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/monitor-app-configuration-reference.md	Title: Monitoring Azure App Configuration data reference description: Important Reference material needed when you monitor App Configuration --++ Last updated 05/05/2021
azure-app-configuration	Monitor App Configuration	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/monitor-app-configuration.md	Title: Monitor Azure App Configuration description: Start here to learn how to monitor App Configuration --++
azure-app-configuration	Overview Managed Identity	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/overview-managed-identity.md	Title: Configure managed identities with Azure App Configuration description: Learn how managed identities work in Azure App Configuration and how to configure a managed identity-+ Last updated 02/25/2020-+
azure-app-configuration	Overview	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/overview.md	Title: What is Azure App Configuration? description: Read an overview of the Azure App Configuration service. Understand why you would want to use App Configuration, and learn how you can use it.--++ Last updated 03/20/2023
azure-app-configuration	Policy Reference	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/policy-reference.md	Title: Built-in policy definitions for Azure App Configuration description: Lists Azure Policy built-in policy definitions for Azure App Configuration. These built-in policy definitions provide common approaches to managing your Azure resources. Last updated 09/13/2023 --++
azure-app-configuration	Powershell Samples	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/powershell-samples.md	Last updated 01/19/2023--++ # PowerShell samples for Azure App Configuration
azure-app-configuration	Pull Key Value Devops Pipeline	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/pull-key-value-devops-pipeline.md	Title: Pull settings from App Configuration with Azure Pipelines description: Learn how to use Azure Pipelines to pull key-values from an App Configuration Store -+ Last updated 11/17/2020-+ # Pull settings from App Configuration with Azure Pipelines
azure-app-configuration	Push Kv Devops Pipeline	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/push-kv-devops-pipeline.md	Title: Push settings to App Configuration with Azure Pipelines description: Learn to use Azure Pipelines to push key-values to an App Configuration Store -+ Last updated 02/23/2021-+ # Push settings to App Configuration with Azure Pipelines
azure-app-configuration	Quickstart Azure App Configuration Create	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-azure-app-configuration-create.md	Title: "Quickstart: Create an Azure App Configuration store"--++ description: "In this quickstart, learn how to create an App Configuration store." ms.devlang: csharp
azure-app-configuration	Quickstart Bicep	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-bicep.md	Title: Create an Azure App Configuration store using Bicep description: Learn how to create an Azure App Configuration store using Bicep.--++ Last updated 05/06/2022
azure-app-configuration	Quickstart Container Apps	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-container-apps.md	Title: "Quickstart: Use Azure App Configuration in Azure Container Apps" description: Learn how to connect a containerized application to Azure App Configuration, using Service Connector. -+ Last updated 03/02/2023-+
azure-app-configuration	Quickstart Dotnet App	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-dotnet-app.md	Title: Quickstart for Azure App Configuration with .NET Framework \| Microsoft Do description: In this article, create a .NET Framework app with Azure App Configuration to centralize storage and management of application settings separate from your code. documentationcenter: ''-+ ms.devlang: csharp Last updated 02/28/2023-+ #Customer intent: As a .NET Framework developer, I want to manage all my app settings in one place. # Quickstart: Create a .NET Framework app with Azure App Configuration
azure-app-configuration	Quickstart Dotnet Core App	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-dotnet-core-app.md	Title: Quickstart for Azure App Configuration with .NET \| Microsoft Docs description: In this quickstart, create a .NET app with Azure App Configuration to centralize storage and management of application settings separate from your code. -+ ms.devlang: csharp Last updated 07/11/2023-+ #Customer intent: As a .NET developer, I want to manage all my app settings in one place. # Quickstart: Create a .NET app with App Configuration
azure-app-configuration	Quickstart Feature Flag Azure Functions Csharp	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-feature-flag-azure-functions-csharp.md	Title: Quickstart for adding feature flags to Azure Functions \| Microsoft Docs description: In this quickstart, use Azure Functions with feature flags from Azure App Configuration and test the function locally. -+ ms.devlang: csharp Last updated 3/20/2023-+ # Quickstart: Add feature flags to an Azure Functions app
azure-app-configuration	Quickstart Feature Flag Dotnet	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-feature-flag-dotnet.md	Title: Quickstart for adding feature flags to .NET Framework apps \| Microsoft Do description: A quickstart for adding feature flags to .NET Framework apps and managing them in Azure App Configuration documentationcenter: ''-+ editor: '' ms.assetid: .NET Last updated 3/20/2023-+ #Customer intent: As a .NET Framework developer, I want to use feature flags to control feature availability quickly and confidently. # Quickstart: Add feature flags to a .NET Framework app
azure-app-configuration	Quickstart Javascript	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-javascript.md	Title: Quickstart for using Azure App Configuration with JavaScript apps \| Microsoft Docs description: In this quickstart, create a Node.js app with Azure App Configuration to centralize storage and management of application settings separate from your code. -+ ms.devlang: javascript Last updated 03/20/2023-+ #Customer intent: As a JavaScript developer, I want to manage all my app settings in one place. # Quickstart: Create a JavaScript app with Azure App Configuration
azure-app-configuration	Quickstart Python Provider	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-python-provider.md	Title: Quickstart for using Azure App Configuration with Python apps \| Microsoft Learn description: In this quickstart, create a Python app with the Azure App Configuration to centralize storage and management of application settings separate from your code. -+ ms.devlang: python Last updated 03/20/2023-+ #Customer intent: As a Python developer, I want to manage all my app settings in one place. # Quickstart: Create a Python app with Azure App Configuration
azure-app-configuration	Quickstart Python	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-python.md	Title: Using Azure App Configuration in Python apps with the Azure SDK for Python \| Microsoft Learn description: This document shows examples of how to use the Azure SDK for Python to access your data in Azure App Configuration. -+ ms.devlang: python Last updated 11/17/2022-+ #Customer intent: As a Python developer, I want to use the Azure SDK for Python to access my data in Azure App Configuration. # Create a Python app with the Azure SDK for Python
azure-app-configuration	Quickstart Resource Manager	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/quickstart-resource-manager.md	Title: Create an Azure App Configuration store by using Azure Resource Manager template (ARM template) description: Learn how to create an Azure App Configuration store by using Azure Resource Manager template (ARM template).--++ Last updated 06/09/2021
azure-app-configuration	Rest Api Authentication Azure Ad	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authentication-azure-ad.md	Title: Azure Active Directory REST API - authentication description: Use Azure Active Directory to authenticate to Azure App Configuration by using the REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Authentication Hmac	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authentication-hmac.md	Title: Azure App Configuration REST API - HMAC authentication description: Use HMAC to authenticate to Azure App Configuration by using the REST API--++ ms.devlang: csharp, golang, java, javascript, powershell, python
azure-app-configuration	Rest Api Authentication Index	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authentication-index.md	∩╗┐ Title: Azure App Configuration REST API - Authentication description: Reference pages for authentication using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Authorization Azure Ad	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authorization-azure-ad.md	Title: Azure App Configuration REST API - Azure Active Directory authorization description: Use Azure Active Directory for authorization against Azure App Configuration by using the REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Authorization Hmac	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authorization-hmac.md	Title: Azure App Configuration REST API - HMAC authorization description: Use HMAC for authorization against Azure App Configuration using the REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Authorization Index	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-authorization-index.md	∩╗┐ Title: Azure App Configuration REST API - Authorization description: Reference pages for authorization using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Consistency	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-consistency.md	∩╗┐ Title: Azure App Configuration REST API - consistency description: Reference pages for ensuring real-time consistency by using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Fiddler	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-fiddler.md	∩╗┐ Title: Azure Active Directory REST API - Test Using Fiddler description: Use Fiddler to test the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Headers	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-headers.md	Title: Azure App Configuration REST API - Headers description: Reference pages for headers used with the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Key Value	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-key-value.md	∩╗┐ Title: Azure App Configuration REST API - key-value description: Reference pages for working with key-values by using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Keys	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-keys.md	Title: Azure App Configuration REST API - Keys description: Reference pages for working with keys using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Labels	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-labels.md	Title: Azure App Configuration REST API - Labels description: Reference pages for working with labels using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Locks	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-locks.md	Title: Azure App Configuration REST API - locks description: Reference pages for working with key-value locks by using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Postman	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-postman.md	∩╗┐ Title: Azure Active Directory REST API - Test by using Postman description: Use Postman to test the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Revisions	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-revisions.md	Title: Azure App Configuration REST API - key-value revisions description: Reference pages for working with key-value revisions by using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Throttling	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-throttling.md	Title: Azure App Configuration REST API - Throttling description: Reference pages for understanding throttling when using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api Versioning	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api-versioning.md	Title: Azure App Configuration REST API - versioning description: Reference pages for versioning by using the Azure App Configuration REST API--++ Last updated 08/17/2020
azure-app-configuration	Rest Api	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/rest-api.md	Title: Azure App Configuration REST API description: Reference pages for the Azure App Configuration REST API--++ Last updated 11/28/2022
azure-app-configuration	Cli Create Service	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/cli-create-service.md	Title: Azure CLI Script Sample - Create an Azure App Configuration Store description: Create an Azure App Configuration store using a sample Azure CLI script. See reference article links to commands used in the script. -+ Last updated 01/18/2023-+
azure-app-configuration	Cli Delete Service	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/cli-delete-service.md	Title: Azure CLI Script Sample - Delete an Azure App Configuration Store description: Delete an Azure App Configuration store using a sample Azure CLI script. See reference article links to commands used in the script. -+ ms.devlang: azurecli Last updated 02/19/2020-+
azure-app-configuration	Cli Export	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/cli-export.md	Title: Azure CLI Script Sample - Export from an Azure App Configuration Store description: Use Azure CLI script to export configuration from Azure App Configuration -+ ms.devlang: azurecli Last updated 02/19/2020-+
azure-app-configuration	Cli Import	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/cli-import.md	Title: Azure CLI script sample - Import to an App Configuration store description: Use Azure CLI script - Importing configuration to Azure App Configuration -+ ms.devlang: azurecli Last updated 02/19/2020-+
azure-app-configuration	Cli Work With Keys	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/cli-work-with-keys.md	Title: Azure CLI Script Sample - Work with key-values in App Configuration Store description: Use Azure CLI script to create, view, update and delete key values from App Configuration store -+ ms.devlang: azurecli Last updated 02/19/2020-+
azure-app-configuration	Powershell Create Service	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/powershell-create-service.md	Title: PowerShell script sample - Create an Azure App Configuration store description: Create an Azure App Configuration store using a sample PowerShell script. See reference article links to commands used in the script. -+ Last updated 02/12/2023-+
azure-app-configuration	Powershell Delete Service	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/scripts/powershell-delete-service.md	Title: PowerShell script sample - Delete an Azure App Configuration store description: Delete an Azure App Configuration store using a sample PowerShell script. See reference article links to commands used in the script. -+ Last updated 02/02/2023-+
azure-app-configuration	Security Controls Policy	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/security-controls-policy.md	Title: Azure Policy Regulatory Compliance controls for Azure App Configuration description: Lists Azure Policy Regulatory Compliance controls available for Azure App Configuration. These built-in policy definitions provide common approaches to managing the compliance of your Azure resources. Last updated 09/14/2023 --++
azure-app-configuration	Use Feature Flags Dotnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/use-feature-flags-dotnet-core.md	Title: Tutorial for using feature flags in a .NET app \| Microsoft Docs description: In this tutorial, you learn how to implement feature flags in .NET Core apps. documentationcenter: ''-+ editor: '' ms.assetid: ms.devlang: csharp Last updated 07/11/2023-+ #Customer intent: I want to control feature availability in my app by using the .NET Core Feature Manager library.
azure-app-configuration	Use Key Vault References Dotnet Core	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-app-configuration/use-key-vault-references-dotnet-core.md	Title: Tutorial for using Azure App Configuration Key Vault references in an ASP description: In this tutorial, you learn how to use Azure App Configuration's Key Vault references from an ASP.NET Core app documentationcenter: ''-+ editor: '' ms.assetid: ms.devlang: csharp Last updated 07/11/2023-+ #Customer intent: I want to update my ASP.NET Core application to reference values stored in Key Vault through App Configuration.
azure-functions	Functions Bindings Event Grid Output	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-functions/functions-bindings-event-grid-output.md	def main(eventGridEvent: func.EventGridEvent, event_time=datetime.datetime.utcnow(), data_version="1.0")) ```-+ ::: zone-end ::: zone pivot="programming-language-csharp" ## Attributes
azure-linux	Intro Azure Linux	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-linux/intro-azure-linux.md	Previously updated : 06/01/2023 Last updated : 09/05/2023 # What is the Azure Linux Container Host for AKS? -The Azure Linux Container Host is an operating system image that's optimized for running container workloads on [Azure Kubernetes Service (AKS)](../../articles/aks/intro-kubernetes.md). It's maintained by Microsoft and based on Microsoft Azure Linux, an open-source Linux distribution created by Microsoft. +The Azure Linux Container Host is an operating system image that's optimized for running container workloads on [Azure Kubernetes Service (AKS)](../../articles/aks/intro-kubernetes.md). Microsoft maintains the Azure Linux Container Host and based it on [CBL-Mariner][cbl-mariner], an open-source Linux distribution created by Microsoft. The Azure Linux Container Host is lightweight, containing only the packages needed to run container workloads. It's hardened based on significant validation tests and internal usage and is compatible with Azure agents. It provides reliability and consistency from cloud to edge across AKS, AKS for Azure Stack HCI, and Azure Arc. You can deploy Azure Linux node pools in a new cluster, add Azure Linux node pools to your existing clusters, or migrate your existing nodes to Azure Linux nodes. To learn more about Azure Linux, see the [Azure Linux GitHub repository](https:/ The Azure Linux Container Host offers the following key benefits: -- Secure supply chain: Microsoft builds, signs, and validates the Azure Linux Container Host packages from source, and hosts its packages and sources in Microsoft-owned and secured platforms.-- Small and lightweight: The Azure Linux Container Host only includes the necessary set of packages needed to run container workloads. As a result, it consumes limited disk and memory resources.-- Secure by default: The Azure Linux Container Host has an emphasis on security and follows the secure-by-default principles, including using a hardened Linux kernel with Azure cloud optimizations and flags tuned for Azure. It also provides a reduced attack surface and eliminates patching and maintenance of unnecessary packages. For more information on Azure Linux Container Host security principles, see the [AKS security concepts](../../articles/aks/concepts-security.md).-- Extensively validated: The AKS and Azure Linux teams run a suite of functional and performance regression tests with the Azure Linux Container Host before releasing to customers, which enables earlier issue detection and mitigation.ΓÇï +- Small and lightweight + - The Azure Linux Container Host only includes the necessary set of packages needed to run container workloads. As a result, it consumes limited disk and memory resources. + - Azure Linux has only 500 packages, and as a result takes up the least disk space by up to 5 GB on AKS. +- Secure supply chain + - The Linux and AKS teams at Microsoft build, sign, and validate the [Azure Linux Container Host packages][azure-linux-packages] from source, and host packages and sources in Microsoft-owned and secured platforms. + - Each package update runs through a full set of unit tests and end-to-end testing on the existing image to prevent regressions. The extensive testing, in combination with the smaller package count, reduces the chances of disruptive updates to applications. +- Secure by default + - The Azure Linux Container Host has an emphasis on security. It follows the secure-by-default principles, including using a hardened Linux kernel with Azure cloud optimizations and flags tuned for Azure. It also provides a reduced attack surface and eliminates patching and maintenance of unnecessary packages. + - Microsoft monitors the CVE database and releases security patches monthly and critical updates within days if necessary. + - Azure Linux passes all the [CIS Level 1 benchmarks][cis-benchmarks], making it the only Linux distribution on AKS that does so. + - For more information on Azure Linux Container Host security principles, see the [AKS security concepts](../../articles/aks/concepts-security.md). +- Maintains compatibility with existing workloads + - All existing and future AKS extensions, add-ons, and open-source projects on AKS support both Ubuntu and Azure Linux. This includes support for runtime components like Dapr, IaC tools like Terraform, and monitoring solutions like Dynatrace. + - Azure Linux ships with containerd as its container runtime and the upstream Linux kernel, which enables existing containers based on Linux images (like Alpine) to work seamlessly on Azure Linux. > [!NOTE] > The Azure Linux Container Host offers the following key benefits: - Learn more about [Azure Linux Container Host core concepts](./concepts-core.md). - Follow our tutorial to [Deploy, manage, and update applications](./tutorial-azure-linux-create-cluster.md). - Get started by [Creating an Azure Linux Container Host for AKS cluster using Azure CLI](./quickstart-azure-cli.md).+ +<!-- LINKS - external --> +[cbl-mariner]: https://github.com/microsoft/CBL-Mariner +[azure-linux-packages]: https://packages.microsoft.com/cbl-mariner/2.0/prod/ + +<!-- LINKS - internal --> +[cis-benchmarks]: ../aks/cis-azure-linux.md
azure-monitor	Agents Overview	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/agents/agents-overview.md	The tables below provide a comparison of Azure Monitor Agent with the legacy the \| \| Event Hub \| \| \| X \| \| Services and features supported \| \| \| \| \| \| \| Microsoft Sentinel \| X ([View scope](./azure-monitor-agent-migration.md#migrate-additional-services-and-features)) \| X \| \| -\| \| VM Insights \| X (Public preview) \| X \| \| +\| \| VM Insights \| X \| X \| \| \| \| Microsoft Defender for Cloud \| X (Public preview) \| X \| \| \| \| Automation Update Management \| \| X \| \| \| \| Azure Stack HCI \| X \| \| \| The tables below provide a comparison of Azure Monitor Agent with the legacy the \| \| Event Hub \| \| \| X \| \| \| Services and features supported \| \| \| \| \| \| \| \| Microsoft Sentinel \| X ([View scope](./azure-monitor-agent-migration.md#migrate-additional-services-and-features)) \| X \| \| -\| \| VM Insights \| X (Public preview) \| X \| \| +\| \| VM Insights \| X \| X \| \| \| \| Microsoft Defender for Cloud \| X (Public preview) \| X \| \| \| \| Automation Update Management \| \| X \| \| \| \| Update Manager \| N/A (Public preview, independent of monitoring agents) \| \| \|
azure-monitor	Alerts Troubleshoot Log	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/alerts/alerts-troubleshoot-log.md	The alert time range is limited to a maximum of two days. Even if the query cont If the query requires more data than the alert evaluation, you can change the time range manually. If there's ago command in the query, it will be changed automatically to be 2 days (48 hours). + ## Log alert fired unnecessarily A configured [log alert rule in Azure Monitor](./alerts-log.md) might be triggered unexpectedly. The following sections describe some common reasons.
azure-monitor	Custom Operations Tracking	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/custom-operations-tracking.md	public class ApplicationInsightsMiddleware : OwinMiddleware catch (Exception e) { requestTelemetry.Success = false; + requestTelemetry.ResponseCode; telemetryClient.TrackException(e); throw; }
azure-monitor	Opentelemetry Enable	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/app/opentelemetry-enable.md	Follow the steps in this section to instrument your application with OpenTelemet - Python Application using Python 3.7+ -> [!CAUTION] -> We have not tested the Azure Monitor OpenTelemetry Distro running side-by-side with the OpenTelemetry Community Package. We recommend you uninstall any OpenTelemetry-related packages before installing the Distro. + +[!TIP] We don't recommend using the OTel Community SDK/API with the Azure Monitor OTel Distro since it automatically loads them as dependencies. ### Install the client library Run your application and open your Application Insights Resource tab in the You've now enabled Application Insights for your application. All the following steps are optional and allow for further customization. -Not working? Check out the troubleshooting page for [ASP.NET Core](/troubleshoot/azure/azure-monitor/app-insights/opentelemetry-troubleshooting-dotnet), [Java](/troubleshoot/azure/azure-monitor/app-insights/opentelemetry-troubleshooting-java), [Node.js](/troubleshoot/azure/azure-monitor/app-insights/opentelemetry-troubleshooting-nodejs), or [Python](/troubleshoot/azure/azure-monitor/app-insights/opentelemetry-troubleshooting-python). - > [!IMPORTANT] > If you have two or more services that emit telemetry to the same Application Insights resource, you're required to [set Cloud Role Names](opentelemetry-configuration.md#set-the-cloud-role-name-and-the-cloud-role-instance) to represent them properly on the Application Map.
azure-monitor	Azure Monitor Workspace Manage	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/essentials/azure-monitor-workspace-manage.md	This article shows you how to create and delete an Azure Monitor workspace. When Use the following command to create an Azure Monitor workspace using Azure CLI. ```azurecli -az resource create --resource-group <resource-group-name> --namespace microsoft.monitor --resource-type accounts --name <azure-monitor-workspace-name> --location <location> --properties {} +az resource create --resource-group <resource-group-name> --namespace microsoft.monitor --resource-type accounts --name <azure-monitor-workspace-name> --location <location> --properties "{}" ``` ### [Resource Manager](#tab/resource-manager)
azure-monitor	Azure Monitor Data Explorer Proxy	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/azure-monitor-data-explorer-proxy.md	union AzureActivity, arg("").Resources ```kusto let CL1 = arg("").Resources ; union AzureActivity, CL1 \| take 10 +``` -```sql When you use the [`join` operator](/azure/data-explorer/kusto/query/joinoperator) instead of union, you need to use a [`hint`](/azure/data-explorer/kusto/query/joinoperator#join-hints) to combine the data in Azure Resource Graph with data in the Log Analytics workspace. Use `Hint.remote={Direction of the Log Analytics Workspace}`. For example: -kusto +```kusto Perf \| where ObjectName == "Memory" and (CounterName == "Available MBytes Memory") \| extend _ResourceId = replace_string(replace_string(replace_string(_ResourceId, 'microsoft.compute', 'Microsoft.Compute'), 'virtualmachines','virtualMachines'),"resourcegroups","resourceGroups") \| join hint.remote=left (arg("").Resources \| where type =~ 'Microsoft.Compute/virtualMachines' \| project _ResourceId=id, tags) on _ResourceId \| project-away _ResourceId1 \| where tostring(tags.env) == "prod" To create a new alert rule based on a cross-service query, follow the steps in [ * [Private Link](../logs/private-link-security.md) (private endpoints) and [IP restrictions](/azure/data-explorer/security-network-restrict-public-access) are not support cross-service queries. * mv-expand is limited to 2000 records. -* the following operators do not work with the cross query with ability with Azure Resource Graph: - -smv-apply(), rand(), arg_max() , arg_min(), avg() , avg_if(), countif(), sumif(), percentile() , percentiles() , percentilew() , percentilesw(), stdev() , stdevif() , stdevp(), variance() , variancep() , varianceif(). +* The following operators do not work with the cross query with ability with Azure Resource Graph: smv-apply(), rand(), arg_max() , arg_min(), avg() , avg_if(), countif(), sumif(), percentile() , percentiles() , percentilew() , percentilesw(), stdev() , stdevif() , stdevp(), variance() , variancep() , varianceif(). ## Next steps * [Write queries](/azure/data-explorer/write-queries)
azure-monitor	Data Collector Api	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-monitor/logs/data-collector-api.md	Last updated 08/08/2023- -# Send log data to Azure Monitor by using the HTTP Data Collector API (preview) +# Send log data to Azure Monitor by using the HTTP Data Collector API (deprecated) This article shows you how to use the HTTP Data Collector API to send log data to Azure Monitor from a REST API client. It describes how to format data that's collected by your script or application, include it in a request, and have that request authorized by Azure Monitor. We provide examples for Azure PowerShell, C#, and Python. > [!NOTE] -> The Azure Monitor HTTP Data Collector API is in public preview. +> The Azure Monitor HTTP Data Collector API has been deprecated and will no longer be functional as of 9/18/2026. It's been replaced by the [Logs ingestion API](logs-ingestion-api-overview.md). ## Concepts You can use the HTTP Data Collector API to send log data to a Log Analytics workspace in Azure Monitor from any client that can call a REST API. The client might be a runbook in Azure Automation that collects management data from Azure or another cloud, or it might be an alternative management system that uses Azure Monitor to consolidate and analyze log data. Any request to the Azure Monitor HTTP Data Collector API must include an authori Here's the format for the authorization header: -``` + +```sql Authorization: SharedKey <WorkspaceID>:<Signature> ``` Authorization: SharedKey <WorkspaceID>:<Signature> Use this format to encode the SharedKey signature string: -``` + +```ruby StringToSign = VERB + "\n" + Content-Length + "\n" + Content-Type + "\n" + StringToSign = VERB + "\n" + Here's an example of a signature string: -``` + +```ruby POST\n1024\napplication/json\nx-ms-date:Mon, 04 Apr 2016 08:00:00 GMT\n/api/logs ``` When you have the signature string, encode it by using the HMAC-SHA256 algorithm on the UTF-8-encoded string, and then encode the result as Base64. Use this format: -``` + +```sql Signature=Base64(HMAC-SHA256(UTF8(StringToSign))) ``` The following properties are reserved and shouldn't be used in a custom record t - TimeGenerated - RawData - ## Data limits The data posted to the Azure Monitor Data collection API is subject to certain constraints: public class ApiExample { ``` + ## Alternatives and considerations Although the Data Collector API should cover most of your needs as you collect f \| [Azure Data Explorer](/azure/data-explorer/ingest-data-overview) \| Azure Data Explorer, now generally available to the public, is the data platform that powers Application Insights Analytics and Azure Monitor Logs. By using the data platform in its raw form, you have complete flexibility (but require the overhead of management) over the cluster (Kubernetes role-based access control (RBAC), retention rate, schema, and so on). Azure Data Explorer provides many [ingestion options](/azure/data-explorer/ingest-data-overview#ingestion-methods), including [CSV, TSV, and JSON](/azure/kusto/management/mappings) files. \| <ul><li> Data that won't be correlated with any other data under Application Insights or Monitor Logs. </li><li> Data that requires advanced ingestion or processing capabilities that aren't available today in Azure Monitor Logs. </li></ul> \| + ## Next steps - Use the [Log Search API](./log-query-overview.md) to retrieve data from the Log Analytics workspace. - Learn more about how to [create a data pipeline with the Data Collector API](create-pipeline-datacollector-api.md) by using a Logic Apps workflow to Azure Monitor.+
azure-netapp-files	Azure Netapp Files Solution Architectures	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-netapp-files/azure-netapp-files-solution-architectures.md	na Previously updated : 06/12/2023 Last updated : 09/18/2023 # Solution architectures using Azure NetApp Files This section provides references to SAP on Azure solutions. * [DB2 Installation Guide on Azure NetApp Files](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/db2-installation-guide-on-anf/ba-p/3709437) * [Manual Recovery Guide for SAP DB2 on Azure VMs from Azure NetApp Files snapshot with AzAcSnap](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/manual-recovery-guide-for-sap-db2-on-azure-vms-from-azure-netapp/ba-p/3865379) * [SAP ASE 16.0 on Azure NetApp Files for SAP Workloads on SLES15](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-ase-16-0-on-azure-netapp-files-for-sap-workloads-on-sles15/ba-p/3729496) +* [SAP Netweaver 7.5 with MaxDB 7.9 on Azure using Azure NetApp Files](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-netweaver-7-5-with-maxdb-7-9-on-azure-using-azure-netapp/ba-p/3905041) ### SAP IQ-NLS
azure-portal	Azure Portal Safelist Urls	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-portal/azure-portal-safelist-urls.md	Title: Allow the Azure portal URLs on your firewall or proxy server description: To optimize connectivity between your network and the Azure portal and its services, we recommend you add these URLs to your allowlist. Previously updated : 08/22/2023 Last updated : 09/14/2023 graph.microsoftazure.us aadcdn.msauth.cn aadcdn.msftauth.cn login.live.com +catalogartifact.azureedge.net +store-images.s-microsoft.com .azure.cn .microsoft.cn *.microsoftonline.cn
azure-sql-edge	Backup Restore	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/backup-restore.md	Title: Back up and restore databases - Azure SQL Edge description: Learn about backup and restore capabilities in Azure SQL Edge. - Previously updated : 05/19/2020 Last updated : 09/14/2023 - +# Back up and restore databases in Azure SQL Edge -# Back up and restore databases in Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. -Azure SQL Edge is built on the latest versions of the Microsoft SQL Database Engine. It provides similar backup and restore database capabilities as those available in SQL Server on Linux and SQL Server running in containers. The backup and restore component provides an essential safeguard for protecting data stored in your Azure SQL Edge databases. +Azure SQL Edge is built on the latest versions of the Microsoft SQL Database Engine. It provides similar backup and restore database capabilities to SQL Server on Linux and SQL Server running in containers. The backup and restore component provides an essential safeguard for protecting data stored in your Azure SQL Edge databases. -To minimize the risk of catastrophic data loss, you should back up your databases periodically to preserve modifications to your data on a regular basis. A well-planned backup and restore strategy helps protect databases against data loss caused by a variety of failures. Test your strategy by restoring a set of backups and then recovering your database, to prepare you to respond effectively to a disaster. +To minimize the risk of catastrophic data loss, you should back up your databases periodically to preserve modifications to your data regularly. A well-planned backup and restore strategy helps protect databases against data loss caused by various failures. Test your strategy by restoring a set of backups and then recovering your database, to prepare you to respond effectively to a disaster. To read more about why backups are important, see [Backup and restore of SQL Server databases](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases/). Azure SQL Edge enables you to back up to and restore from both local storage and Azure SQL Edge supports the same backup types as SQL Server. For a complete list, see [Backup overview](/sql/relational-databases/backup-restore/backup-overview-sql-server/). -> [!IMPORTANT] +> [!IMPORTANT] > Databases created in Azure SQL Edge use the simple recovery model by default. As such, you can't perform log backups on these databases. If you need to do this, you'll need an administrator to change the database recovery model to the full recovery model. For a complete list of recovery models supported by SQL Server, see [Recovery model overview](/sql/relational-databases/backup-restore/recovery-models-sql-server#RMov). ### Back up to local disk -In the following example, you use the `BACKUP DATABASE` Transact-SQL command to create a database backup in the container. For the purpose of this example, you create a new folder called backup to store the backup files. +In the following example, you use the `BACKUP DATABASE` Transact-SQL command to create a database backup in the container. For this example, you create a new folder called backup to store the backup files. 1. Create a folder for the backups. Run this command on the host where your Azure SQL Edge container is running. In the following command, replace <AzureSQLEdge_Container_Name> with the name of the Azure SQL Edge container in your deployment. - ```bash - sudo docker exec -it <AzureSQLEdge_Container_Name> mkdir /var/opt/mssql/backup - ``` + ```bash + sudo docker exec -it <AzureSQLEdge_Container_Name> mkdir /var/opt/mssql/backup + ``` -2. Connect to the Azure SQL Edge instance by using SQL Server Management Studio (SSMS), or by using Azure Data Studio. Run the `BACKUP DATABASE` command to take the backup of your user database. In the following example, you're taking the backup of the IronOreSilicaPrediction database. +1. Connect to the Azure SQL Edge instance by using SQL Server Management Studio (SSMS), or by using Azure Data Studio. Run the `BACKUP DATABASE` command to take the backup of your user database. In the following example, you're taking the backup of the `IronOreSilicaPrediction` database. - ```sql - BACKUP DATABASE [IronOreSilicaPrediction] - TO DISK = N'/var/opt/mssql/backup/IronOrePredictDB.bak' - WITH NOFORMAT, NOINIT, NAME = N'IronOreSilicaPrediction-Full Database Backup', - SKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 10 - GO - ``` + ```sql + BACKUP DATABASE [IronOreSilicaPrediction] TO DISK = N'/var/opt/mssql/backup/IronOrePredictDB.bak' + WITH NOFORMAT, + NOINIT, + NAME = N'IronOreSilicaPrediction-Full Database Backup', + SKIP, + NOREWIND, + NOUNLOAD, + COMPRESSION, + STATS = 10; + GO + ``` -3. After you run the command, if the backup of the database is successful, you'll see messages similar to the following in the results section of SSMS or Azure Data Studio. +1. After you run the command, if the backup of the database is successful, you'll see messages similar to the following in the results section of SSMS or Azure Data Studio. - ```txt + ```output 10 percent processed. 20 percent processed. 30 percent processed. In the following example, you use the `BACKUP DATABASE` Transact-SQL command to ### Back up to URL -Azure SQL Edge supports backups to both page blobs and block blobs. For more information, see [Back up to block blob vs page blob](/sql/relational-databases/backup-restore/sql-server-backup-to-url#blockbloborpageblob). In the following example, the database IronOreSilicaPrediction is being backed up to a block blob. +Azure SQL Edge supports backups to both page blobs and block blobs. For more information, see [Back up to block blob vs page blob](/sql/relational-databases/backup-restore/sql-server-backup-to-url#blockbloborpageblob). In the following example, the database `IronOreSilicaPrediction` is being backed up to a block blob. 1. To configure backups to block blobs, first generate a shared access signature (SAS) token that you can use to create a SQL Server credential on Azure SQL Edge. The script creates a SAS that is associated with a stored access policy. For more information, see [Shared access signatures, part 1: Understanding the SAS model](../storage/common/storage-sas-overview.md). The script also writes the T-SQL command required to create the credential on SQL Server. The following script assumes that you already have an Azure subscription with a storage account, and a storage container for the backups. ```PowerShell - # Define global variables for the script + # Define global variables for the script $subscriptionName='<your subscription name>' # the name of subscription name you will use $resourcegroupName = '<your resource group name>' # the name of resource group you will use $storageAccountName= '<your storage account name>' # the storage account name you will use for backups - $containerName= '<your storage container name>' # the storage container name to which you will attach the SAS policy with its SAS token - $policyName = 'SASPolicy' # the name of the SAS policy + $containerName= '<your storage container name>' # the storage container name to which you will attach the SAS policy with its SAS token + $policyName = 'SASPolicy' # the name of the SAS policy # adds an authenticated Azure account for use in the session Login-AzAccount Azure SQL Edge supports backups to both page blobs and block blobs. For more inf Select-AzSubscription -Subscription $subscriptionName # Generate the SAS token - $sa = Get-AzStorageAccount -ResourceGroupName $resourcegroupName -Name $storageAccountName - $storagekey = Get-AzStorageAccountKey -ResourceGroupName $resourcegroupName -Name $storageAccountName + $sa = Get-AzStorageAccount -ResourceGroupName $resourcegroupName -Name $storageAccountName + $storagekey = Get-AzStorageAccountKey -ResourceGroupName $resourcegroupName -Name $storageAccountName $storageContext = New-AzStorageContext -StorageAccountName $storageAccountName -StorageAccountKey $storagekey[0].Value $cbc = Get-AzStorageContainer -Name $containerName -Context $storageContext $policy = New-AzStorageContainerStoredAccessPolicy -Container $containerName -Policy $policyName -Context $storageContext -ExpiryTime $(Get-Date).ToUniversalTime().AddYears(10) -Permission "rwld" $sas = New-AzStorageContainerSASToken -Policy $policyName -Context $storageContext -Container $containerName Write-Host 'Shared Access Signature= '$($sas.Substring(1))'' - # Outputs the Transact SQL to the clipboard and to the screen to create the credential using the Shared Access Signature - Write-Host 'Credential T-SQL' + # Outputs the Transact SQL to the clipboard and to the screen to create the credential using the Shared Access Signature + Write-Host 'Credential T-SQL' $tSql = "CREATE CREDENTIAL [{0}] WITH IDENTITY='Shared Access Signature', SECRET='{1}'" -f $cbc.CloudBlobContainer.Uri.AbsoluteUri,$sas.Substring(1) - $tSql \| clip + $tSql \| clip Write-Host $tSql ``` After successfully running the script, copy the `CREATE CREDENTIAL` command to a query tool. Then connect to an instance of SQL Server, and run the command to create the credential with the SAS. -2. Connect to the Azure SQL Edge instance by using SSMS or Azure Data Studio, and create the credential by using the command from the previous step. Make sure to replace the `CREATE CREDENTIAL` command with the actual output from the previous step. +1. Connect to the Azure SQL Edge instance by using SSMS or Azure Data Studio, and create the credential by using the command from the previous step. Make sure to replace the `CREATE CREDENTIAL` command with the actual output from the previous step. ```sql - IF NOT EXISTS + IF NOT EXISTS (SELECT * FROM sys.credentials - WHERE name = 'https://<mystorageaccountname>.blob.core.windows.net/<mystorageaccountcontainername>') + WHERE name = 'https://<mystorageaccountname>.blob.core.windows.net/<mystorageaccountcontainername>') CREATE CREDENTIAL [https://<mystorageaccountname>.blob.core.windows.net/<mystorageaccountcontainername>] - WITH IDENTITY = 'SHARED ACCESS SIGNATURE', + WITH IDENTITY = 'SHARED ACCESS SIGNATURE', SECRET = '<SAS_TOKEN>'; ``` -3. The following command takes a backup of the IronOreSilicaPrediction to the Azure storage container. +1. The following command takes a backup of the `IronOreSilicaPrediction` to the Azure storage container. ```sql BACKUP DATABASE IronOreSilicaPrediction TO URL = 'https://<mystorageaccountname>.blob.core.windows.net/<mycontainername>/IronOreSilicaPrediction.bak' - With MAXTRANSFERSIZE = 4194304,BLOCKSIZE=65536; + With MAXTRANSFERSIZE = 4194304,BLOCKSIZE=65536; GO ``` Azure SQL Edge supports backups to both page blobs and block blobs. For more inf In Azure SQL Edge, you can restore from a local disk, a network location, or an Azure Blob storage account. For more information about restore and recovery in SQL Server, see [Restore and recovery overview](/sql/relational-databases/backup-restore/restore-and-recovery-overview-sql-server). For an overview of the simple recovery model in SQL Server, see [Complete database restores (simple recovery model)](/sql/relational-databases/backup-restore/complete-database-restores-simple-recovery-model). -> [!IMPORTANT] -> Databases created in Azure SQL Edge cannot be restored on an instance of Microsoft SQL Server or Azure SQL. Additionally, a database created on Microsoft SQL Server or Azure SQL can be restored on Azure SQL Edge, provided the database does not contain any of the features not supported by Azure SQL Edge. +> [!IMPORTANT] +> Databases created in Azure SQL Edge can't be restored on an instance of Microsoft SQL Server or Azure SQL. Additionally, a database created on Microsoft SQL Server or Azure SQL can be restored on Azure SQL Edge, provided the database doesn't contain any of the features not supported by Azure SQL Edge. ### Restore from a local disk -This example uses the IronOreSilicaPrediction backup that you made in the previous example. Now, you'll restore it as a new database with a different name. +This example uses the `IronOreSilicaPrediction` backup that you made in the previous example. Now, you'll restore it as a new database with a different name. 1. If the database backup file isn't already present in the container, you can use the following command to copy the file into the container. The following example assumes that the backup file is present on the local host, and is being copied to the /var/opt/mssql/backup folder into an Azure SQL Edge container named sql1. This example uses the IronOreSilicaPrediction backup that you made in the prev sudo docker cp IronOrePredictDB.bak sql1:/var/opt/mssql/backup ``` -2. Connect to the Azure SQL Edge instance by using SSMS or Azure Data Studio to run the restore command. In the following example, IronOrePredictDB.bak is restored to create a new database, IronOreSilicaPrediction_2. +1. Connect to the Azure SQL Edge instance by using SSMS or Azure Data Studio to run the restore command. In the following example, `IronOrePredictDB.bak` is restored to create a new database, `IronOreSilicaPrediction_2`. ```sql Restore FilelistOnly from disk = N'/var/opt/mssql/backup/IronOrePredictDB.bak' This example uses the IronOreSilicaPrediction backup that you made in the prev Restore Database IronOreSilicaPrediction_2 From disk = N'/var/opt/mssql/backup/IronOrePredictDB.bak' WITH MOVE 'IronOreSilicaPrediction' TO '/var/opt/mssql/datf', - MOVE 'IronOreSilicaPrediction_log' TO '/var/opt/mssql/data/IronOreSilicaPrediction_Primary_2.ldf' + MOVE 'IronOreSilicaPrediction_log' TO '/var/opt/mssql/data/IronOreSilicaPrediction_Primary_2.ldf'; ``` -3. After you run the restore command, if the restore operation was successful, you'll see messages similar to the following in the output window. +1. After you run the restore command, if the restore operation was successful, you'll see messages similar to the following in the output window. - ```txt + ```output Processed 51648 pages for database 'IronOreSilicaPrediction_2', file 'IronOreSilicaPrediction' on file 1. Processed 2 pages for database 'IronOreSilicaPrediction_2', file 'IronOreSilicaPrediction_log' on file 1. RESTORE DATABASE successfully processed 51650 pages in 6.543 seconds (61.670 MB/sec). This example uses the IronOreSilicaPrediction backup that you made in the prev ### Restore from URL -Azure SQL Edge also supports restoring a database from an Azure Storage account. You can restore from either the block blobs or page blob backups. In the following example, the IronOreSilicaPrediction_2020_04_16.bak database backup file on a block blob is restored to create the database, IronOreSilicaPrediction_3. +Azure SQL Edge also supports restoring a database from an Azure Storage account. You can restore from either the block blobs or page blob backups. In the following example, the `IronOreSilicaPrediction_2020_04_16.bak` database backup file on a block blob is restored to create the database, `IronOreSilicaPrediction_3`. ```sql RESTORE DATABASE IronOreSilicaPrediction_3 FROM URL = 'https://mystorageaccount.blob.core.windows.net/mysecondcontainer/IronOreSilicaPrediction_2020_04_16.bak' -WITH MOVE 'IronOreSilicaPrediction' TO '/var/opt/mssql/datf', +WITH MOVE 'IronOreSilicaPrediction' TO '/var/opt/mssql/datf', MOVE 'IronOreSilicaPrediction_log' TO '/var/opt/mssql/data/IronOreSilicaPrediction_Primary_3.ldf', STATS = 10; ```
azure-sql-edge	Configure Replication	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/configure-replication.md	Title: Configure replication to Azure SQL Edge description: Learn about configuring replication to Azure SQL Edge. - Previously updated : 05/19/2020 Last updated : 09/14/2023 - +# Configure replication to Azure SQL Edge -# Configure replication to Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. -You can configure an instance of Azure SQL Edge as the push subscriber for one-way transactional replication or snapshot replication. This instance can't act as the publisher or the distributor for a transactional replication configuration. Note that Azure SQL Edge doesn't support merge replication, peer-to-peer replication, or Oracle publishing. +You can configure an instance of Azure SQL Edge as the push subscriber for one-way transactional replication or snapshot replication. This instance can't act as the publisher or the distributor for a transactional replication configuration. Azure SQL Edge doesn't support merge replication, peer-to-peer replication, or Oracle publishing. ## Supported configurations - + - The instance of Azure SQL Edge must be a push subscriber for a publisher. - The publisher and the distributor can be either: - An instance of SQL Server running on-premises, or an instance of SQL Server running in an Azure virtual machine. For more information, see [SQL Server on Azure Virtual Machines overview](/azure/azure-sql/virtual-machines/index). SQL Server instances must be using a version later than SQL Server 2016. - - An instance of Azure SQL Managed Instance. SQL Managed Instance can host publisher, distributor, and subscriber databases. For more information, see [Replication with SQL Database Managed Instance](/azure/sql-database/replication-with-sql-database-managed-instance/). + - An instance of Azure SQL Managed Instance. SQL Managed Instance can host publisher, distributor, and subscriber databases. For more information, see [Replication with SQL Managed Instance](/azure/sql-database/replication-with-sql-database-managed-instance/). -- The distribution database and the replication agents can't be placed on an instance of Azure SQL Edge. +- The distribution database and the replication agents can't be placed on an instance of Azure SQL Edge. -> [!NOTE] -> If you attempt to configure replication by using an unsupported version, you might receive the following two errors: MSSQL_REPL20084 ("The process could not connect to Subscriber.") and MSSQL_REPL40532 ("Cannot open server \<name> requested by the login. The login failed."). +> [!NOTE] +> If you attempt to configure replication by using an unsupported version, you might receive the following two errors: MSSQL_REPL20084 ("The process could not connect to Subscriber.") and MSSQL_REPL40532 ("Cannot open server \<name> requested by the login. The login failed."). ## Remarks The following requirements and best practices are important to understand as you - You can configure replication by using [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms). You can also do so by running Transact-SQL statements on the publisher, by using either SQL Server Management Studio or [Azure Data Studio](/sql/azure-data-studio/download-azure-data-studio). - To replicate to an instance of Azure SQL Edge, you must use SQL Server authentication to sign in. - Replicated tables must have a primary key.-- A single publication on SQL Server can support both Azure SQL Edge and SQL Server (on-premises and SQL Server in an Azure virtual machine) subscribers. -- Replication management, monitoring, and troubleshooting must be performed from the SQL Server instance. -- Only push subscriptions to Azure SQL Edge are supported. -- Only `@subscriber_type = 0` is supported in the stored procedure `sp_addsubscription` for Azure SQL Edge. +- A single publication on SQL Server can support both Azure SQL Edge and SQL Server (on-premises and SQL Server in an Azure virtual machine) subscribers. +- Replication management, monitoring, and troubleshooting must be performed from the SQL Server instance. +- Only push subscriptions to Azure SQL Edge are supported. +- Only `@subscriber_type = 0` is supported in the stored procedure `sp_addsubscription` for Azure SQL Edge. - Azure SQL Edge doesn't support bi-directional, immediate, updatable, or peer-to-peer replication.-- Azure SQL Edge only supports a subset of features available in SQL Server or SQL Managed Instance. If you attempt to replicate a database (or objects within the database) that contains one or more unsupported features, the attempt fails. For example, if you attempt to replicate a database that contains objects with spatial data types, you'll receive an error. For more information, see [Supported features of Azure SQL Edge](features.md). +- Azure SQL Edge only supports a subset of features available in SQL Server or SQL Managed Instance. If you attempt to replicate a database (or objects within the database) that contains one or more unsupported features, the attempt fails. For example, if you attempt to replicate a database that contains objects with spatial data types, you receive an error. For more information, see [Supported features of Azure SQL Edge](features.md). ## Initialize reference data on an instance of Azure SQL Edge You might want to initialize your instance with reference data that changes over time. For example, you might want to update machine learning models on your instance of Azure SQL Edge, after they have been trained on a SQL Server instance. Here's how to initialize your instance in such a scenario: -1. Create a transactional replication publication on a SQL Server database. -2. On the SQL Server instance, use the New Subscription Wizard or Transact-SQL statements to create a push to subscription to Azure SQL Edge. -3. You can initialize the replicated database on Azure SQL Edge by using a snapshot generated by the snapshot agent, and distributed and delivered by the distribution agent. Alternatively, you can initialize by using a backup of the database from the publisher. Remember that if the database backup contains objects or features not supported by Azure SQL Edge, the restore operation fails. +1. Create a transactional replication publication on a SQL Server database. +1. On the SQL Server instance, use the New Subscription Wizard or Transact-SQL statements to create a push to subscription to Azure SQL Edge. +1. You can initialize the replicated database on Azure SQL Edge by using a snapshot generated by the snapshot agent, and distributed and delivered by the distribution agent. Alternatively, you can initialize by using a backup of the database from the publisher. Remember that if the database backup contains objects or features not supported by Azure SQL Edge, the restore operation fails. ## Limitations The following options aren't supported for Azure SQL Edge subscriptions: -- Copy file groups association -- Copy table partitioning schemes -- Copy index partitioning schemes -- Copy user defined statistics -- Copy default bindings -- Copy rule bindings -- Copy fulltext indexes -- Copy XML XSD -- Copy XML indexes -- Copy permissions -- Copy spatial indexes -- Copy filtered indexes -- Copy data compression attribute -- Copy sparse column attribute +- Copy file groups association +- Copy table partitioning schemes +- Copy index partitioning schemes +- Copy user defined statistics +- Copy default bindings +- Copy rule bindings +- Copy fulltext indexes +- Copy XML XSD +- Copy XML indexes +- Copy permissions +- Copy spatial indexes +- Copy filtered indexes +- Copy data compression attribute +- Copy sparse column attribute - Copy filestream, `hierarchyid`, or spatial data types-- Convert `hierarchyid` to MAX data types -- Convert spatial to MAX data types -- Copy extended properties -- Copy permissions +- Convert `hierarchyid` to MAX data types +- Convert spatial to MAX data types +- Copy extended properties +- Copy permissions ## Examples Create a publication and a push subscription. For more information, see: - + - [Create a publication](/sql/relational-databases/replication/publish/create-a-publication)-- [Create a push subscription](/sql/relational-databases/replication/create-a-push-subscription/) by using the Azure SQL Edge server name and IP as the subscriber (for example, myEdgeinstance,1433), and a database name on the Azure SQL Edge instance as the destination database (for example, AdventureWorks). +- [Create a push subscription](/sql/relational-databases/replication/create-a-push-subscription/) by using the Azure SQL Edge server name and IP as the subscriber (for example, myEdgeinstance,1433), and a database name on the Azure SQL Edge instance as the destination database (for example, AdventureWorks). -## Next steps +## Next steps - [Create a publication](/sql/relational-databases/replication/publish/create-a-publication) - [Create a push subscription](/sql/relational-databases/replication/create-a-push-subscription/) - [Types of replication](/sql/relational-databases/replication/types-of-replication) - [Monitoring (replication)](/sql/relational-databases/replication/monitor/monitoring-replication)-- [Initialize a subscription](/sql/relational-databases/replication/initialize-a-subscription) +- [Initialize a subscription](/sql/relational-databases/replication/initialize-a-subscription)
azure-sql-edge	Configure	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/configure.md	Title: Configure Azure SQL Edge description: Learn about configuring Azure SQL Edge. - Previously updated : 09/22/2020 Last updated : 09/14/2023 - -+ - # Configure Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + Azure SQL Edge supports configuration through one of the following two options: - Environment variables - An mssql.conf file placed in the /var/opt/mssql folder -> [!NOTE] +> [!NOTE] > Setting environment variables overrides the settings specified in the mssql.conf file. ## Configure by using environment variables Azure SQL Edge exposes several different environment variables that can be used to configure the SQL Edge container. These environment variables are a subset of the ones available for SQL Server on Linux. For more information on SQL Server on Linux environment variables, see [Environment variables](/sql/linux/sql-server-linux-configure-environment-variables/). -The following new environment variables were added to Azure SQL Edge. - -\| Environment variable \| Description \| Values \| -\|--\|--\| - \| -\| PlanId \| Specifies the Azure SQL Edge SKU to be used during initialization. This environment variable is only required when deploying Azure SQL Edge using Azure IoT Edge. \| asde-developer-on-iot-edge or asde-premium-on-iot-edge \| -\| MSSQL_TELEMETRY_ENABLED \| Enable or disable usage and diagnostics data collection. \| TRUE or FALSE \| -\| MSSQL_TELEMETRY_DIR \| Sets the target directory for the usage and diagnostics data collection audit files. \| Folder location within SQL Edge container. This folder can be mapped to a host volume using either mount points or data volumes. \| -\| MSSQL_PACKAGE \| Specifies the location of the dacpac or bacpac package to be deployed. \| Folder, file, or SAS URL containing the dacpac or bacpac packages. For more information, refer [Deploy SQL Database DACPAC and BACPAC packages in SQL Edge](deploy-dacpac.md). \| +The following new environment variables were added to Azure SQL Edge. +\| Environment variable \| Description \| Values \| +\| \| \| \| +\| PlanId \| Specifies the Azure SQL Edge SKU to be used during initialization. This environment variable is only required when deploying Azure SQL Edge using Azure IoT Edge. \| asde-developer-on-iot-edge or asde-premium-on-iot-edge \| +\| MSSQL_TELEMETRY_ENABLED \| Enable or disable usage and diagnostics data collection. \| TRUE or FALSE \| +\| MSSQL_TELEMETRY_DIR \| Sets the target directory for the usage and diagnostics data collection audit files. \| Folder location within SQL Edge container. This folder can be mapped to a host volume using either mount points or data volumes. \| +\| MSSQL_PACKAGE \| Specifies the location of the dacpac or bacpac package to be deployed. \| Folder, file, or SAS URL containing the dacpac or bacpac packages. For more information, see [Deploy SQL Database DACPAC and BACPAC packages in SQL Edge](deploy-dacpac.md). \| -The following SQL Server on Linux environment variable isn't supported for Azure SQL Edge. If defined, this environment variable will be ignored during container initialization. +The following SQL Server on Linux environment variable isn't supported for Azure SQL Edge. If defined, this environment variable is ignored during container initialization. \| Environment variable \| Description \| -\|--\|--\| -\| MSSQL_ENABLE_HADR \| Enable availability group. For example, 1 is enabled, and 0 is disabled. \| +\| \| \| +\| MSSQL_ENABLE_HADR \| Enable availability group. For example, `1` is enabled, and `0` is disabled. \| -> [!IMPORTANT] +> [!IMPORTANT] > The MSSQL_PID environment variable for SQL Edge only accepts Premium and Developer as the valid values. Azure SQL Edge doesn't support initialization using a product key. ### Specify the environment variables Specify environment variables for SQL Edge when you deploy the service through t Add values in Environment Variables. -![Set by using environment variables list](media/configure/set-environment-variables.png) Add values in Container Create Options. -![Set by using container create options](media/configure/set-environment-variables-using-create-options.png) -> [!NOTE] +> [!NOTE] > In the disconnected deployment mode, environment variables can be specified using the `-e` or `--env` or the `--env-file` option of the `docker run` command. ## Configure by using an `mssql.conf` file Add values in Container Create Options. Azure SQL Edge doesn't include the [mssql-conf configuration utility](/sql/linux/sql-server-linux-configure-mssql-conf/) like SQL Server on Linux does. You need to manually configure the mssql.conf file and place it in the persistent storage drive that is mapped to the /var/opt/mssql/ folder in the SQL Edge module. When you're deploying SQL Edge from Azure Marketplace, this mapping is specified as the Mounts option in the Container Create Options. ```json +{ + "Mounts": [ { - "Mounts": [ - { - "Type": "volume", - "Source": "sqlvolume", - "Target": "/var/opt/mssql" - } - ] - } + "Type": "volume", + "Source": "sqlvolume", + "Target": "/var/opt/mssql" } + ] +} ``` -The following new mssql.conf options were added for Azure SQL Edge. +The following new mssql.conf options were added for Azure SQL Edge. -\|Option\|Description\| -\|:\|:\| -\|customerfeedback \| Choose if SQL Server sends feedback to Microsoft. For more information, see [Disable usage and diagnostic data collection](usage-and-diagnostics-data-configuration.md#disable-usage-and-diagnostic-data-collection)\| -\|userrequestedlocalauditdirectory \| Sets the target directory for the usage and diagnostics data collection audit files. For more information, see [Local audit of usage and diagnostic data collection](usage-and-diagnostics-data-configuration.md#local-audit-of-usage-and-diagnostic-data-collection) \| +\| Option \| Description \| +\| : \| : \| +\| customerfeedback \| Choose if SQL Server sends feedback to Microsoft. For more information, see [Disable usage and diagnostic data collection](usage-and-diagnostics-data-configuration.md#disable-usage-and-diagnostic-data-collection) \| +\| userrequestedlocalauditdirectory \| Sets the target directory for the usage and diagnostics data collection audit files. For more information, see [Local audit of usage and diagnostic data collection](usage-and-diagnostics-data-configuration.md#local-audit-of-usage-and-diagnostic-data-collection) \| The following mssql.conf options aren't applicable to SQL Edge: -\|Option\|Description\| -\|:\|:\| -\|Customer feedback \| Choose if SQL Server sends feedback to Microsoft. \| -\|Database mail profile \| Set the default database mail profile for SQL Server on Linux. \| -\|High availability \| Enable Availability Groups. \| -\|Microsoft Distributed Transaction Coordinator \| Configure and troubleshoot MSDTC on Linux. Additional distributed transaction-related configuration options aren't supported for SQL Edge. For more information on these additional configuration options, see [Configure MSDTC](/sql/linux/sql-server-linux-configure-mssql-conf#msdtc). \| -\|ML Services EULAs \| Accept R and Python EULAs for Azure Machine Learning packages. Applies to SQL Server 2019 only.\| -\|outboundnetworkaccess \|Enable outbound network access for [Machine Learning Services](/sql/linux/sql-server-linux-setup-machine-learning/) R, Python, and Java extensions.\| +\| Option \| Description \| +\| : \| : \| +\| Customer feedback \| Choose if SQL Server sends feedback to Microsoft. \| +\| Database mail profile \| Set the default database mail profile for SQL Server on Linux. \| +\| High availability \| Enable Availability Groups. \| +\| Microsoft Distributed Transaction Coordinator \| Configure and troubleshoot MSDTC on Linux. Additional distributed transaction-related configuration options aren't supported for SQL Edge. For more information on these additional configuration options, see [Configure MSDTC](/sql/linux/sql-server-linux-configure-mssql-conf#msdtc). \| +\| ML Services EULAs \| Accept R and Python EULAs for Azure Machine Learning packages. Applies to SQL Server 2019 only. \| +\| outboundnetworkaccess \| Enable outbound network access for [Machine Learning Services](/sql/linux/sql-server-linux-setup-machine-learning/) R, Python, and Java extensions. \| The following sample mssql.conf file works for SQL Edge. For more information on the format for an `mssql.conf` file, see [mssql.conf format](/sql/linux/sql-server-linux-configure-mssql-conf#mssql-conf-format). traceflag2 = 1204 ## Run Azure SQL Edge as non-root user -By default, the Azure SQL Edge containers run with a non-root user/group. When deployed through the Azure Marketplace (or using docker run), unless a different user/group is specified, SQL Edge containers starts up as the mssql (non-root) user. To specify a different non-root user during deployment, add the `"User": "<name\|uid>[:<group\|gid>]"` key-value pair under container create options. In the example below SQL Edge is configured to start as the user `IoTAdmin`. +By default, the Azure SQL Edge containers run with a non-root user/group. When deployed through the Azure Marketplace (or using `docker run`), unless a different user/group is specified, SQL Edge containers starts up as the mssql (non-root) user. To specify a different non-root user during deployment, add the `"User": "<name\|uid>[:<group\|gid>]"` key-value pair under container create options. In the following example, SQL Edge is configured to start as the user `IoTAdmin`. ```json { By default, the Azure SQL Edge containers run with a non-root user/group. When d } ``` -To allow the non-root user to access DB files that are on mounted volumes, ensure that the user/group you run the container under, has read & write permissions on the persistent file storage. In the example below we set the non-root user with user_id 10001 as the owner of the files. +To allow the non-root user to access DB files that are on mounted volumes, ensure that the user/group you run the container under, has read & write permissions on the persistent file storage. In the following example, we set the non-root user with `user_id` of `10001` as the owner of the files. ```bash chown -R 10001:0 <database file dir> ``` -### Upgrading from earlier CTP releases +### Upgrade from earlier CTP releases Earlier CTPs of Azure SQL Edge were configured to run as the root users. The following options are available when upgrading from earlier CTPs. - Continue to use the root user - To continue using the root user, add the `"User": "0:0"` key-value pair under container create options.-- Use the default mssql user - To use the default mssql user, follow the steps below - - Add a user named mssql on the docker host. In the example below, we add a user mssql with ID 10001. This user is also added to the root group. +- Use the default mssql user - To use the default mssql user, follow these steps: + - Add a user named `mssql` on the Docker host. In the example below, we add a user mssql with ID 10001. This user is also added to the root group. + ```bash sudo useradd -M -s /bin/bash -u 10001 -g 0 mssql ``` - - Change the permission on the directory/mount volume where the database file resides + + - Change the permission on the directory/mount volume where the database file resides + ```bash sudo chgrp -R 0 /var/lib/docker/volumes/kafka_sqldata/ sudo chmod -R g=u /var/lib/docker/volumes/kafka_sqldata/ ```+ - Use a different non-root user account - To use a different non-root user account - - Update the container create options to specify add `"User": "user_name \| user_id` key-value pair under container create options. Replace user_name or user_id with an actual user_name or user_id from your docker host. + - Update the container create options to specify add `"User": "user_name \| user_id` key-value pair under container create options. Replace user_name or user_id with an actual user_name or user_id from your Docker host. - Change the permissions on the directory/mount volume. ## Persist your data Your Azure SQL Edge configuration changes and database files are persisted in the container even if you restart the container with `docker stop` and `docker start`. However, if you remove the container with `docker rm`, everything in the container is deleted, including Azure SQL Edge and your databases. The following section explains how to use data volumes to persist your database files even if the associated containers are deleted. -> [!IMPORTANT] -> For Azure SQL Edge, it is critical that you understand data persistence in Docker. In addition to the discussion in this section, see Docker's documentation on [how to manage data in Docker containers](https://docs.docker.com/engine/tutorials/dockervolumes/). +> [!IMPORTANT] +> For Azure SQL Edge, it's critical that you understand data persistence in Docker. In addition to the discussion in this section, see Docker's documentation on [how to manage data in Docker containers](https://docs.docker.com/engine/tutorials/dockervolumes/). ### Mount a host directory as data volume docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<YourStrong!Passw0rd>" -p 14 This technique also enables you to share and view the files on the host outside of Docker. -> [!IMPORTANT] -> Host volume mapping for Docker on Windows does not currently support mapping the complete `/var/opt/mssql` directory. However, you can map a subdirectory, such as `/var/opt/mssql/data` to your host machine. +> [!IMPORTANT] +> Host volume mapping for Docker on Windows doesn't currently support mapping the complete `/var/opt/mssql` directory. However, you can map a subdirectory, such as `/var/opt/mssql/data` to your host machine. -> [!IMPORTANT] -> Host volume mapping for Docker on Mac with the Azure SQL Edge image is not supported at this time. Use data volume containers instead. This restriction is specific to the `/var/opt/mssql` directory. Reading from a mounted directory works fine. For example, you can mount a host directory using -v on Mac and restore a backup from a .bak file that resides on the host. +> [!IMPORTANT] +> Host volume mapping for Docker on macOS with the Azure SQL Edge image isn't supported at this time. Use data volume containers instead. This restriction is specific to the `/var/opt/mssql` directory. Reading from a mounted directory works fine. For example, you can mount a host directory using `-v` on macOS and restore a backup from a `.bak` file that resides on the host. ### Use data volume containers docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=<YourStrong!Passw0rd>' -p 14 docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=<YourStrong!Passw0rd>" -p 1433:1433 -v sqlvolume:/var/opt/mssql -d mcr.microsoft.com/azure-sql-edge ``` -> [!NOTE] -> This technique for implicitly creating a data volume in the run command does not work with older versions of Docker. In that case, use the explicit steps outlined in the Docker documentation, [Creating and mounting a data volume container](https://docs.docker.com/engine/tutorials/dockervolumes/#creating-and-mounting-a-data-volume-container). +> [!NOTE] +> This technique for implicitly creating a data volume in the run command doesn't work with older versions of Docker. In that case, use the explicit steps outlined in the Docker documentation, [Creating and mounting a data volume container](https://docs.docker.com/engine/tutorials/dockervolumes/#creating-and-mounting-a-data-volume-container). Even if you stop and remove this container, the data volume persists. You can view it with the `docker volume ls` command. If you then create another container with the same volume name, the new containe To remove a data volume container, use the `docker volume rm` command. -> [!WARNING] +> [!WARNING] > If you delete the data volume container, any Azure SQL Edge data in the container is permanently deleted. - ## Next steps - [Connect to Azure SQL Edge](connect.md)
azure-sql-edge	Connect	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/connect.md	Title: Connect and query Azure SQL Edge description: Learn how to connect to and query Azure SQL Edge. Previously updated : 07/28/2023 Last updated : 09/14/2023 # Connect and query Azure SQL Edge -In Azure SQL Edge, after you deploy a container, you can connect to the database engine from any of the following locations: +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + +In Azure SQL Edge, after you deploy a container, you can connect to the Database Engine from any of the following locations: - Inside the container - From another Docker container running on the same host
azure-sql-edge	Create External Stream Transact Sql	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/create-external-stream-transact-sql.md	Title: CREATE EXTERNAL STREAM (Transact-SQL) - Azure SQL Edge description: Learn about the CREATE EXTERNAL STREAM statement in Azure SQL Edge - Previously updated : 07/27/2020 Last updated : 09/14/2023 - - # CREATE EXTERNAL STREAM (Transact-SQL) -The EXTERNAL STREAM object has a dual purpose of both an input and output stream. It can be used as an input to query streaming data from event ingestion services such as Azure Event Hub, Azure IoT Hub (or Edge Hub) or Kafka or it can be used as an output to specify where and how to store results from a streaming query. +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + +The EXTERNAL STREAM object has a dual purpose of both an input and output stream. It can be used as an input to query streaming data from event ingestion services such as Azure Event Hubs, Azure IoT Hub (or Edge Hub) or Kafka or it can be used as an output to specify where and how to store results from a streaming query. -An EXTERNAL STREAM can also be specified and created as both an output and input for services such as Event Hub or Blob storage. This facilitates chaining scenarios where a streaming query is persisting results to the external stream as output and another streaming query reading from the same external stream as input. +An EXTERNAL STREAM can also be specified and created as both an output and input for services such as Event Hubs or Blob storage. This facilitates chaining scenarios where a streaming query is persisting results to the external stream as output and another streaming query reading from the same external stream as input. Azure SQL Edge currently only supports the following data sources as stream inputs and outputs. \| Data source type \| Input \| Output \| Description \| -\|\|-\|--\|\| -\| Azure IoT Edge hub \| Y \| Y \| Data source to read and write streaming data to an Azure IoT Edge hub. For more information, see [IoT Edge Hub](../iot-edge/iot-edge-runtime.md#iot-edge-hub).\| -\| SQL Database \| N \| Y \| Data source connection to write streaming data to SQL Database. The database can be a local database in Azure SQL Edge, or a remote database in SQL Server or Azure SQL Database.\| -\| Kafka \| Y \| N \| Data source to read streaming data from a Kafka topic. Kafka support is not available for the ARM64 version of Azure SQL Edge.\| -- +\| \| \| \| \| +\| Azure IoT Edge hub \| Y \| Y \| Data source to read and write streaming data to an Azure IoT Edge hub. For more information, see [IoT Edge Hub](../iot-edge/iot-edge-runtime.md#iot-edge-hub). \| +\| SQL Database \| N \| Y \| Data source connection to write streaming data to SQL Database. The database can be a local database in Azure SQL Edge, or a remote database in SQL Server or Azure SQL Database. \| +\| Kafka \| Y \| N \| Data source to read streaming data from a Kafka topic. \| ## Syntax ```syntaxsql -CREATE EXTERNAL STREAM {external_stream_name} -( <column_definition> [, <column_definition> ] * ) -- Used for Inputs - optional +CREATE EXTERNAL STREAM { external_stream_name } +( <column_definition> [ , <column_definition> ] * ) -- Used for Inputs - optional WITH ( <with_options> ) <column_definition> ::= WITH ( <with_options> ) [ ( precision [ , scale ] \| max ) ] <with_options> ::= - DATA_SOURCE = data_source_name, - LOCATION = location_name, - [FILE_FORMAT = external_file_format_name], --Used for Inputs - optional - [<optional_input_options>], - [<optional_output_options>], + DATA_SOURCE = data_source_name , + LOCATION = location_name , + [ FILE_FORMAT = external_file_format_name ] , --Used for Inputs - optional + [ <optional_input_options> ] , + [ <optional_output_options> ] , TAGS = <tag_column_value> <optional_input_options> ::= - INPUT_OPTIONS = '[<Input_options_data>]' + INPUT_OPTIONS = ' [ <input_options_data> ] ' <Input_option_data> ::= <input_option_values> [ , <input_option_values> ] <input_option_values> ::= - PARTITIONS: [number_of_partitions] + PARTITIONS: [ number_of_partitions ] \| CONSUMER_GROUP: [ consumer_group_name ] \| TIME_POLICY: [ time_policy ] \| LATE_EVENT_TOLERANCE: [ late_event_tolerance_value ] \| OUT_OF_ORDER_EVENT_TOLERANCE: [ out_of_order_tolerance_value ] <optional_output_options> ::= - OUTPUT_OPTIONS = '[<output_option_data>]' + OUTPUT_OPTIONS = ' [ <output_option_data> ] ' <output_option_data> ::= <output_option_values> [ , <output_option_values> ] WITH ( <with_options> ) <output_option_values> ::= REJECT_POLICY: [ reject_policy ] \| MINIMUM_ROWS: [ row_value ] - \| MAXIMUM_TIME: [ time_value_minutes] + \| MAXIMUM_TIME: [ time_value_minutes ] \| PARTITION_KEY_COLUMN: [ partition_key_column_name ] \| PROPERTY_COLUMNS: [ ( [ output_col_name ] ) ] \| SYSTEM_PROPERTY_COLUMNS: [ ( [ output_col_name ] ) ] WITH ( <with_options> ) ## Arguments -- [DATA_SOURCE](/sql/t-sql/statements/create-external-data-source-transact-sql/)-- [FILE_FORMAT](/sql/t-sql/statements/create-external-file-format-transact-sql/)-- LOCATION: Specifies the name for the actual data or location in the data source. - - For Edge Hub or Kafka stream objects, location specifies the name of the Edge Hub or Kafka topic to read from or write to. - - For SQL stream objects(SQL Server, Azure SQL Database or Azure SQL Edge) location specifies the name of the table. If the stream is created in the same database and schema as the destination table, then just the Table name suffices. Otherwise you need to fully qualify (`database_name.schema_name.table_name`) the table name. - - For Azure Blob Storage stream object location refers to the path pattern to use inside the blob container. For more information, see [Outputs from Azure Stream Analytics](/articles/stream-analytics/stream-analytics-define-outputs.md#blob-storage-and-azure-data-lake-gen2). --- INPUT_OPTIONS: Specify options as key-value pairs for services such as Kafka, IoT Edge Hub that are inputs to streaming queries - - PARTITIONS: - Number of partitions defined for a topic. The maximum number of partitions which can be used is limited to 32. - - Applies to Kafka Input Streams - - CONSUMER_GROUP: - Event and IoT Hubs limit the number of readers within one consumer group (to 5). Leaving this field empty will use the '$Default' consumer group. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - TIME_POLICY: - Describes whether to drop events or adjust the event time when late events or out of order events pass their tolerance value. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - LATE_EVENT_TOLERANCE: - The maximum acceptable time delay. The delay represents the difference between the event's timestamp and the system clock. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - OUT_OF_ORDER_EVENT_TOLERANCE: - Events can arrive out of order after they've made the trip from the input to the streaming query. These events can be accepted as-is, or you can choose to pause for a set period to reorder them. - - Reserved for future usage. Does not apply to Azure SQL Edge. --- OUTPUT_OPTIONS: Specify options as key-value pairs for supported services that are outputs to streaming queries - - REJECT_POLICY: DROP \| RETRY - Species the data error handling policies when data conversion errors occur. - - Applies to all supported outputs - - MINIMUM_ROWS: - Minimum rows required per batch written to an output. For Parquet, every batch will create a new file. - - Applies to all supported outputs - - MAXIMUM_TIME: - Maximum wait time in minutes per batch. After this time, the batch will be written to the output even if the minimum rows requirement is not met. - - Applies to all supported outputs - - PARTITION_KEY_COLUMN: - The column that is used for the partition key. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - PROPERTY_COLUMNS: - A comma-separated list of the names of output columns that will be attached to messages as custom properties if provided. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - SYSTEM_PROPERTY_COLUMNS: - A JSON-formatted collection of name/value pairs of System Property names and output columns to be populated on Service Bus messages. e.g. { "MessageId": "column1", "PartitionKey": "column2"} - - Reserved for future usage. Does not apply to Azure SQL Edge. - - PARTITION_KEY: - The name of the output column containing the partition key. The partition key is a unique identifier for the partition within a given table that forms the first part of an entity's primary key. It is a string value that may be up to 1 KB in size. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - ROW_KEY: - The name of the output column containing the row key. The row key is a unique identifier for an entity within a given partition. It forms the second part of an entity's primary key. The row key is a string value that may be up to 1 KB in size. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - BATCH_SIZE: - This represents the number of transactions for table storage where the maximum can go up to 100 records. For Azure Functions, this represents the batch size in bytes sent to the function per call - default is 256 kB. - - Reserved for future usage. Does not apply to Azure SQL Edge. - - MAXIMUM_BATCH_COUNT: - Maximum number of events sent to the function per call for Azure function - default is 100. For SQL Database, this represents the maximum number of records sent with every bulk insert transaction - default is 10,000. - - Applies to all SQL based outputs - - STAGING_AREA: EXTERNAL DATA SOURCE object to Blob Storage - The staging area for high-throughput data ingestion into Azure Synapse Analytics - - Reserved for future usage. Does not apply to Azure SQL Edge. +#### DATA_SOURCE + +For more information, see [DATA_SOURCE](/sql/t-sql/statements/create-external-data-source-transact-sql/). + +#### FILE_FORMAT + +For more information, see [FILE_FORMAT](/sql/t-sql/statements/create-external-file-format-transact-sql/). + +#### LOCATION + +Specifies the name for the actual data or location in the data source. + +- For Edge Hub or Kafka stream objects, location specifies the name of the Edge Hub or Kafka topic to read from or write to. +- For SQL stream objects (SQL Server, Azure SQL Database or Azure SQL Edge), the location specifies the name of the table. If the stream is created in the same database and schema as the destination table, then just the Table name suffices. Otherwise you need to fully qualify the table name (`<database_name>.<schema_name>.<table_name>`). +- For Azure Blob Storage stream object location refers to the path pattern to use inside the blob container. For more information, see [Outputs from Azure Stream Analytics](../stream-analytics/blob-storage-azure-data-lake-gen2-output.md). + +#### INPUT_OPTIONS + +Specify options as key-value pairs for services such as Kafka and IoT Edge Hubs, which are inputs to streaming queries. + +- PARTITIONS: + + Number of partitions defined for a topic. The maximum number of partitions that can be used is limited to 32 (Applies to Kafka Input Streams). + + - CONSUMER_GROUP: + + Event and IoT Hubs limit the number of readers within one consumer group (to 5). Leaving this field empty will use the '$Default' consumer group. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + + - TIME_POLICY: + + Describes whether to drop events or adjust the event time when late events or out of order events pass their tolerance value. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + + - LATE_EVENT_TOLERANCE: + + The maximum acceptable time delay. The delay represents the difference between the event's timestamp and the system clock. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + + - OUT_OF_ORDER_EVENT_TOLERANCE: + + Events can arrive out of order after they've made the trip from the input to the streaming query. These events can be accepted as-is, or you can choose to pause for a set period to reorder them. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +#### OUTPUT_OPTIONS + +Specify options as key-value pairs for supported services that are outputs to streaming queries + +- REJECT_POLICY: DROP \| RETRY + + Species the data error handling policies when data conversion errors occur. + + - Applies to all supported outputs. + +- MINIMUM_ROWS: + + Minimum rows required per batch written to an output. For Parquet, every batch creates a new file. + + - Applies to all supported outputs. + +- MAXIMUM_TIME: + + Maximum wait time in minutes per batch. After this time, the batch will be written to the output even if the minimum rows requirement isn't met. + + - Applies to all supported outputs. + +- PARTITION_KEY_COLUMN: + + The column that is used for the partition key. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- PROPERTY_COLUMNS: + + A comma-separated list of the names of output columns that are attached to messages as custom properties, if provided. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- SYSTEM_PROPERTY_COLUMNS: + + A JSON-formatted collection of name/value pairs of System Property names and output columns to be populated on Service Bus messages. For example, `{ "MessageId": "column1", "PartitionKey": "column2" }`. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- PARTITION_KEY: + + The name of the output column containing the partition key. The partition key is a unique identifier for the partition within a given table that forms the first part of an entity's primary key. It's a string value that may be up to 1 KB in size. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- ROW_KEY: + + The name of the output column containing the row key. The row key is a unique identifier for an entity within a given partition. It forms the second part of an entity's primary key. The row key is a string value that may be up to 1 KB in size. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- BATCH_SIZE: + + This represents the number of transactions for table storage where the maximum can go up to 100 records. For Azure Functions, this represents the batch size in bytes sent to the function per call - default is 256 kB. + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. + +- MAXIMUM_BATCH_COUNT: + + Maximum number of events sent to the function per call for Azure function - default is 100. For SQL Database, this represents the maximum number of records sent with every bulk insert transaction - default is 10,000. + + - Applies to all SQL based outputs + +- STAGING_AREA: EXTERNAL DATA SOURCE object to Blob Storage + + The staging area for high-throughput data ingestion into Azure Synapse Analytics + + - Reserved for future usage. Doesn't apply to Azure SQL Edge. For more information about supported input and output options corresponding to the data source type, see [Azure Stream Analytics - Input Overview](../stream-analytics/stream-analytics-add-inputs.md) and [Azure Stream Analytics - Outputs Overview](../stream-analytics/stream-analytics-define-outputs.md) respectively. ## Examples -### Example 1 - EdgeHub - -Type: Input or Output<br> +### Example A: EdgeHub -Syntax: +Type: Input or Output. ```sql CREATE EXTERNAL DATA SOURCE MyEdgeHub -WITH -( - LOCATION = 'edgehub://' -); + WITH (LOCATION = 'edgehub://'); CREATE EXTERNAL FILE FORMAT myFileFormat -WITH ( - FORMAT_TYPE = JSON -); + WITH (FORMAT_TYPE = JSON); CREATE EXTERNAL STREAM Stream_A -WITH -( - DATA_SOURCE = MyEdgeHub, - FILE_FORMAT = myFileFormat, - LOCATION = '<mytopicname>', - OUTPUT_OPTIONS = - 'REJECT_TYPE: Drop' -); + WITH ( + DATA_SOURCE = MyEdgeHub, + FILE_FORMAT = myFileFormat, + LOCATION = '<mytopicname>', + OUTPUT_OPTIONS = 'REJECT_TYPE: Drop' + ); ``` -### Example 2 - Azure SQL Database, Azure SQL Edge, SQL Server - -Type: Output<br> +### Example B: Azure SQL Database, Azure SQL Edge, SQL Server -Syntax: +Type: Output ```sql CREATE DATABASE SCOPED CREDENTIAL SQLCredName -WITH IDENTITY = '<user>', -SECRET = '<password>'; + WITH IDENTITY = '<user>', + SECRET = '<password>'; -- Azure SQL Database CREATE EXTERNAL DATA SOURCE MyTargetSQLTabl -WITH -( - LOCATION = '<my_server_name>.database.windows.net', - CREDENTIAL = SQLCredName -); + WITH ( + LOCATION = '<my_server_name>.database.windows.net', + CREDENTIAL = SQLCredName + ); --SQL Server or Azure SQL Edge CREATE EXTERNAL DATA SOURCE MyTargetSQLTabl -WITH -( - LOCATION = ' <sqlserver://<ipaddress>,<port>', - CREDENTIAL = SQLCredName -); + WITH ( + LOCATION = ' <sqlserver://<ipaddress>,<port>', + CREDENTIAL = SQLCredName + ); CREATE EXTERNAL STREAM Stream_A -WITH -( - DATA_SOURCE = MyTargetSQLTable, - LOCATION = '<DatabaseName>.<SchemaName>.<TableName>' , - --Note: If table is contained in the database, <TableName> should be sufficient - OUTPUT_OPTIONS = - 'REJECT_TYPE: Drop' -); + WITH ( + DATA_SOURCE = MyTargetSQLTable, + LOCATION = '<DatabaseName>.<SchemaName>.<TableName>', + --Note: If table is contained in the database, <TableName> should be sufficient + OUTPUT_OPTIONS = 'REJECT_TYPE: Drop' + ); ``` -### Example 3 - Kafka +### Example C: Kafka -Type: Input<br> +Type: Input -Syntax: ```sql CREATE EXTERNAL DATA SOURCE MyKafka_tweets -WITH -( - --The location maps to KafkaBootstrapServer - LOCATION = 'kafka://<kafkaserver>:<ipaddress>', - CREDENTIAL = kafkaCredName -); + WITH ( + --The location maps to KafkaBootstrapServer + LOCATION = 'kafka://<kafkaserver>:<ipaddress>', + CREDENTIAL = kafkaCredName + ); CREATE EXTERNAL FILE FORMAT myFileFormat -WITH ( - FORMAT_TYPE = JSON, - DATA_COMPRESSION = 'org.apache.hadoop.io.compress.GzipCodec' -); - -CREATE EXTERNAL STREAM Stream_A (user_id VARCHAR, tweet VARCHAR) -WITH -( - DATA_SOURCE = MyKafka_tweets, - LOCATION = '<KafkaTopicName>', - FILE_FORMAT = myFileFormat, - INPUT_OPTIONS = - 'PARTITIONS: 5' -); + WITH ( + FORMAT_TYPE = JSON, + DATA_COMPRESSION = 'org.apache.hadoop.io.compress.GzipCodec' + ); + +CREATE EXTERNAL STREAM Stream_A ( + user_id VARCHAR, + tweet VARCHAR + ) + WITH ( + DATA_SOURCE = MyKafka_tweets, + LOCATION = '<KafkaTopicName>', + FILE_FORMAT = myFileFormat, + INPUT_OPTIONS = 'PARTITIONS: 5' + ); ``` ## See also
azure-sql-edge	Create Stream Analytics Job	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/create-stream-analytics-job.md	Title: Create a T-SQL streaming job in Azure SQL Edge description: Learn about creating Stream Analytics jobs in Azure SQL Edge. - Previously updated : 07/27/2020 Last updated : 09/14/2023 - +# Create a data streaming job in Azure SQL Edge -# Create a data streaming job in Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. This article explains how to create a T-SQL streaming job in Azure SQL Edge. You create the external stream input and output objects, and then you define the streaming job query as part of the streaming job creation. This article explains how to create a T-SQL streaming job in Azure SQL Edge. You T-SQL streaming uses the external data source functionality of SQL Server to define the data sources associated with the external stream inputs and outputs of the streaming job. Use the following T-SQL commands to create an external stream input or output object: - [CREATE EXTERNAL FILE FORMAT (Transact-SQL)](/sql/t-sql/statements/create-external-file-format-transact-sql)- - [CREATE EXTERNAL DATA SOURCE (Transact-SQL)](/sql/t-sql/statements/create-external-data-source-transact-sql)- - [CREATE EXTERNAL STREAM (Transact-SQL)](#example-create-an-external-stream-object-to-azure-sql-database) Additionally, if Azure SQL Edge, SQL Server, or Azure SQL Database is used as an output stream, you need the [CREATE DATABASE SCOPED CREDENTIAL (Transact-SQL)](/sql/t-sql/statements/create-database-scoped-credential-transact-sql). This T-SQL command defines the credentials to access the database. Additionally, if Azure SQL Edge, SQL Server, or Azure SQL Database is used as an Azure SQL Edge currently only supports the following data sources as stream inputs and outputs. \| Data source type \| Input \| Output \| Description \| -\|\|-\|--\|\| -\| Azure IoT Edge hub \| Y \| Y \| Data source to read and write streaming data to an Azure IoT Edge hub. For more information, see [IoT Edge Hub](../iot-edge/iot-edge-runtime.md#iot-edge-hub).\| -\| SQL Database \| N \| Y \| Data source connection to write streaming data to SQL Database. The database can be a local database in Azure SQL Edge, or a remote database in SQL Server or Azure SQL Database.\| -\| Kafka \| Y \| N \| Data source to read streaming data from a Kafka topic. This adapter is currently only available for Intel or AMD versions of Azure SQL Edge. It isn't available for the ARM64 version of Azure SQL Edge.\| +\| \| \| \| \| +\| Azure IoT Edge hub \| Y \| Y \| Data source to read and write streaming data to an Azure IoT Edge hub. For more information, see [IoT Edge Hub](../iot-edge/iot-edge-runtime.md#iot-edge-hub). \| +\| SQL Database \| N \| Y \| Data source connection to write streaming data to SQL Database. The database can be a local database in Azure SQL Edge, or a remote database in SQL Server or Azure SQL Database. \| +\| Kafka \| Y \| N \| Data source to read streaming data from a Kafka topic. \| ### Example: Create an external stream input/output object for Azure IoT Edge hub The following example creates an external stream object for Azure IoT Edge hub. 1. Create an external file format of the type JSON. - ```sql - Create External file format InputFileFormat - WITH - ( - format_type = JSON, - ) - go - ``` - -2. Create an external data source for Azure IoT Edge hub. The following T-SQL script creates a data source connection to an IoT Edge hub that runs on the same Docker host as Azure SQL Edge. - - ```sql - CREATE EXTERNAL DATA SOURCE EdgeHubInput - WITH - ( - LOCATION = 'edgehub://' - ) - go - ``` - -3. Create the external stream object for Azure IoT Edge hub. The following T-SQL script creates a stream object for the IoT Edge hub. In case of an IoT Edge hub stream object, the LOCATION parameter is the name of the IoT Edge hub topic or channel being read or written to. - - ```sql - CREATE EXTERNAL STREAM MyTempSensors - WITH - ( + ```sql + CREATE EXTERNAL FILE format InputFileFormat + WITH (FORMAT_TYPE = JSON); + GO + ``` + +1. Create an external data source for Azure IoT Edge hub. The following T-SQL script creates a data source connection to an IoT Edge hub that runs on the same Docker host as Azure SQL Edge. + + ```sql + CREATE EXTERNAL DATA SOURCE EdgeHubInput + WITH (LOCATION = 'edgehub://'); + GO + ``` + +1. Create the external stream object for Azure IoT Edge hub. The following T-SQL script creates a stream object for the IoT Edge hub. In case of an IoT Edge hub stream object, the LOCATION parameter is the name of the IoT Edge hub topic or channel being read or written to. + + ```sql + CREATE EXTERNAL STREAM MyTempSensors + WITH ( DATA_SOURCE = EdgeHubInput, FILE_FORMAT = InputFileFormat, LOCATION = N'TemperatureSensors', INPUT_OPTIONS = N'', OUTPUT_OPTIONS = N'' - ); - go - ``` + ); + GO + ``` ### Example: Create an external stream object to Azure SQL Database -The following example creates an external stream object to the local database in Azure SQL Edge. +The following example creates an external stream object to the local database in Azure SQL Edge. 1. Create a master key on the database. This is required to encrypt the credential secret. - ```sql - CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<<Strong_Password_For_Master_Key_Encryption>>'; - ``` + ```sql + CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<<Strong_Password_For_Master_Key_Encryption>>'; + ``` -2. Create a database-scoped credential for accessing the SQL Server source. The following example creates a credential to the external data source, with IDENTITY = username, and SECRET = password. +1. Create a database-scoped credential for accessing the SQL Server source. The following example creates a credential to the external data source, with IDENTITY = username, and SECRET = password. - ```sql - CREATE DATABASE SCOPED CREDENTIAL SQLCredential - WITH IDENTITY = '<SQL_Login>', SECRET = '<SQL_Login_PASSWORD>' - go - ``` + ```sql + CREATE DATABASE SCOPED CREDENTIAL SQLCredential + WITH IDENTITY = '<SQL_Login>', SECRET = '<SQL_Login_PASSWORD>'; + GO + ``` -3. Create an external data source with CREATE EXTERNAL DATA SOURCE. The following example: +1. Create an external data source with CREATE EXTERNAL DATA SOURCE. The following example: - * Creates an external data source named LocalSQLOutput. - * Identifies the external data source (`LOCATION = '<vendor>://<server>[:<port>]'`). In the example, it points to a local instance of Azure SQL Edge. - * Uses the credential created previously. + - Creates an external data source named LocalSQLOutput. + - Identifies the external data source (`LOCATION = '<vendor>://<server>[:<port>]'`). In the example, it points to a local instance of Azure SQL Edge. + - Uses the credential created previously. - ```sql - CREATE EXTERNAL DATA SOURCE LocalSQLOutput - WITH - ( + ```sql + CREATE EXTERNAL DATA SOURCE LocalSQLOutput + WITH ( LOCATION = 'sqlserver://tcp:.,1433', CREDENTIAL = SQLCredential - ) - go - ``` - -4. Create the external stream object. The following example creates an external stream object pointing to a table dbo.TemperatureMeasurements, in the database MySQLDatabase. - - ```sql - CREATE EXTERNAL STREAM TemperatureMeasurements - WITH - ( - DATA_SOURCE = LocalSQLOutput, - LOCATION = N'MySQLDatabase.dbo.TemperatureMeasurements', - INPUT_OPTIONS = N'', - OUTPUT_OPTIONS = N'' - ); - ``` + ); + GO + ``` + +1. Create the external stream object. The following example creates an external stream object pointing to a table dbo.TemperatureMeasurements, in the database MySQLDatabase. + + ```sql + CREATE EXTERNAL STREAM TemperatureMeasurements + WITH + ( + DATA_SOURCE = LocalSQLOutput, + LOCATION = N'MySQLDatabase.dbo.TemperatureMeasurements', + INPUT_OPTIONS = N'', + OUTPUT_OPTIONS = N'' + ); + ``` ### Example: Create an external stream object for Kafka -The following example creates an external stream object to the local database in Azure SQL Edge. This example assumes that the kafka server is configured for anonymous access. +The following example creates an external stream object to the local database in Azure SQL Edge. This example assumes that the kafka server is configured for anonymous access. 1. Create an external data source with CREATE EXTERNAL DATA SOURCE. The following example: - ```sql - Create EXTERNAL DATA SOURCE [KafkaInput] - With - ( - LOCATION = N'kafka://<kafka_bootstrap_server_name_ip>:<port_number>' - ) - GO - ``` -2. Create an external file format for the kafka input. The following example created a JSON file format with GZipped Compression. + ```sql + CREATE EXTERNAL DATA SOURCE [KafkaInput] + WITH (LOCATION = N'kafka://<kafka_bootstrap_server_name_ip>:<port_number>'); + GO + ``` + +1. Create an external file format for the Kafka input. The following example created a JSON file format with GZipped Compression. ```sql - CREATE EXTERNAL FILE FORMAT JsonGzipped - WITH - ( - FORMAT_TYPE = JSON , - DATA_COMPRESSION = 'org.apache.hadoop.io.compress.GzipCodec' - ) + CREATE EXTERNAL FILE FORMAT JsonGzipped + WITH ( + FORMAT_TYPE = JSON, + DATA_COMPRESSION = 'org.apache.hadoop.io.compress.GzipCodec' + ); + GO ``` -3. Create the external stream object. The following example creates an external stream object pointing to Kafka topic `TemperatureMeasurement`. +1. Create the external stream object. The following example creates an external stream object pointing to Kafka topic `TemperatureMeasurement`. - ```sql - CREATE EXTERNAL STREAM TemperatureMeasurement - WITH - ( - DATA_SOURCE = KafkaInput, - FILE_FORMAT = JsonGzipped, - LOCATION = 'TemperatureMeasurement', - INPUT_OPTIONS = 'PARTITIONS: 10' - ); - ``` + ```sql + CREATE EXTERNAL STREAM TemperatureMeasurement + WITH + ( + DATA_SOURCE = KafkaInput, + FILE_FORMAT = JsonGzipped, + LOCATION = 'TemperatureMeasurement', + INPUT_OPTIONS = 'PARTITIONS: 10' + ); + GO + ``` ## Create the streaming job and the streaming queries Use the `sys.sp_create_streaming_job` system stored procedure to define the streaming queries and create the streaming job. The `sp_create_streaming_job` stored procedure takes the following parameters: -- `job_name`: The name of the streaming job. Streaming job names are unique across the instance.-- `statement`: [Stream Analytics Query Language](/stream-analytics-query/stream-analytics-query-language-reference)-based streaming query statements. +- `@job_name`: The name of the streaming job. Streaming job names are unique across the instance. +- `@statement`: [Stream Analytics Query Language](/stream-analytics-query/stream-analytics-query-language-reference)-based streaming query statements. The following example creates a simple streaming job with one streaming query. This query reads the inputs from the IoT Edge hub, and writes to `dbo.TemperatureMeasurements` in the database. ```sql -EXEC sys.sp_create_streaming_job @name=N'StreamingJob1', -@statement= N'Select * INTO TemperatureMeasurements from MyEdgeHubInput' +EXEC sys.sp_create_streaming_job @name = N'StreamingJob1', + @statement = N'Select * INTO TemperatureMeasurements from MyEdgeHubInput' ``` The following example creates a more complex streaming job with multiple different queries. These queries include one that uses the built-in `AnomalyDetection_ChangePoint` function to identify anomalies in the temperature data. ```sql -EXEC sys.sp_create_streaming_job @name=N'StreamingJob2', @statement= -N' Select * INTO TemperatureMeasurements1 from MyEdgeHubInput1 - -Select * Into TemperatureMeasurements2 from MyEdgeHubInput2 - -Select * Into TemperatureMeasurements3 from MyEdgeHubInput3 - -SELECT -Timestamp as [Time], -[Temperature] As [Temperature], -GetRecordPropertyValue(AnomalyDetection_ChangePoint(Temperature, 80, 1200) OVER(LIMIT DURATION(minute, 20)), ''Score'') as ChangePointScore, -GetRecordPropertyValue(AnomalyDetection_ChangePoint(Temperature, 80, 1200) OVER(LIMIT DURATION(minute, 20)), ''IsAnomaly'') as IsChangePointAnomaly -INTO TemperatureAnomalies FROM MyEdgeHubInput2; -' -go +EXEC sys.sp_create_streaming_job @name = N'StreamingJob2', + @statement = N' + SELECT * + INTO TemperatureMeasurements1 + FROM MyEdgeHubInput1 + + SELECT * + INTO TemperatureMeasurements2 + FROM MyEdgeHubInput2 + + SELECT * + INTO TemperatureMeasurements3 + FROM MyEdgeHubInput3 + + SELECT timestamp AS [Time], + [Temperature] AS [Temperature], + GetRecordPropertyValue(AnomalyDetection_ChangePoint(Temperature, 80, 1200) OVER (LIMIT DURATION(minute, 20)), '' Score '') AS ChangePointScore, + GetRecordPropertyValue(AnomalyDetection_ChangePoint(Temperature, 80, 1200) OVER (LIMIT DURATION(minute, 20)), '' IsAnomaly '') AS IsChangePointAnomaly + INTO TemperatureAnomalies + FROM MyEdgeHubInput2; +'; +GO ``` ## Start, stop, drop, and monitor streaming jobs go To start a streaming job in Azure SQL Edge, run the `sys.sp_start_streaming_job` stored procedure. The stored procedure requires the name of the streaming job to start, as input. ```sql -exec sys.sp_start_streaming_job @name=N'StreamingJob1' -go +EXEC sys.sp_start_streaming_job @name = N'StreamingJob1'; +GO ``` To stop a streaming job, run the `sys.sp_stop_streaming_job` stored procedure. The stored procedure requires the name of the streaming job to stop, as input. ```sql -exec sys.sp_stop_streaming_job @name=N'StreamingJob1' -go +EXEC sys.sp_stop_streaming_job @name = N'StreamingJob1'; +GO ``` To drop (or delete) a streaming job, run the `sys.sp_drop_streaming_job` stored procedure. The stored procedure requires the name of the streaming job to drop, as input. ```sql -exec sys.sp_drop_streaming_job @name=N'StreamingJob1' -go +EXEC sys.sp_drop_streaming_job @name = N'StreamingJob1'; +GO ``` To get the current status of a streaming job, run the `sys.sp_get_streaming_job` stored procedure. The stored procedure requires the name of the streaming job to drop, as input. It outputs the name and the current status of the streaming job. ```sql -exec sys.sp_get_streaming_job @name=N'StreamingJob1' - WITH RESULT SETS -( - ( - name nvarchar(256), - status nvarchar(256), - error nvarchar(256) - ) -) +EXEC sys.sp_get_streaming_job @name = N'StreamingJob1' +WITH RESULT SETS ( + ( + name NVARCHAR(256), + status NVARCHAR(256), + error NVARCHAR(256) + ) + ); +GO ``` The streaming job can have any one of the following statuses: \| Status \| Description \| -\|--\| \| +\| \| \| \| Created \| The streaming job was created, but hasn't yet been started. \| \| Starting \| The streaming job is in the starting phase. \| \| Idle \| The streaming job is running, but there's no input to process. \| \| Processing \| The streaming job is running, and is processing inputs. This state indicates a healthy state for the streaming job. \| -\| Degraded \| The streaming job is running, but there were some non-fatal errors during input processing. The input job will continue to run, but will drop inputs that encounter errors. \| +\| Degraded \| The streaming job is running, but there were some non-fatal errors during input processing. The input job continues to run, but will drop inputs that encounter errors. \| \| Stopped \| The streaming job has been stopped. \| \| Failed \| The streaming job failed. This is generally an indication of a fatal error during processing. \| -> [!NOTE] -> Since the streaming job is executed asynchronously, the job might encounter errors at runtime. In order to troubleshoot a streaming job failure, use the `sys.sp_get_streaming_job` stored procedure, or review the docker log from the Azure SQL Edge container, which can provide the error details from the streaming job. +> [!NOTE] +> Since the streaming job is executed asynchronously, the job might encounter errors at runtime. In order to troubleshoot a streaming job failure, use the `sys.sp_get_streaming_job` stored procedure, or review the Docker log from the Azure SQL Edge container, which can provide the error details from the streaming job. ## Next steps -- [View metadata associated with streaming jobs in Azure SQL Edge](streaming-catalog-views.md) +- [View metadata associated with streaming jobs in Azure SQL Edge](streaming-catalog-views.md) - [Create an external stream](create-external-stream-transact-sql.md)
azure-sql-edge	Data Retention Cleanup	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/data-retention-cleanup.md	Title: Manage historical data with retention policy - Azure SQL Edge description: Learn how to manage historical data with retention policy in Azure SQL Edge - Previously updated : 09/04/2020 Last updated : 09/14/2023 keywords: - SQL Edge - data retention- - # Manage historical data with retention policy -Data Retention can enabled on the database and any of the underlying tables individually, allowing users to create flexible aging policies for their tables and databases. Applying data retention is simple: it requires only one parameter to be set during table creation or as part of an alter table operation. +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. -After data retention policy is defined for a database and the underlying table, a background timer task runs to remove any obsolete records from the table enabled for data retention. Identification of matching rows and their removal from the table occur transparently, in the background task that is scheduled and run by the system. Age condition for the table rows is checked based on the column used as the `filter_column` in the table definition. If retention period, for example, is set to one week, table rows eligible for cleanup satisfy either of the following condition: +After the data retention policy is defined for a database and the underlying table, a background time timer task runs to remove any obsolete records from the table enabled for data retention. Identification of matching rows and their removal from the table occur transparently, in the background task scheduled and run by the system. Age condition for the table rows is checked based on the `filter_column` column specified in the table definition. If retention period is set to one week, for instance, table rows eligible for cleanup satisfy either of the following condition: -- If the filter column uses DATETIMEOFFSET data type then the condition is `filter_column < DATEADD(WEEK, -1, SYSUTCDATETIME())`-- Else then the condition is `filter_column < DATEADD(WEEK, -1, SYSDATETIME())` +- If the filter column uses DATETIMEOFFSET data type, then the condition is `filter_column < DATEADD(WEEK, -1, SYSUTCDATETIME())` +- Otherwise, the condition is `filter_column < DATEADD(WEEK, -1, SYSDATETIME())` ## Data retention cleanup phases -Data retention cleanup operation comprises of two phases. -- Discovery Phase - In this phase the cleanup operation identifies all the tables within the user databases to build a list for cleanup. Discovery runs once a day.-- Cleanup Phase - In this phase, cleanup is run against all tables with finite data retention, identified in the discovery phase. If the cleanup operation cannot be performed on a table, then that table is skipped in the current run and will be retried in the next iteration. The following principles are used during cleanup - - If an obsolete row is locked by another transaction, that row is skipped. - - Cleanup runs with a default 5 seconds lock timeout setting. If the locks cannot be acquired on the tables within the timeout window, the table is skipped in the current run and will be retried in the next iteration. - - If there is an error during cleanup of a table, that table is skipped and will be picked up in the next iteration. +The data retention cleanup operation consists of two phases: + +1. Discovery: In this phase, the cleanup operation identifies all the tables within the user databases to build a list for cleanup. Discovery runs once a day. +1. Cleanup: In this phase, cleanup is run against all tables with finite data retention, identified in the discovery phase. If the cleanup operation can't be performed on a table, then that table is skipped in the current run and will be retried in the next iteration. The following principles are used during cleanup: + - If an obsolete row is locked by another transaction, that row is skipped. + - Cleanup runs with a default lock timeout of 5 seconds. If the locks can't be acquired on the tables within the timeout window, the table is skipped in the current run and will be retried in the next iteration. + - If there's an error during cleanup of a table, that table is skipped and will be picked up in the next iteration. ## Manual cleanup -Depending on the data retention settings on a table and the nature of the workload on the database, it's possible that the automatic cleanup thread may not completely remove all obsolete rows during its run. To assist with this and allow users to manually remove obsolete rows, the `sys.sp_cleanup_data_retention` stored procedure has been introduced in Azure SQL Edge. +Depending on the data retention settings on a table and the nature of the workload on the database, it's possible that the automatic cleanup thread may not completely remove all obsolete rows during its run. To allow users to manually remove obsolete rows, the `sys.sp_cleanup_data_retention` stored procedure has been introduced in Azure SQL Edge. + +This stored procedure takes three parameters: + +- `@schema_name`: Name of the owning schema for the table. Required. +- `@table_name`: Name of the table for which manual cleanup is being run. Required. +- `@rowcount`: Output variable. Returns the number of rows cleaned up by the manual cleanup sp. Optional. -This stored procedure takes three parameters. - - Schema Name - Name of the owning schema for the table. This is a required parameter. - - Table Name - Name of the table for which manual cleanup is being run. This is a required parameter. - - rowcount (Output) - output variable. Returns the number of rows cleaned up by the manual cleanup sp. This is an optional parameter. +For more information, see [sys.sp_cleanup_data_retention (Transact-SQL)](sys-sp-cleanup-data-retention.md). The following example shows the execution of the manual cleanup sp for table `dbo.data_retention_table`. ```sql -declare @rowcnt bigint -EXEC sys.sp_cleanup_data_retention 'dbo', 'data_retention_table', @rowcnt output -select @rowcnt +DECLARE @rowcnt BIGINT; +EXEC sys.sp_cleanup_data_retention 'dbo', 'data_retention_table', @rowcnt OUTPUT; +SELECT @rowcnt; ``` ## How obsolete rows are deleted -The cleanup process depends on the index layout of the table. A background task is created to perform obsolete data cleanup for all tables with finite retention period. Clean up logic for the rowstore (B-tree or Heap) index deletes aged row in smaller chunks (up to 10K) minimizing pressure on database log and IO subsystem. Although cleanup logic utilizes required B-tree index, order of deletions for the rows older than retention period cannot be firmly guaranteed. Hence, do not take any dependency on the cleanup order in your applications. +The cleanup process depends on the index layout of the table. A background task is created to perform obsolete data cleanup for all tables with finite retention period. Clean up logic for the rowstore (heap or B-tree) index deletes aged row in smaller chunks (up to 10,000), minimizing pressure on database log and the I/O subsystem. Although cleanup logic utilizes the required B-tree index, the order of deletions for the rows older than retention period can't be firmly guaranteed. In other words, don't take a dependency on the cleanup order in your applications. -The cleanup task for the clustered columnstore removes entire row groups at once (typically contain 1 million of rows each), which is very efficient, especially when data is generated and ages out at a high pace. +> [!WARNING] +> In the case of heaps and B-tree indexes, data retention runs a delete query on the underlying tables, which can conflict with delete triggers on the tables. You should either remove delete triggers from the tables, or avoid using data retention on tables that have delete DML triggers. -![Data Retention Cleanup](./media/data-retention-cleanup/data-retention-cleanup.png) +The cleanup task for the clustered columnstore indexes removes entire row groups at once (typically contain 1 million of rows each), which is efficient, especially when data is generated and ages out at a high pace. -Excellent data compression and efficient retention cleanup makes clustered columnstore index a perfect choice for scenarios when your workload rapidly generates high amount of data. -> [!Note] -> In the case of B-Tree Indexes and heaps, data retention runs a delete query on the underlying tables, which can conflict with delete triggers on the tables. It is recommended to either remove delete triggers from the tables or to not enable data retention on tables that have delete DML trigger. +Excellent data compression and efficient retention cleanup makes clustered columnstore indexes a perfect choice for scenarios when your workload rapidly generates a large amount of data. -## Monitoring data retention cleanup +## Monitor data retention cleanup -Data retention policy cleanup operations can be monitored using extended events (XEvents) in Azure SQL Edge. For more information on extended events, refer [XEvents Overview](/sql/relational-databases/extended-events/extended-events). +Data retention policy cleanup operations can be monitored using Extended Events in Azure SQL Edge. For more information on extended events, see [Extended Events Overview](/sql/relational-databases/extended-events/extended-events). -The following six extended events help track the state of the cleanup operations. +The following Extended Events help track the state of the cleanup operations. \| Name \| Description \| -\|\| \| -\| data_retention_task_started \| Occurs when background task for cleanup of tables with retention policy starts. \| -\| data_retention_task_completed \| Occurs when background task for cleanup of tables with retention policy ends. \| -\| data_retention_task_exception \| Occurs when background task for cleanup of tables with retention policy fails outside of retention cleanup process specific to table. \| -\| data_retention_cleanup_started \| Occurs when clean up process of table with data retention policy starts. \| -\| data_retention_cleanup_exception \| Occurs cleanup process of table with retention policy fails. \| -\| data_retention_cleanup_completed \| Occurs when clean up process of table with data retention policy ends. \| +\| \| \| +\| data_retention_task_started \| Occurs when the background task for cleanup of tables with a retention policy starts. \| +\| data_retention_task_completed \| Occurs when the background task for cleanup of tables with a retention policy ends. \| +\| data_retention_task_exception \| Occurs when the background task for cleanup of tables with a retention policy fails, outside of retention cleanup process specific to those tables. \| +\| data_retention_cleanup_started \| Occurs when the cleanup process of a table with data retention policy starts. \| +\| data_retention_cleanup_exception \| Occurs when the cleanup process of a table with retention policy fails. \| +\| data_retention_cleanup_completed \| Occurs when the cleanup process of a table with data retention policy ends. \| -Additionally, a new ring buffer type named `RING_BUFFER_DATA_RETENTION_CLEANUP` has been added to sys.dm_os_ring_buffers dynamic management view. This view can be used to monitor the data retention cleanup operations. +Additionally, a new ring buffer type named `RING_BUFFER_DATA_RETENTION_CLEANUP` has been added to the `sys.dm_os_ring_buffers` dynamic management view. This view can be used to monitor the data retention cleanup operations. +## Next steps -## Next Steps - [Data Retention Policy](data-retention-overview.md) - [Enable and Disable Data Retention Policies](data-retention-enable-disable.md)
azure-sql-edge	Data Retention Enable Disable	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/data-retention-enable-disable.md	Title: Enable and disable data retention policies - Azure SQL Edge description: Learn how to enable and disable data retention policies in Azure SQL Edge - Previously updated : 09/04/2020 Last updated : 09/14/2023 keywords: - SQL Edge - data retention- - # Enable and disable data retention policies -This topic describes how to enable and disable data retention policies for a database and a table. +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + +This article describes how to enable and disable data retention policies for a database and a table. ## Enable data retention for a database -The following example shows how to enable data retention by using [Alter Database](/sql/t-sql/statements/alter-database-transact-sql-set-options). +The following example shows how to enable data retention by using [ALTER DATABASE](/sql/t-sql/statements/alter-database-transact-sql-set-options). ```sql -ALTER DATABASE [<DatabaseName>] SET DATA_RETENTION ON; +ALTER DATABASE [<DatabaseName>] SET DATA_RETENTION ON; ``` ## Check if data retention is enabled for a database -The following command can be used to check if data retention is enabled for a database +The following command can be used to check if data retention is enabled for a database. + ```sql -SELECT is_data_retention_enabled, name +SELECT is_data_retention_enabled, + name FROM sys.databases; ``` ## Enable data retention for a table -Data Retention must be enabled for each table for which you want data to be automatically purged. When Data Retention is enabled on the database and the table, a background system task will periodically scan the table to identify and delete any obsolete (aged) rows. Data Retention can be enabled on a table either during table creation using [Create Table](/sql/t-sql/statements/create-table-transact-sql) or by using [Alter Table](/sql/t-sql/statements/alter-table-transact-sql). +Data Retention must be enabled for each table for which you want data to be automatically purged. When data retention is enabled on the database and the table, a background system task periodically scans the table to identify and delete any obsolete (aged) rows. Data retention can be enabled on a table either during table creation using [CREATE TABLE](/sql/t-sql/statements/create-table-transact-sql) or by using [ALTER TABLE](/sql/t-sql/statements/alter-table-transact-sql). -The following example shows how to enable data retention for a table by using [Create Table](/sql/t-sql/statements/create-table-transact-sql). +The following example shows how to enable data retention for a table by using [CREATE TABLE](/sql/t-sql/statements/create-table-transact-sql). ```sql -CREATE TABLE [dbo].[data_retention_table] -( -[dbdatetime2] datetime2(7), -[product_code] int, -[value] char(10), -CONSTRAINT [pk_current_data_retention_table] PRIMARY KEY CLUSTERED ([product_code]) -) WITH (DATA_DELETION = ON ( FILTER_COLUMN = [dbdatetime2], RETENTION_PERIOD = 1 day ) ) +CREATE TABLE [dbo].[data_retention_table] ( + [dbdatetime2] DATETIME2(7), + [product_code] INT, + [value] CHAR(10), + CONSTRAINT [pk_current_data_retention_table] PRIMARY KEY CLUSTERED ([product_code]) +) +WITH ( + DATA_DELETION = ON ( + FILTER_COLUMN = [dbdatetime2], + RETENTION_PERIOD = 1 day + ) + ); ``` -The `WITH (DATA_DELETION = ON ( FILTER_COLUMN = [dbdatetime2], RETENTION_PERIOD = 1 day ) )` part of the create table command sets the data retention on the table. The command uses the following required parameters +The `WITH (DATA_DELETION = ON (FILTER_COLUMN = [dbdatetime2], RETENTION_PERIOD = 1 day))` part of the CREATE TABLE command sets the data retention on the table. The command uses the following required parameters: + +- DATA_DELETION: Indicates whether data retention is ON or OFF. -- DATA_DELETION - Indicates whether data retention is ON or OFF.-- FILTER_COLUMN - Name on the column in the table, which will be used to ascertain if the rows are obsolete or not. The filter column can only be a column with the following data types - - Date - - SmallDateTime - - DateTime - - DateTime2 - - DateTimeOffset -- RETENTION_PERIOD - An integer value followed by a unit descriptor. The allowed units are DAY, DAYS, WEEK, WEEKS, MONTH, MONTHS, YEAR and YEARS. +- FILTER_COLUMN: Name on the column in the table, which will be used to ascertain if the rows are obsolete or not. The filter column can only be a column with the following data types: -The following example shows how to enable data retention for table by using [Alter Table](/sql/t-sql/statements/alter-table-transact-sql). + - date + - smalldatetime + - datetime + - datetime2 + - datetimeoffset + +- RETENTION_PERIOD: An integer value followed by a unit descriptor. The allowed units are DAY, DAYS, WEEK, WEEKS, MONTH, MONTHS, YEAR and YEARS. + +The following example shows how to enable data retention for table by using [ALTER TABLE](/sql/t-sql/statements/alter-table-transact-sql). ```sql -Alter Table [dbo].[data_retention_table] -SET (DATA_DELETION = On (FILTER_COLUMN = [timestamp], RETENTION_PERIOD = 1 day)) +ALTER TABLE [dbo].[data_retention_table] +SET ( + DATA_DELETION = ON ( + FILTER_COLUMN = [timestamp], + RETENTION_PERIOD = 1 day + ) +) ``` ## Check if data retention is enabled for a table SET (DATA_DELETION = On (FILTER_COLUMN = [timestamp], RETENTION_PERIOD = 1 day)) The following command can be used to check the tables for which data retention is enabled ```sql -select name, data_retention_period, data_retention_period_unit from sys.tables +SELECT name, + data_retention_period, + data_retention_period_unit +FROM sys.tables; ``` -A value of data_retention_period = -1 and data_retention_period_unit as INFINITE, indicates that data retention is not set on the table. +A value of `data_retention_period = -1` and `data_retention_period_unit` as INFINITE, indicates that data retention isn't set on the table. -The following query can be used to identify the column used as the filter_column for data retention. +The following query can be used to identify the column used as the `filter_column` for data retention. ```sql -Select name from sys.columns -where is_data_deletion_filter_column =1 -and object_id = object_id(N'dbo.data_retention_table', N'U') +SELECT name +FROM sys.columns +WHERE is_data_deletion_filter_column = 1 + AND object_id = object_id(N'dbo.data_retention_table', N'U'); ``` -## Correlating DB and table data retention settings +## Correlate database and table data retention settings -The data retention setting on the database and the table, are used in conjunction to determine if autocleanup for aged rows will run on the tables or not. +The data retention setting on the database and the table are used in conjunction to determine if autocleanup for aged rows runs on the tables. -\|Database Option \| Table Option \| Behavior \| -\|-\|--\|-\| -\| OFF \| OFF \| Data Retention policy is disabled and both auto and manual cleanup of aged records is disabled.\| -\| OFF \| ON \| Data Retention policy is enabled for the table. Auto cleanup of obsolete records is disabled, however manual cleanup method can be used to cleanup obsolete records. \| -\| ON \| OFF \| Data Retention policy is enabled at the database level. However since the option is disabled at the table level, there is no retention-based cleanup of aged rows.\| -\| ON \| ON \| Data Retention policy is enabled for both the database and tables. Automatic cleanup of obsolete records is enabled. \| +\| Database option \| Table option \| Behavior \| +\| \| \| \| +\| OFF \| OFF \| Data retention policy is disabled and both auto and manual cleanup of aged records is disabled. \| +\| OFF \| ON \| Data retention policy is enabled for the table. Auto cleanup of obsolete records is disabled, however manual cleanup method can be used to clean up obsolete records. \| +\| ON \| OFF \| Data retention policy is enabled at the database level. However since the option is disabled at the table level, there's no retention-based cleanup of aged rows. \| +\| ON \| ON \| Data retention policy is enabled for both the database and tables. Automatic cleanup of obsolete records is enabled. \| ## Disable data retention on a table -Data Retention can be disabled on a table by using [Alter Table](/sql/t-sql/statements/alter-table-transact-sql). The following command can be used to disable data retention on a table. +Data retention can be disabled on a table by using [ALTER TABLE](/sql/t-sql/statements/alter-table-transact-sql). The following command can be used to disable data retention on a table. ```sql -Alter Table [dbo].[data_retention_table] -Set (DATA_DELETION = OFF) +ALTER TABLE [dbo].[data_retention_table] +SET (DATA_DELETION = OFF); ``` ## Disable data retention on a database -Data Retention can be disabled on a table by using [Alter Database](/sql/t-sql/statements/alter-database-transact-sql-set-options). The following command can be used to disable data retention on a database. +Data retention can be disabled on a table by using [ALTER DATABASE](/sql/t-sql/statements/alter-database-transact-sql-set-options). The following command can be used to disable data retention on a database. ```sql -ALTER DATABASE [<DatabaseName>] SET DATA_RETENTION OFF; +ALTER DATABASE [<DatabaseName>] SET DATA_RETENTION OFF; ``` ## Next steps+ - [Data Retention and Automatic Data Purging](data-retention-overview.md) - [Manage historical data with retention policy](data-retention-cleanup.md)
azure-sql-edge	Data Retention Overview	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/data-retention-overview.md	Title: Data retention policy overview - Azure SQL Edge description: Learn about the data retention policy in Azure SQL Edge - Previously updated : 09/04/2020 Last updated : 09/14/2023 keywords: - SQL Edge - data retention- - # Data retention overview -Collection and storage of data from connected IoT devices is important to drive and gain operational and business insights. However given the volume of data originating from these devices, it becomes important for organizations to carefully plan the amount of data they want to retain and at what granularity. While retaining all data at all granularity is desirable, it's not always practical. Additionally, the volume of data that can be retained is constrained by the amount of storage available on the IoT or Edge devices. +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + +Collection and storage of data from connected IoT devices is important to drive and gain operational and business insights. However, with the volume of data originating from these devices, it becomes important for organizations to carefully plan the amount of data they want to retain and at what granularity. While retaining all data at all granularity is desirable, it's not always practical. Additionally, the volume of data that can be retained is constrained by the amount of storage available on the IoT or Edge devices. -In Azure SQL Edge database administrators can define data retention policy on a SQL Edge database and its underlying tables. Once the data retention policy is defined, a background system task will run to purge any obsolete (old) data from the user tables. +In Azure SQL Edge, database administrators can define data retention policy on a SQL Edge database and its underlying tables. Once the data retention policy is defined, a background system task runs to purge any obsolete (old) data from the user tables. -> [!Note] -> Data once purged from the table, is not recoverable. The only possible way to recover the purged data is to restore the database from an older backup. +> [!NOTE] +> Data once purged from the table, isn't recoverable. The only possible way to recover the purged data is to restore the database from an older backup. Quickstarts: Quickstarts: ## How data retention works -To configure data retention, you can use DDL statements. For more information, [Enable and Disable Data Retention Policies](data-retention-enable-disable.md). For automatic deletion of the obsolete records, data retention must first be enabled for both the database and the tables that you want to be purged within that database. +To configure data retention, you can use DDL statements. For more information, [Enable and Disable Data Retention Policies](data-retention-enable-disable.md). For automatic deletion of the obsolete records, data retention must first be enabled for both the database and the tables that you want to be purged within that database. -After data retention is configured for a table, a background task runs to identify the obsolete records in a table and delete those records. If for some reason, the automatic cleanup of the tasks is not running or is unable to keep up with the deletes, then a manual cleanup operation can be performed on these tables. For more information on automatic and manual cleanups, refer [Automatic and Manual Cleanup](data-retention-cleanup.md). +After data retention is configured for a table, a background task runs to identify the obsolete records in a table and delete those records. If for some reason, the automatic cleanup of the tasks isn't running or is unable to keep up with the delete operations, then a manual cleanup operation can be performed on these tables. For more information on automatic and manual cleanups, see [Automatic and Manual Cleanup](data-retention-cleanup.md). -## Limitations and restrictions +## Limitations -- Data Retention, if enabled, is automatically disabled when the database is restored from a full backup or is reattached. -- Data Retention cannot be enabled for a Temporal History Table-- Data Retention filter colomn cannot be altered. To alter the column, disable data retention on the table. +- Data Retention, if enabled, is automatically disabled when the database is restored from a full backup or is reattached. +- Data Retention can't be enabled for a Temporal History Table +- Data Retention filter column can't be altered. To alter the column, disable data retention on the table. -## Next Steps +## Next steps - [Machine Learning and Artificial Intelligence with ONNX in SQL Edge](onnx-overview.md). - [Building an end to end IoT Solution with SQL Edge using IoT Edge](tutorial-deploy-azure-resources.md).
azure-sql-edge	Date Bucket Tsql	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/date-bucket-tsql.md	Title: Date_Bucket (Transact-SQL) - Azure SQL Edge -description: Learn about using Date_Bucket in Azure SQL Edge + Title: DATE_BUCKET (Transact-SQL) - Azure SQL Edge +description: Learn about using DATE_BUCKET in Azure SQL Edge - Previously updated : 09/03/2020 Last updated : 09/14/2023 keywords: - - Date_Bucket + - DATE_BUCKET - SQL Edge- +# DATE_BUCKET (Transact-SQL) -# Date_Bucket (Transact-SQL) +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. -This function returns the datetime value corresponding to the start of each datetime bucket, from the timestamp defined by the `origin` parameter or the default origin value of `1900-01-01 00:00:00.000` if the origin parameter is not specified. +This function returns the datetime value corresponding to the start of each datetime bucket, from the timestamp defined by the `origin` parameter or the default origin value of `1900-01-01 00:00:00.000` if the origin parameter isn't specified. -See [Date and Time Data Types and Functions (Transact-SQL)](/sql/t-sql/functions/date-and-time-data-types-and-functions-transact-sql/) for an overview of all Transact-SQL date and time data types and functions. +See [Date and Time Data Types and Functions (Transact-SQL)](/sql/t-sql/functions/date-and-time-data-types-and-functions-transact-sql/) for an overview of all Transact-SQL date and time data types and functions. [Transact-SQL Syntax Conventions](/sql/t-sql/language-elements/transact-sql-syntax-conventions-transact-sql/) ## Syntax ```syntaxsql -DATE_BUCKET (datepart, number, date, origin) +DATE_BUCKET (datePart , number , date , origin) ``` ## Arguments -datepart +#### datePart -The part of date that is used with the ΓÇÿnumberΓÇÖ parameter. Ex. Year, month, minute, second etc. +The part of date that is used with the 'number' parameter, as shown in the following table. `DATE_BUCKET` doesn't accept user-defined variable equivalents for the datePart arguments. -> [!NOTE] -> `DATE_BUCKET` does not accept user-defined variable equivalents for the datePart arguments. +\| datePart \| Abbreviations \| +\| \| \| +\| day \| dd, d \| +\| week \| wk, ww \| +\| month \| mm, m \| +\| quarter \| qq, q \| +\| year \| yy, yyyy \| +\| hour \| hh \| +\| minute \| mi, n \| +\| second \| ss, s \| +\| millisecond \| ms \| -\|datePart\|Abbreviations\| -\|\|\| -\|day\|dd, d\| -\|week\|wk, ww\| -\|month\|mm, m\| -\|quarter\|qq, q\| -\|year\|yy, yyyy\| -\|hour\|hh\| -\|minute\|mi, n\| -\|second\|ss, s\| -\|millisecond\|ms\| +#### number -number +The integer number that decides the width of the bucket combined with datePart argument. This represents the width of the datePart buckets from the origin time. This argument has to be a positive integer value. -The integer number that decides the width of the bucket combined with datepart argument. This represents the width of the datepart buckets from the origin time. `This argument has to be a positive integer value`. - -date +#### date An expression that can resolve to one of the following values: -+ date -+ datetime -+ datetime2 -+ datetimeoffset -+ smalldatetime -+ time +- date +- datetime +- datetime2 +- datetimeoffset +- smalldatetime +- time -For date, `DATE_BUCKET` will accept a column expression, expression, or user-defined variable if they resolve to any of the data types mentioned above. +For date, `DATE_BUCKET` accepts a column expression, expression, or user-defined variable if they resolve to any of the data types mentioned previously. -Origin +#### origin An optional expression that can resolve to one of the following values: -+ date -+ datetime -+ datetime2 -+ datetimeoffset -+ smalldatetime -+ time +- date +- datetime +- datetime2 +- datetimeoffset +- smalldatetime +- time -The data type for `Origin` should match the data type of the `Date` parameter. +The data type for origin should match the data type of the date parameter. -`DATE_BUCKET` uses a default origin date value of `1900-01-01 00:00:00.000` i.e. 12:00 AM on Monday, January 1 1900, if no Origin value is specified for the function. +`DATE_BUCKET` uses a default origin date value of `1900-01-01 00:00:00.000`, that is, 12:00 AM on Monday, January 1, 1900, if no origin value is specified for the function. -## Return Type +## Return type -The return value data type for this method is dynamic. The return type depends on the argument supplied for `date`. If a valid input data type is supplied for `date`, `DATE_BUCKET` returns the same data type. `DATE_BUCKET` raises an error if a string literal is specified for the `date` parameter. +The return value data type for this method is dynamic. The return type depends on the argument supplied for date. If a valid input data type is supplied for date, `DATE_BUCKET` returns the same data type. `DATE_BUCKET` raises an error if a string literal is specified for the date parameter. -## Return Values +## Return values -### Understanding the output from `DATE_BUCKET` +### Understand the output from `DATE_BUCKET` -`Date_Bucket` returns the latest date or time value, corresponding to the datePart and number parameter. For example, in the expressions below, `Date_Bucket` will return the output value of `2020-04-13 00:00:00.0000000`, as the output is calculated based on one week buckets from the default origin time of `1900-01-01 00:00:00.000`. The value `2020-04-13 00:00:00.0000000` is 6276 weeks from the origin value of `1900-01-01 00:00:00.000`. +`DATE_BUCKET` returns the latest date or time value, corresponding to the datePart and number parameters. For example, in the following expressions, `DATE_BUCKET` returns the output value of `2020-04-13 00:00:00.0000000`, as the output is calculated based on one week buckets from the default origin time of `1900-01-01 00:00:00.000`. The value `2020-04-13 00:00:00.0000000` is 6276 weeks from the origin value of `1900-01-01 00:00:00.000`. ```sql -declare @date datetime2 = '2020-04-15 21:22:11'; -Select DATE_BUCKET(WEEK, 1, @date); +DECLARE @date DATETIME2 = '2020-04-15 21:22:11'; + +SELECT DATE_BUCKET(WEEK, 1, @date); ``` -For all the expressions below, the same output value of `2020-04-13 00:00:00.0000000` will be returned. This is because `2020-04-13 00:00:00.0000000` is 6276 weeks from the origin date and 6276 is divisible by 2, 3, 4 and 6. +For all the following expressions, the same output value of `2020-04-13 00:00:00.0000000` is returned. This is because `2020-04-13 00:00:00.0000000` is 6276 weeks from the origin date and 6276 is divisible by 2, 3, 4 and 6. ```sql -declare @date datetime2 = '2020-04-15 21:22:11'; -Select DATE_BUCKET(WEEK, 2, @date); -Select DATE_BUCKET(WEEK, 3, @date); -Select DATE_BUCKET(WEEK, 4, @date); -Select DATE_BUCKET(WEEK, 6, @date); +DECLARE @date DATETIME2 = '2020-04-15 21:22:11'; + +SELECT DATE_BUCKET(WEEK, 2, @date); +SELECT DATE_BUCKET(WEEK, 3, @date); +SELECT DATE_BUCKET(WEEK, 4, @date); +SELECT DATE_BUCKET(WEEK, 6, @date); ``` The output for the expression below is `2020-04-06 00:00:00.0000000`, which is 6275 weeks from the default origin time `1900-01-01 00:00:00.000`. ```sql -declare @date datetime2 = '2020-04-15 21:22:11'; -Select DATE_BUCKET(WEEK, 5, @date); +DECLARE @date DATETIME2 = '2020-04-15 21:22:11'; + +SELECT DATE_BUCKET(WEEK, 5, @date); ``` The output for the expression below is `2020-06-09 00:00:00.0000000` , which is 75 weeks from the specified origin time `2019-01-01 00:00:00`. ```sql -declare @date datetime2 = '2020-06-15 21:22:11'; -declare @origin datetime2 = '2019-01-01 00:00:00'; -Select DATE_BUCKET(WEEK, 5, @date, @origin); +DECLARE @date DATETIME2 = '2020-06-15 21:22:11'; +DECLARE @origin DATETIME2 = '2019-01-01 00:00:00'; + +SELECT DATE_BUCKET(WEEK, 5, @date, @origin); ``` -## datepart Argument +## Remarks -dayofyear, day, and weekday return the same value. Each datepart and its abbreviations return the same value. +Use `DATE_BUCKET` in the following clauses: + +- `GROUP BY` +- `HAVING` +- `ORDER BY` +- `SELECT <list>` +- `WHERE` + +#### `datePart` argument -## number Argument +dayofyear, day, and weekday return the same value. Each datePart and its abbreviations return the same value. -The number argument cannot exceed the range of positive int values. In the following statements, the argument for number exceeds the range of int by 1. The following statement returns the following error message: "`Msg 8115, Level 16, State 2, Line 2. Arithmetic overflow error converting expression to data type int."` +#### number argument + +The number argument can't exceed the range of positive int values. In the following statements, the argument for number exceeds the range of int by 1. The following statement returns the following error message: `Msg 8115, Level 16, State 2, Line 2. Arithmetic overflow error converting expression to data type int.` ```sql -declare @date datetime2 = '2020-04-30 00:00:00'; -Select DATE_BUCKET(DAY, 2147483648, @date); +DECLARE @date DATETIME2 = '2020-04-30 00:00:00'; + +SELECT DATE_BUCKET(DAY, 2147483648, @date); ``` -If a negative value for number is passed to the `Date_Bucket` function, the following error will be returned. +If a negative value for number is passed to the `DATE_BUCKET` function, the following error is returned. -```txt +```output Msg 9834, Level 16, State 1, Line 1 -Invalid bucket width value passed to date_bucket function. Only positive values are allowed. -```` +Invalid bucket width value passed to DATE_BUCKET function. Only positive values are allowed. +``` -## date Argument +#### date argument -`DATE_BUCKET` return the base value corresponding to the data type of the `date` argument. In the following example, an output value with datetime2 datatype is returned. +`DATE_BUCKET` return the base value corresponding to the data type of the date argument. In the following example, an output value with datetime2 data type is returned. ```sql -Select DATE_BUCKET(DAY, 10, SYSUTCDATETIME()); +SELECT DATE_BUCKET(DAY, 10, SYSUTCDATETIME()); ``` -## origin Argument - -The data type of the `origin` and `date` arguments in must be the same. If different data types are used, an error will be generated. - -## Remarks - -Use `DATE_BUCKET` in the following clauses: +#### origin argument -+ GROUP BY -+ HAVING -+ ORDER BY -+ SELECT \<list> -+ WHERE +The data type of the origin and date arguments in must be the same. If different data types are used, an error is generated. ## Examples -### A. Calculating Date_Bucket with a bucket width of 1 from the origin time +### A. Calculate DATE_BUCKET with a bucket width of 1 from the origin time -Each of these statements increments date_bucket with a bucket width of 1 from the origin time: +Each of these statements increments DATE_BUCKET with a bucket width of 1 from the origin time: ```sql -declare @date datetime2 = '2020-04-30 21:21:21' -Select 'Week', DATE_BUCKET(WEEK, 1, @date) -Union All -Select 'Day', DATE_BUCKET(DAY, 1, @date) -Union All -Select 'Hour', DATE_BUCKET(HOUR, 1, @date) -Union All -Select 'Minutes', DATE_BUCKET(MINUTE, 1, @date) -Union All -Select 'Seconds', DATE_BUCKET(SECOND, 1, @date); +DECLARE @date DATETIME2 = '2020-04-30 21:21:21'; + +SELECT 'Week', DATE_BUCKET(WEEK, 1, @date) +UNION ALL SELECT 'Day', DATE_BUCKET(DAY, 1, @date) +UNION ALL SELECT 'Hour', DATE_BUCKET(HOUR, 1, @date) +UNION ALL SELECT 'Minutes', DATE_BUCKET(MINUTE, 1, @date) +UNION ALL SELECT 'Seconds', DATE_BUCKET(SECOND, 1, @date); ``` -Here is the result set. +Here's the result set. -```txt +```output Week 2020-04-27 00:00:00.0000000 Day 2020-04-30 00:00:00.0000000 Hour 2020-04-30 21:00:00.0000000 Minutes 2020-04-30 21:21:00.0000000 Seconds 2020-04-30 21:21:21.0000000 ``` -### B. Using expressions as arguments for the number and date parameters +### B. Use expressions as arguments for the number and date parameters -These examples use different types of expressions as arguments for the number and date parameters. These examples are built using the 'AdventureWorksDW2017' Database. +These examples use different types of expressions as arguments for the number and date parameters. These examples are built using the `AdventureWorksDW2019` Database. -#### Specifying user-defined variables as number and date +#### Specify user-defined variables as number and date This example specifies user-defined variables as arguments for number and date: ```sql -DECLARE @days int = 365, - @datetime datetime2 = '2000-01-01 01:01:01.1110000'; /* 2000 was a leap year /; -SELECT Date_Bucket(DAY, @days, @datetime); +DECLARE @days INT = 365, + @datetime DATETIME2 = '2000-01-01 01:01:01.1110000';/ 2000 was a leap year /; + +SELECT DATE_BUCKET(DAY, @days, @datetime); ``` -Here is the result set. +Here's the result set. -```txt +```output 1999-12-08 00:00:00.0000000 (1 row affected) ``` -#### Specifying a column as date +#### Specify a column as date In the example below, we are calculating the sum of OrderQuantity and sum of UnitPrice grouped over weekly date buckets. ```sql -SELECT - Date_Bucket(WEEK, 1 ,cast(Shipdate as datetime2)) AS ShippedDateBucket - ,Sum(OrderQuantity) As SumOrderQuantity - ,Sum(UnitPrice) As SumUnitPrice +SELECT DATE_BUCKET(WEEK, 1, CAST(Shipdate AS DATETIME2)) AS ShippedDateBucket, + Sum(OrderQuantity) AS SumOrderQuantity, + Sum(UnitPrice) AS SumUnitPrice FROM dbo.FactInternetSales FIS -where Shipdate between '2011-01-03 00:00:00.000' and '2011-02-28 00:00:00.000' -Group by Date_Bucket(week, 1 ,cast(Shipdate as datetime2)) -order by ShippedDateBucket; +WHERE Shipdate BETWEEN '2011-01-03 00:00:00.000' + AND '2011-02-28 00:00:00.000' +GROUP BY DATE_BUCKET(week, 1, CAST(Shipdate AS DATETIME2)) +ORDER BY ShippedDateBucket; ``` -Here is the result set. +Here's the result set. -```txt +```output ShippedDateBucket SumOrderQuantity SumUnitPrice - 2011-01-03 00:00:00.0000000 21 65589.7546 ShippedDateBucket SumOrderQuantity SumUnitPrice 2011-02-28 00:00:00.0000000 9 28968.6982 ``` -#### Specifying scalar system function as date +#### Specify scalar system function as date This example specifies `SYSDATETIME` for date. The exact value returned depends on the day and time of statement execution: ```sql -SELECT Date_Bucket(WEEK, 10, SYSDATETIME()); +SELECT DATE_BUCKET(WEEK, 10, SYSDATETIME()); ``` -Here is the result set. +Here's the result set. -```txt +```output 2020-03-02 00:00:00.0000000 (1 row affected) ``` -#### Specifying scalar subqueries and scalar functions as number and date +#### Specify scalar subqueries and scalar functions as number and date This example uses scalar subqueries, `MAX(OrderDate)`, as arguments for number* and date. `(SELECT top 1 CustomerKey FROM dbo.DimCustomer where GeographyKey > 100)` serves as an artificial argument for the number parameter, to show how to select a number argument from a value list. ```sql -SELECT DATE_BUCKET(WEEK,(SELECT top 1 CustomerKey FROM dbo.DimCustomer where GeographyKey > 100), - (SELECT MAX(OrderDate) FROM dbo.FactInternetSales)); +SELECT DATE_BUCKET(WEEK, + ( + SELECT TOP 1 CustomerKey + FROM dbo.DimCustomer + WHERE GeographyKey > 100 + ), + ( + SELECT MAX(OrderDate) + FROM dbo.FactInternetSales + ) + ); ``` -#### Specifying numeric expressions and scalar system functions as number and date +#### Specify numeric expressions and scalar system functions as number and date This example uses a numeric expression ((10/2)), and scalar system functions (SYSDATETIME) as arguments for number and date. ```sql -SELECT Date_Bucket(WEEK,(10/2), SYSDATETIME()); +SELECT DATE_BUCKET(WEEK, (10 / 2), SYSDATETIME()); ``` -#### Specifying an aggregate window function as number +#### Specify an aggregate window function as number This example uses an aggregate window function as an argument for number. ```sql -Select - DISTINCT DATE_BUCKET(DAY, 30, Cast([shipdate] as datetime2)) as DateBucket, - First_Value([SalesOrderNumber]) OVER (Order by DATE_BUCKET(DAY, 30, Cast([shipdate] as datetime2))) as First_Value_In_Bucket, - Last_Value([SalesOrderNumber]) OVER (Order by DATE_BUCKET(DAY, 30, Cast([shipdate] as datetime2))) as Last_Value_In_Bucket - from [dbo].[FactInternetSales] -Where ShipDate between '2011-01-03 00:00:00.000' and '2011-02-28 00:00:00.000' -order by DateBucket; +SELECT DISTINCT DATE_BUCKET(DAY, 30, CAST([shipdate] AS DATETIME2)) AS DateBucket, + FIRST_VALUE([SalesOrderNumber]) OVER ( + ORDER BY DATE_BUCKET(DAY, 30, CAST([shipdate] AS DATETIME2)) + ) AS FIRST_VALUE_In_Bucket, + LAST_VALUE([SalesOrderNumber]) OVER ( + ORDER BY DATE_BUCKET(DAY, 30, CAST([shipdate] AS DATETIME2)) + ) AS LAST_VALUE_In_Bucket +FROM [dbo].[FactInternetSales] +WHERE ShipDate BETWEEN '2011-01-03 00:00:00.000' + AND '2011-02-28 00:00:00.000' +ORDER BY DateBucket; GO ``` -### C. Using a non-default origin value + +### C. Use a non-default origin value This example uses a non-default origin value to generate the date buckets. ```sql -declare @date datetime2 = '2020-06-15 21:22:11'; -declare @origin datetime2 = '2019-01-01 00:00:00'; -Select DATE_BUCKET(HOUR, 2, @date, @origin); +DECLARE @date DATETIME2 = '2020-06-15 21:22:11'; +DECLARE @origin DATETIME2 = '2019-01-01 00:00:00'; + +SELECT DATE_BUCKET(HOUR, 2, @date, @origin); ``` ## See also -[CAST and CONVERT (Transact-SQL)](/sql/t-sql/functions/cast-and-convert-transact-sql/) +- [CAST and CONVERT (Transact-SQL)](/sql/t-sql/functions/cast-and-convert-transact-sql/)
azure-sql-edge	Deploy Dacpac	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/deploy-dacpac.md	Title: Using SQL Database DACPAC and BACPAC packages - Azure SQL Edge -description: Learn about using dacpacs and bacpacs in Azure SQL Edge +description: Learn about using DACPACs and BACPACs in Azure SQL Edge - Previously updated : 09/03/2020 Last updated : 09/14/2023 keywords: - SQL Edge - sqlpackage- - # SQL Database DACPAC and BACPAC packages in SQL Edge -Azure SQL Edge is an optimized relational database engine geared for IoT and edge deployments. It's built on the latest versions of the Microsoft SQL Database Engine, which provides industry-leading performance, security, and query processing capabilities. Along with the industry-leading relational database management capabilities of SQL Server, Azure SQL Edge provides in-built streaming capability for real-time analytics and complex event-processing. - -Azure SQL Edge provides native mechanism that enable you to deploy a [SQL Database DACPAC and BACPAC](/sql/relational-databases/data-tier-applications/data-tier-applications) package during, or after deploying SQL Edge. - -SQL Database dacpac and bacpac packages can be deployed to SQL Edge using the `MSSQL_PACKAGE` environment variable. The environment variable can be configured with any of the following. -- A local folder location within the SQL container containing the dacpac and bacpac files. This folder can be mapped to a host volume using either mount points or data volume containers. -- A local file path within the SQL container mapping to the dacpac or the bacpac file. This file path can be mapped to a host volume using either mount points or data volume containers. -- A local file path within the SQL container mapping to a zip file containing the dacpac or bacpac files. This file path can be mapped to a host volume using either mount points or data volume containers. -- An Azure Blob SAS URL to a zip file containing the dacpac and bacpac files.-- An Azure Blob SAS URL to a dacpac or a bacpac file. - -## Use a SQL Database DAC package with SQL Edge - -To deploy (or import) a SQL Database DAC package `(.dacpac)` or a BACPAC file `(.bacpac)` using Azure Blob storage and a zip file, follow the steps below. - -1. Create/Extract a DAC package or Export a Bacpac File using one of the mechanism mentioned below. - - Use [SQL Database Project Extension - Azure Data Studio](/sql/azure-data-studio/extensions/sql-database-project-extension-getting-started) to [create a new database project or export an existing database](/sql/azure-data-studio/extensions/sql-database-project-extension-getting-started) - - Create or extract a SQL Database DAC package. See [Extracting a DAC from a database](/sql/relational-databases/data-tier-applications/extract-a-dac-from-a-database/) for information on how to generate a DAC package for an existing SQL Server database. - - Exporting a deployed DAC package or a database. See [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application/) for information on how to generate a bacpac file for an existing SQL Server database. +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. -> [!NOTE] -> If you are using external streaming jobs as part of the database, please ensure the following: -> -> - The generated dacpac will capture all the SQL Server Objects corresponding to the inputs/output streams and the streaming jobs. But the jobs will not be automatically started. In order to have the external streaming job automatically started after deployment, add a post-deployment script that restarts the jobs as follows: -> -> ``` -> exec sys.sp_stop_streaming_job @name=N'<JOB NAME>'; -> GO -> exec sys.sp_start_streaming_job @name=N'<JOB NAME>'; -> GO -> ``` -> -> - Ensure any credentials required by the external streaming jobs to access input or output streams are provided as part of the dacpac. +Azure SQL Edge is an optimized relational database engine geared for IoT and edge deployments. It's built on the latest versions of the Microsoft SQL Database Engine, which provides industry-leading performance, security, and query processing capabilities. Along with the industry-leading relational database management capabilities of SQL Server, Azure SQL Edge provides in-built streaming capability for real-time analytics and complex event-processing. +Azure SQL Edge provides native mechanisms to deploy a [SQL Database DACPAC and BACPAC](/sql/relational-databases/data-tier-applications/data-tier-applications) package during, or after deploying, SQL Edge. +SQL Database DACPAC and BACPAC packages can be deployed to SQL Edge using the `MSSQL_PACKAGE` environment variable. The environment variable can be configured with any of the following. -2. Zip the `.dacpac` or the `.bacpac` file and upload it to an Azure Blob storage account. For more information on uploading files to Azure Blob storage, see [Upload, download, and list blobs with the Azure portal](../storage/blobs/storage-quickstart-blobs-portal.md). +- A local folder location within the SQL container containing the DACPAC and BACPAC files. This folder can be mapped to a host volume using either mount points or data volume containers. +- A local file path within the SQL container mapping to the DACPAC or the BACPAC file. This file path can be mapped to a host volume using either mount points or data volume containers. +- A local file path within the SQL container mapping to a zip file containing the DACPAC or BACPAC files. This file path can be mapped to a host volume using either mount points or data volume containers. +- An Azure Blob SAS URL to a zip file containing the DACPAC and BACPAC files. +- An Azure Blob SAS URL to a DACPAC or a BACPAC file. -3. Generate a shared access signature for the zip file by using the Azure portal. For more information, see [Delegate access with shared access signatures (SAS)](../storage/common/storage-sas-overview.md). +## Use a SQL Database DAC package with SQL Edge -4. Update the SQL Edge module configuration to include the shared access URI for the DAC package. To update the SQL Edge module, take these steps: +To deploy (or import) a SQL Database DAC package `(.dacpac)` or a BACPAC file `(.bacpac)` using Azure Blob storage and a zip file, follow these steps. - 1. In the Azure portal, go to your IoT Hub deployment. +1. Create/extract a DAC package or export a BACPAC file using one of the following mechanisms. + - Use [SQL Database Project Extension - Azure Data Studio](/sql/azure-data-studio/extensions/sql-database-project-extension-getting-started) to [create a new database project or export an existing database](/sql/azure-data-studio/extensions/sql-database-project-extension-getting-started) + - Create or extract a SQL Database DAC package. See [Extracting a DAC from a database](/sql/relational-databases/data-tier-applications/extract-a-dac-from-a-database/) for information on how to generate a DAC package for an existing SQL Server database. + - Exporting a deployed DAC package or a database. See [Export a Data-tier Application](/sql/relational-databases/data-tier-applications/export-a-data-tier-application/) for information on how to generate a BACPAC file for an existing SQL Server database. - 2. In the left pane, select IoT Edge. + If you're using external streaming jobs as part of the database, ensure that: - 3. On the IoT Edge page, find and select the IoT Edge where the SQL Edge module is deployed. + - The generated DACPAC captures all the SQL Server objects corresponding to the inputs/output streams and the streaming jobs, but the jobs won't be automatically started. In order to have the external streaming job automatically started after deployment, add a post-deployment script that restarts the jobs as follows: - 4. On the IoT Edge Device device page, select Set Module. + ```sql + EXEC `sys.sp_stop_streaming_job` @name = N'<JOB NAME>'; + GO + EXEC `sys.sp_start_streaming_job` @name = N'<JOB NAME>'; + GO + ``` - 5. On the Set modules page, and click on the Azure SQL Edge module. + - Any credentials required by the external streaming jobs to access input or output streams are provided as part of the DACPAC. - 6. On the Update IoT Edge Module pane, select Environment Variables. Add the `MSSQL_PACKAGE` environment variable and specify the SAS URL generated in Step 3 above as the value for the environment variable. +1. Zip the `.dacpac` or the `.bacpac` file and upload it to an Azure Blob storage account. For more information on uploading files to Azure Blob storage, see [Upload, download, and list blobs with the Azure portal](../storage/blobs/storage-quickstart-blobs-portal.md). - 7. Select Update. +1. Generate a shared access signature for the zip file by using the Azure portal. For more information, see [Delegate access with shared access signatures (SAS)](../storage/common/storage-sas-overview.md). - 8. On the Set modules page, select Review + create. +1. Update the SQL Edge module configuration to include the shared access URI for the DAC package. To update the SQL Edge module, take these steps: - 9. On the Set modules page, select Create. + 1. In the Azure portal, go to your IoT Hub deployment. + 1. In the left pane, select IoT Edge. + 1. On the IoT Edge page, find and select the IoT Edge where the SQL Edge module is deployed. + 1. On the IoT Edge Device device page, select Set Module. + 1. On the Set modules page, and select the Azure SQL Edge module. + 1. On the Update IoT Edge Module pane, select Environment Variables. Add the `MSSQL_PACKAGE` environment variable and specify the SAS URL generated in Step 3 above as the value for the environment variable. + 1. Select Update. + 1. On the Set modules page, select Review + create. + 1. On the Set modules page, select Create. -5. After the module update, the package files are downloaded, unzipped, and deployed against the SQL Edge instance. +1. After the module update, the package files are downloaded, unzipped, and deployed against the SQL Edge instance. -On each restart of the Azure SQL Edge container, SQL Edge attempts to download the zipped file package and evaluate for changes. If a new version of the dacpac file is encountered, the changes are deployed to the database in SQL Edge. +On each restart of the Azure SQL Edge container, SQL Edge attempts to download the zipped file package and evaluate for changes. If a new version of the DACPAC file is encountered, the changes are deployed to the database in SQL Edge. -## Known Issue +## Known issue -During some DACPAC or BACPAC deployments users may encounter a command timeouts, resulting in the failure of the dacpac deployment operation. If you encounter this problem, please use the SQLPackage.exe (or SQL Client Tools) to apply the DACPAC or BACPAC maually. +During some DACPAC or BACPAC deployments users may encounter a command timeout, resulting in the failure of the DACPAC deployment operation. If you encounter this problem, use the SQLPackage.exe (or SQL Client Tools) to apply the DACPAC or BACPAC manually. ## Next steps
azure-sql-edge	Deploy Kubernetes	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/deploy-kubernetes.md	Title: Deploy an Azure SQL Edge container in Kubernetes - Azure SQL Edge description: Learn about deploying an Azure SQL Edge container in Kubernetes - Previously updated : 09/22/2020 Last updated : 09/14/2023 keywords: - SQL Edge - container - - kubernetes - + - Kubernetes - # Deploy an Azure SQL Edge container in Kubernetes -Azure SQL Edge can be deployed on a Kubernetes cluster both as an IoT Edge module through Azure IoT Edge running on Kubernetes or as a standalone container pod. For the remainder of this article, we will focus on the standalone container deployment on a kubernetes cluster. For information on deploying Azure IoT Edge on Kubernetes, refer [Azure IoT Edge on Kubernetes (preview)](https://microsoft.github.io/iotedge-k8s-doc/introduction.html). +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + +Azure SQL Edge can be deployed on a Kubernetes cluster both as an IoT Edge module through Azure IoT Edge running on Kubernetes, or as a standalone container pod. For the remainder of this article, we will focus on the standalone container deployment on a Kubernetes cluster. For information on deploying Azure IoT Edge on Kubernetes, see [Azure IoT Edge on Kubernetes (preview)](https://microsoft.github.io/iotedge-k8s-doc/introduction.html). -This tutorial demonstrates how to configure a highly available Azure SQL Edge instance in a container on a kubernetes cluster. +This tutorial demonstrates how to configure a highly available Azure SQL Edge instance in a container on a Kubernetes cluster. > [!div class="checklist"] > * Create an SA password This tutorial demonstrates how to configure a highly available Azure SQL Edge in Kubernetes 1.6 and later has support for [storage classes](https://kubernetes.io/docs/concepts/storage/storage-classes/), [persistent volume claims](https://kubernetes.io/docs/concepts/storage/storage-classes/#persistentvolumeclaims), and the [Azure disk volume type](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_disk). You can create and manage your Azure SQL Edge instances natively in Kubernetes. The example in this article shows how to create a [deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) to achieve a high availability configuration similar to a shared disk failover cluster instance. In this configuration, Kubernetes plays the role of the cluster orchestrator. When an Azure SQL Edge instance in a container fails, the orchestrator bootstraps another instance of the container that attaches to the same persistent storage. -![Azure SQL Edge in a Kubernetes cluster](media/deploy-kubernetes/kubernetes-sql-edge.png) In the preceding diagram, `azure-sql-edge` is a container in a [pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/). Kubernetes orchestrates the resources in the cluster. A [replica set](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/) ensures that the pod is automatically recovered after a node failure. Applications connect to the service. In this case, the service represents a load balancer that hosts an IP address that stays the same after failure of the `azure-sql-edge`. In the following diagram, the `azure-sql-edge` container has failed. As the orchestrator, Kubernetes guarantees the correct count of healthy instances in the replica set, and starts a new container according to the configuration. The orchestrator starts a new pod on the same node, and `azure-sql-edge` reconnects to the same persistent storage. The service connects to the re-created `azure-sql-edge`. -![Azure SQL Edge in a Kubernetes cluster after pod fail](media/deploy-kubernetes/kubernetes-sql-edge-after-pod-fail.png) In the following diagram, the node hosting the `azure-sql-edge` container has failed. The orchestrator starts the new pod on a different node, and `azure-sql-edge` reconnects to the same persistent storage. The service connects to the re-created `azure-sql-edge`. -![Azure SQL Edge in a Kubernetes cluster after node fail](media/deploy-kubernetes/kubernetes-sql-edge-after-node-fail.png) ## Prerequisites -* Kubernetes cluster - - The tutorial requires a Kubernetes cluster. The steps use [kubectl](https://kubernetes.io/docs/reference/kubectl/) to manage the cluster. +- Kubernetes cluster + - The tutorial requires a Kubernetes cluster. The steps use [kubectl](https://kubernetes.io/docs/reference/kubectl/) to manage the cluster. - - For the purpose of this tutorial, we will be using Azure Kubernetes Service to deploy Azure SQL Edge. See [Deploy an Azure Kubernetes Service (AKS) cluster](../aks/tutorial-kubernetes-deploy-cluster.md) to create and connect to a single-node Kubernetes cluster in AKS with `kubectl`. + - For the purpose of this tutorial, we are using Azure Kubernetes Service to deploy Azure SQL Edge. See [Deploy an Azure Kubernetes Service (AKS) cluster](../aks/tutorial-kubernetes-deploy-cluster.md) to create and connect to a single-node Kubernetes cluster in AKS with `kubectl`. - >[!NOTE] - >To protect against node failure, a Kubernetes cluster requires more than one node. + > [!NOTE] + > To protect against node failure, a Kubernetes cluster requires more than one node. -* Azure CLI +- Azure CLI - The instructions in this tutorial have been validated against Azure CLI 2.10.1. -## Create a kubernetes namespace for SQL Edge deployment +## Create a Kubernetes namespace for SQL Edge deployment -Create a new namespace in the kubernetes cluster. This namespace will be used to deploy SQL Edge and all the required artifacts. For more information on Kubernetes namespaces, refer [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/). +Create a new namespace in the kubernetes cluster. This namespace is used to deploy SQL Edge and all the required artifacts. For more information on Kubernetes namespaces, see [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/). ```azurecli kubectl create namespace <namespace name> - ``` + ``` ## Create an SA password The following command creates a password for the SA account: ```azurecli kubectl create secret generic mssql --from-literal=SA_PASSWORD="MyC0m9l&xP@ssw0rd" -n <namespace name> - ``` + ``` Replace `MyC0m9l&xP@ssw0rd` with a complex password. ## Create storage -Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) and [persistent volume claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistent-volume-claim-protection) in the Kubernetes cluster. Complete the following steps: +Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) and [persistent volume claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistent-volume-claim-protection) in the Kubernetes cluster. Complete the following steps: -1. Create a manifest to define the storage class and the persistent volume claim. The manifest specifies the storage provisioner, parameters, and [reclaim policy](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming). The Kubernetes cluster uses this manifest to create the persistent storage. +1. Create a manifest to define the storage class and the persistent volume claim. The manifest specifies the storage provisioner, parameters, and [reclaim policy](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming). The Kubernetes cluster uses this manifest to create the persistent storage. - The following yaml example defines a storage class and persistent volume claim. The storage class provisioner is `azure-disk`, because this Kubernetes cluster is in Azure. The storage account type is `Standard_LRS`. The persistent volume claim is named `mssql-data`. The persistent volume claim metadata includes an annotation connecting it back to the storage class. + The following yaml example defines a storage class and persistent volume claim. The storage class provisioner is `azure-disk`, because this Kubernetes cluster is in Azure. The storage account type is `Standard_LRS`. The persistent volume claim is named `mssql-data`. The persistent volume claim metadata includes an annotation connecting it back to the storage class. ```yaml kind: StorageClass Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers Save the file (for example, pvc.yaml). -2. Create the persistent volume claim in Kubernetes. +1. Create the persistent volume claim in Kubernetes. ```azurecli kubectl apply -f <Path to pvc.yaml file> -n <namespace name> Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers `<Path to pvc.yaml file>` is the location where you saved the file. - The persistent volume is automatically created as an Azure storage account, and bound to the persistent volume claim. + The persistent volume is automatically created as an Azure storage account, and bound to the persistent volume claim. - ![Screenshot of persistent volume claim command](medi.png) + :::image type="content" source="medi.png" alt-text="Screenshot of persistent volume claim command."::: -3. Verify the persistent volume claim. +1. Verify the persistent volume claim. ```azurecli kubectl describe pvc <PersistentVolumeClaim> -n <name of the namespace> Configure a [persistent volume](https://kubernetes.io/docs/concepts/storage/pers The returned metadata includes a value called `Volume`. This value maps to the name of the blob. - ![Screenshot of returned metadata, including Volume](media/deploy-kubernetes/describe-volume.png) + :::image type="content" source="media/deploy-kubernetes/describe-volume.png" alt-text="Screenshot of returned metadata, including Volume."::: -4. Verify the persistent volume. +1. Verify the persistent volume. ```azurecli kubectl describe pv -n <namespace name> ``` - `kubectl` returns metadata about the persistent volume that was automatically created and bound to the persistent volume claim. + `kubectl` returns metadata about the persistent volume that was automatically created and bound to the persistent volume claim. ## Create the deployment -In this example, the container hosting the Azure SQL Edge instance is described as a Kubernetes deployment object. The deployment creates a replica set. The replica set creates the pod. +In this example, the container hosting the Azure SQL Edge instance is described as a Kubernetes deployment object. The deployment creates a replica set. The replica set creates the pod. -In this step, create a manifest to describe the container based on the Azure SQL Edge Docker image. The manifest references the `mssql-data` persistent volume claim, and the `mssql` secret that you already applied to the Kubernetes cluster. The manifest also describes a [service](https://kubernetes.io/docs/concepts/services-networking/service/). This service is a load balancer. The load balancer guarantees that the IP address persists after Azure SQL Edge instance is recovered. +In this step, create a manifest to describe the container based on the Azure SQL Edge Docker image. The manifest references the `mssql-data` persistent volume claim, and the `mssql` secret that you already applied to the Kubernetes cluster. The manifest also describes a [service](https://kubernetes.io/docs/concepts/services-networking/service/). This service is a load balancer. The load balancer guarantees that the IP address persists after Azure SQL Edge instance is recovered. 1. Create a manifest (a YAML file) to describe the deployment. The following example describes a deployment, including a container based on the Azure SQL Edge container image. -```yaml -apiVersion: apps/v1 -kind: Deployment -metadata: - name: sqledge-deployment -spec: - replicas: 1 - selector: - matchLabels: - app: sqledge - template: - metadata: - labels: - app: sqledge - spec: - volumes: - - name: sqldata - persistentVolumeClaim: - claimName: mssql-data - containers: - - name: azuresqledge - image: mcr.microsoft.com/azure-sql-edge:latest - ports: - - containerPort: 1433 - volumeMounts: - - name: sqldata - mountPath: /var/opt/mssql - env: - - name: MSSQL_PID - value: "Developer" - - name: ACCEPT_EULA - value: "Y" - - name: SA_PASSWORD - valueFrom: - secretKeyRef: - name: mssql - key: SA_PASSWORD - - name: MSSQL_AGENT_ENABLED - value: "TRUE" - - name: MSSQL_COLLATION - value: "SQL_Latin1_General_CP1_CI_AS" - - name: MSSQL_LCID - value: "1033" - terminationGracePeriodSeconds: 30 - securityContext: - fsGroup: 10001 - -apiVersion: v1 -kind: Service -metadata: - name: sqledge-deployment -spec: - selector: - app: sqledge - ports: - - protocol: TCP - port: 1433 - targetPort: 1433 - name: sql - type: LoadBalancer -``` - - Copy the preceding code into a new file, named `sqldeployment.yaml`. Update the following values: - - * MSSQL_PID `value: "Developer"`: Sets the container to run Azure SQL Edge Developer edition. Developer edition is not licensed for production data. If the deployment is for production use, set the edition to `Premium`. - - >[!NOTE] - >For more information, see [How to license Azure SQL Edge](https://azure.microsoft.com/pricing/details/sql-edge/). - - * `persistentVolumeClaim`: This value requires an entry for `claimName:` that maps to the name used for the persistent volume claim. This tutorial uses `mssql-data`. + ```yaml + apiVersion: apps/v1 + kind: Deployment + metadata: + name: sqledge-deployment + spec: + replicas: 1 + selector: + matchLabels: + app: sqledge + template: + metadata: + labels: + app: sqledge + spec: + volumes: + - name: sqldata + persistentVolumeClaim: + claimName: mssql-data + containers: + - name: azuresqledge + image: mcr.microsoft.com/azure-sql-edge:latest + ports: + - containerPort: 1433 + volumeMounts: + - name: sqldata + mountPath: /var/opt/mssql + env: + - name: MSSQL_PID + value: "Developer" + - name: ACCEPT_EULA + value: "Y" + - name: SA_PASSWORD + valueFrom: + secretKeyRef: + name: mssql + key: SA_PASSWORD + - name: MSSQL_AGENT_ENABLED + value: "TRUE" + - name: MSSQL_COLLATION + value: "SQL_Latin1_General_CP1_CI_AS" + - name: MSSQL_LCID + value: "1033" + terminationGracePeriodSeconds: 30 + securityContext: + fsGroup: 10001 + + apiVersion: v1 + kind: Service + metadata: + name: sqledge-deployment + spec: + selector: + app: sqledge + ports: + - protocol: TCP + port: 1433 + targetPort: 1433 + name: sql + type: LoadBalancer + ``` + + Copy the preceding code into a new file, named `sqldeployment.yaml`. Update the following values: + + * MSSQL_PID `value: "Developer"`: Sets the container to run Azure SQL Edge Developer edition. Developer edition isn't licensed for production data. If the deployment is for production use, set the edition to `Premium`. + + > [!NOTE] + > For more information, see [How to license Azure SQL Edge](https://azure.microsoft.com/pricing/details/sql-edge/). + + * `persistentVolumeClaim`: This value requires an entry for `claimName:` that maps to the name used for the persistent volume claim. This tutorial uses `mssql-data`. * `name: SA_PASSWORD`: Configures the container image to set the SA password, as defined in this section. spec: valueFrom: secretKeyRef: name: mssql - key: SA_PASSWORD + key: SA_PASSWORD ``` - When Kubernetes deploys the container, it refers to the secret named `mssql` to get the value for the password. + When Kubernetes deploys the container, it refers to the secret named `mssql` to get the value for the password. - >[!NOTE] - >By using the `LoadBalancer` service type, the Azure SQL Edge instance is accessible remotely (via the internet) at port 1433. + > [!NOTE] + > By using the `LoadBalancer` service type, the Azure SQL Edge instance is accessible remotely (via the internet) at port 1433. - Save the file (for example, sqledgedeploy.yaml). + Save the file (for example, `sqledgedeploy.yaml`). -2. Create the deployment. +1. Create the deployment. ```azurecli kubectl apply -f <Path to sqledgedeploy.yaml file> -n <namespace name> spec: `<Path to sqldeployment.yaml file>` is the location where you saved the file. - ![Screenshot of deployment command](medi.png) + :::image type="content" source="medi.png" alt-text="Screenshot of deployment command."::: The deployment and service are created. The Azure SQL Edge instance is in a container, connected to persistent storage. To view the status of the pod, type `kubectl get pod -n <namespace name>`. - ![Screenshot of get pod command](medi.png) + :::image type="content" source="medi.png" alt-text="Screenshot of get pod command."::: In the preceding image, the pod has a status of `Running`. This status indicates that the container is ready. This may take several minutes. - >[!NOTE] - >After the deployment is created, it can take a few minutes before the pod is visible. The delay is because the cluster pulls the Azure SQL Edge container image from the Docker hub. After the image is pulled the first time, subsequent deployments might be faster if the deployment is to a node that already has the image cached on it. + > [!NOTE] + > After the deployment is created, it can take a few minutes before the pod is visible. The delay is because the cluster pulls the Azure SQL Edge container image from the Docker hub. After the image is pulled the first time, subsequent deployments might be faster if the deployment is to a node that already has the image cached on it. -3. Verify the services are running. Run the following command: +1. Verify the services are running. Run the following command: ```azurecli kubectl get services -n <namespace name> ``` - This command returns services that are running, as well as the internal and external IP addresses for the services. Note the external IP address for the `mssql-deployment` service. Use this IP address to connect to Azure SQL Edge. + This command returns services that are running, as well as the internal and external IP addresses for the services. Note the external IP address for the `mssql-deployment` service. Use this IP address to connect to Azure SQL Edge. - ![Screenshot of get service command](medi.png) + :::image type="content" source="medi.png" alt-text="Screenshot of get service command."::: For more information about the status of the objects in the Kubernetes cluster, run: ```azurecli az aks browse --resource-group <MyResourceGroup> --name <MyKubernetesClustername> - ``` + ``` ## Connect to the Azure SQL Edge instance -If you configured the container as described, you can connect with an application from outside the Azure virtual network. Use the `sa` account and the external IP address for the service. Use the password that you configured as the Kubernetes secret. For more information on connecting to an Azure SQL Edge instance, refer [Connect to Azure SQL Edge](connect.md). +If you configured the container as described, you can connect with an application from outside the Azure virtual network. Use the `sa` account and the external IP address for the service. Use the password that you configured as the Kubernetes secret. For more information on connecting to an Azure SQL Edge instance, see [Connect to Azure SQL Edge](connect.md). ## Verify failure and recovery To verify failure and recovery, you can delete the pod. Do the following steps: Note the name of the pod running Azure SQL Edge. -2. Delete the pod. +1. Delete the pod. ```azurecli kubectl delete pod sqledge-deployment-7df66c9999-rc9xl ``` - `sqledge-deployment-7df66c9999-rc9xl` is the value returned from the previous step for pod name. -Kubernetes automatically re-creates the pod to recover an Azure SQL Edge instance, and connect to the persistent storage. Use `kubectl get pods` to verify that a new pod is deployed. Use `kubectl get services` to verify that the IP address for the new container is the same. + `sqledge-deployment-7df66c9999-rc9xl` is the value returned from the previous step for pod name. + +Kubernetes automatically re-creates the pod to recover an Azure SQL Edge instance, and connect to the persistent storage. Use `kubectl get pods` to verify that a new pod is deployed. Use `kubectl get services` to verify that the IP address for the new container is the same. ## Summary -In this tutorial, you learned how to deploy Azure SQL Edge containers to a Kubernetes cluster for high availability. +In this tutorial, you learned how to deploy Azure SQL Edge containers to a Kubernetes cluster for high availability. > [!div class="checklist"] > * Create an SA password
azure-sql-edge	Deploy Onnx	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/deploy-onnx.md	description: Learn how to train a model, convert it to ONNX, deploy it to Azure Previously updated : 06/21/2022 Last updated : 09/14/2023 ms.prod: sql ms.technology: machine-learning keywords: deploy SQL Edge - # Deploy and make predictions with an ONNX model and SQL machine learning +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + In this quickstart, you'll learn how to train a model, convert it to ONNX, deploy it to [Azure SQL Edge](onnx-overview.md), and then run native PREDICT on data using the uploaded ONNX model. This quickstart is based on scikit-learn and uses the [Boston Housing dataset](https://scikit-learn.org/0.24/modules/generated/sklearn.datasets.load_boston.html). ## Before you begin -* If you're using Azure SQL Edge, and you haven't deployed an Azure SQL Edge module, follow the steps of [deploy SQL Edge using the Azure portal](deploy-portal.md). +- If you're using Azure SQL Edge, and you haven't deployed an Azure SQL Edge module, follow the steps of [deploy SQL Edge using the Azure portal](deploy-portal.md). -* Install [Azure Data Studio](/sql/azure-data-studio/download). +- Install [Azure Data Studio](/sql/azure-data-studio/download). -* Install Python packages needed for this quickstart: +- Install Python packages needed for this quickstart: - 1. Open [New Notebook](/sql/azure-data-studio/sql-notebooks) connected to the Python 3 Kernel. + 1. Open [New Notebook](/sql/azure-data-studio/sql-notebooks) connected to the Python 3 Kernel. 1. Select Manage Packages - 1. In the Installed tab, look for the following Python packages in the list of installed packages. If any of these packages are not installed, select the Add New tab, search for the package, and select Install. + 1. In the Installed tab, look for the following Python packages in the list of installed packages. If any of these packages aren't installed, select the Add New tab, search for the package, and select Install. - scikit-learn - numpy - onnxmltools This quickstart is based on scikit-learn and uses the [Boston Housing datase - skl2onnx - sqlalchemy -* For each script part below, enter it in a cell in the Azure Data Studio notebook and run the cell. +- For each script part in the following sections, enter it in a cell in the Azure Data Studio notebook and run the cell. ## Train a pipeline boston = load_boston() boston df = pd.DataFrame(data=np.c_[boston['data'], boston['target']], columns=boston['feature_names'].tolist() + ['MEDV']) - + target_column = 'MEDV' - + # Split the data frame into features and target x_train = pd.DataFrame(df.drop([target_column], axis = 1)) y_train = pd.DataFrame(df.iloc[:,df.columns.tolist().index(target_column)]) print(y_train.head()) Output: -```text +```output * Training dataset x CRIM ZN INDUS CHAS NOX RM AGE DIS RAD TAX \ print(y_train.head()) 3 0.03237 0.0 2.18 0.0 0.458 6.998 45.8 6.0622 3.0 222.0 4 0.06905 0.0 2.18 0.0 0.458 7.147 54.2 6.0622 3.0 222.0 - PTRATIO B LSTAT -0 15.3 396.90 4.98 -1 17.8 396.90 9.14 -2 17.8 392.83 4.03 -3 18.7 394.63 2.94 -4 18.7 396.90 5.33 + PTRATIO B LSTAT +0 15.3 396.90 4.98 +1 17.8 396.90 9.14 +2 17.8 392.83 4.03 +3 18.7 394.63 2.94 +4 18.7 396.90 5.33 * Training dataset y print('* Scikit-learn MSE: {}'.format(sklearn_mse)) Output: -```text +```output * Scikit-learn r2 score: 0.7406426641094094 * Scikit-learn MSE: 21.894831181729206 ``` ## Convert the model to ONNX -Convert the data types to the supported SQL data types. This conversion will be required for other dataframes as well. +Convert the data types to the supported SQL data types. This conversion is required for other dataframes as well. ```python from skl2onnx.common.data_types import FloatTensorType, Int64TensorType, DoubleTensorType onnx_model_path = 'boston1.model.onnx' onnxmltools.utils.save_model(onnx_model, onnx_model_path) ``` -> [!NOTE] -> You may need to set the `target_opset` parameter for the skl2onnx.convert_sklearn function if there is a mismatch between ONNX runtime version in SQL Edge and skl2onnx packge. For more information, see the [SQL Edge Release notes](release-notes.md) to get the ONNX runtime version corresponding for the release, and pick the `target_opset` for the ONNX runtime based on the [ONNX backward compatibility matrix](https://github.com/microsoft/onnxruntime/blob/master/docs/Versioning.md#version-matrix). +> [!NOTE] +> You may need to set the `target_opset` parameter for the skl2onnx.convert_sklearn function if there's a mismatch between ONNX runtime version in SQL Edge and skl2onnx packge. For more information, see the [SQL Edge Release notes](release-notes.md) to get the ONNX runtime version corresponding for the release, and pick the `target_opset` for the ONNX runtime based on the [ONNX backward compatibility matrix](https://github.com/microsoft/onnxruntime/blob/master/docs/Versioning.md#version-matrix). ## Test the ONNX model After converting the model to ONNX format, score the model to show little to no degradation in performance. -> [!NOTE] +> [!NOTE] > ONNX Runtime uses floats instead of doubles so small discrepancies are possible. ```python print() Output: -```text +```output * Onnx r2 score: 0.7406426691136831 * Onnx MSE: 21.894830759270633 Load the data into SQL. First, create two tables, features and target*, to store subsets of the Boston housing dataset. - Features contains all data being used to predict the target, median value. -* Target contains the median value for each record in the dataset. +- Features contains all data being used to predict the target, median value. +- Target contains the median value for each record in the dataset. ```python import sqlalchemy print(x_train.head()) print(y_train.head()) ``` -Finally, use `sqlalchemy` to insert the `x_train` and `y_train` pandas dataframes into the tables `features` and `target`, respectively. +Finally, use `sqlalchemy` to insert the `x_train` and `y_train` pandas dataframes into the tables `features` and `target`, respectively. ```python db_connection_string = 'mssql+pyodbc://' + username + ':' + password + '@' + server + '/' + database + '?driver=ODBC+Driver+17+for+SQL+Server' Now you can view the data in the database. With the model in SQL, run native PREDICT on the data using the uploaded ONNX model. -> [!NOTE] +> [!NOTE] > Change the notebook kernel to SQL to run the remaining cell. ```sql DECLARE @model VARBINARY(max) = ( WITH predict_input AS ( - SELECT TOP (1000) [id] - , CRIM - , ZN - , INDUS - , CHAS - , NOX - , RM - , AGE - , DIS - , RAD - , TAX - , PTRATIO - , B - , LSTAT + SELECT TOP (1000) [id], + CRIM, + ZN, + INDUS, + CHAS, + NOX, + RM, + AGE, + DIS, + RAD, + TAX, + PTRATIO, + B, + LSTAT FROM [dbo].[features] ) -SELECT predict_input.id - , p.variable1 AS MEDV -FROM PREDICT(MODEL = @model, DATA = predict_input, RUNTIME=ONNX) WITH (variable1 FLOAT) AS p; +SELECT predict_input.id, + p.variable1 AS MEDV +FROM PREDICT(MODEL = @model, DATA = predict_input, RUNTIME = ONNX) WITH (variable1 FLOAT) AS p; ``` -## Next Steps +## Next steps -* [Machine Learning and AI with ONNX in SQL Edge](onnx-overview.md) +- [Machine Learning and AI with ONNX in SQL Edge](onnx-overview.md)
azure-sql-edge	Deploy Portal	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/deploy-portal.md	description: Learn how to deploy Azure SQL Edge using the Azure portal Previously updated : 01/13/2023 Last updated : 09/14/2023 keywords: deploy SQL Edge # Deploy Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + Azure SQL Edge is a relational database engine optimized for IoT and Azure IoT Edge deployments. It provides capabilities to create a high-performance data storage and processing layer for IoT applications and solutions. This quickstart shows you how to get started with creating an Azure SQL Edge module through Azure IoT Edge using the Azure portal. ## Before you begin Azure Marketplace is an online applications and services marketplace where you c 1. On the Environment Variables section of the Update IoT Edge Module pane, specify the desired values for the environment variables. For a complete list of Azure SQL Edge environment variables, see [Configure using environment variables](configure.md#configure-by-using-environment-variables). The following default environment variables are defined for the module. - \| Parameter \| Description \| + \| Parameter \| Description \| \| \| \| \| MSSQL_SA_PASSWORD \| Change the default value to specify a strong password for the SQL Edge admin account. \| \| MSSQL_LCID \| Change the default value to set the desired language ID to use for SQL Edge. For example, 1036 is French. \| Azure Marketplace is an online applications and services marketplace where you c - Binds and Mounts - If you need to deploy more than one SQL Edge module, ensure that you update the mounts option to create a new source and target pair for the persistent volume. For more information on mounts and volume, refer [Use volumes](https://docs.docker.com/storage/volumes/) on Docker documentation. + If you need to deploy more than one SQL Edge module, ensure that you update the mounts option to create a new source and target pair for the persistent volume. For more information on mounts and volume, see [Use volumes](https://docs.docker.com/storage/volumes/) on Docker documentation. ```json { Azure Marketplace is an online applications and services marketplace where you c ``` > [!IMPORTANT] - > Do not change the `PlanId` environment variable defined in the create config setting. If this value is changed, the Azure SQL Edge container will fail to start. + > Don't change the `PlanId` environment variable defined in the create config setting. If this value is changed, the Azure SQL Edge container will fail to start. > [!WARNING] > If you reinstall the module, remember to remove any existing bindings first, otherwise your environment variables will not be updated. 1. On the Update IoT Edge Module pane, select Update. -1. On the Set modules on device page select Next: Routes > if you need to define routes for your deployment. Otherwise select Review + Create. For more information on configuring routes, see [Deploy modules and establish routes in IoT Edge](../iot-edge/module-composition.md). +1. On the Set modules on device page, select Next: Routes > if you need to define routes for your deployment. Otherwise select Review + Create. For more information on configuring routes, see [Deploy modules and establish routes in IoT Edge](../iot-edge/module-composition.md). 1. On the Set modules on device page, select Create. ## Connect to Azure SQL Edge Azure Marketplace is an online applications and services marketplace where you c The following steps use the Azure SQL Edge command-line tool, sqlcmd, inside the container to connect to Azure SQL Edge. > [!NOTE] -> SQL Server command line tools, including sqlcmd, are not available inside the ARM64 version of Azure SQL Edge containers. +> SQL Server command line tools, including sqlcmd, aren't available inside the ARM64 version of Azure SQL Edge containers. 1. Use the `docker exec -it` command to start an interactive bash shell inside your running container. In the following example, `AzureSQLEdge` is name specified by the `Name` parameter of your IoT Edge Module. The following steps create a new database named `TestDB`. ```sql CREATE DATABASE TestDB; - Go + GO ``` 1. On the next line, write a query to return the name of all of the databases on your server: ```sql - SELECT Name from sys.databases; - Go + SELECT name from sys.databases; + GO ``` ### Insert data Next, create a new table called `Inventory`, and insert two new rows. 1. Insert data into the new table: ```sql - INSERT INTO Inventory VALUES (1, 'banana', 150); INSERT INTO Inventory VALUES (2, 'orange', 154); + INSERT INTO Inventory + VALUES (1, 'banana', 150); + + INSERT INTO Inventory + VALUES (2, 'orange', 154); ``` 1. Type `GO` to execute the previous commands: Now, run a query to return data from the `Inventory` table. ## Connect from outside the container -You can connect and run SQL queries against your Azure SQL Edge instance from any external Linux, Windows, or macOS tool that supports SQL connections. For more information on connecting to a SQL Edge container from outside, refer [Connect and Query Azure SQL Edge](./connect.md). +You can connect and run SQL queries against your Azure SQL Edge instance from any external Linux, Windows, or macOS tool that supports SQL connections. For more information on connecting to a SQL Edge container from outside, see [Connect and Query Azure SQL Edge](connect.md). In this quickstart, you deployed a SQL Edge Module on an IoT Edge device.
azure-sql-edge	Disconnected Deployment	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/disconnected-deployment.md	Title: Deploy Azure SQL Edge with Docker - Azure SQL Edge description: Learn about deploying Azure SQL Edge with Docker Previously updated : 01/13/2023 Last updated : 09/14/2023 keywords: - SQL Edge - container - - docker + - Docker # Deploy Azure SQL Edge with Docker +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + In this quickstart, you use Docker to pull and run the Azure SQL Edge container image. Then connect with sqlcmd to create your first database and run queries. This image consists of SQL Edge based on Ubuntu 18.04. It can be used with the Docker Engine 1.8+ on Linux. Azure SQL Edge containers aren't supported on the following platforms for produc \| Parameter \| Description \| \| \| \| \| -e "ACCEPT_EULA=Y" \| Set the ACCEPT_EULA variable to any value to confirm your acceptance of the [End-User Licensing Agreement](https://go.microsoft.com/fwlink/?linkid=2139274). Required setting for the SQL Edge image. \| - \| -e "MSSQL_SA_PASSWORD=yourStrong(!)Password" \| Specify your own strong password that is at least 8 characters and meets the [Azure SQL Edge password requirements](/sql/relational-databases/security/password-policy). Required setting for the SQL Edge image. \| + \| -e "MSSQL_SA_PASSWORD=yourStrong(!)Password" \| Specify your own strong password that is at least eight characters and meets the [Azure SQL Edge password requirements](/sql/relational-databases/security/password-policy). Required setting for the SQL Edge image. \| \| -p 1433:1433 \| Map a TCP port on the host environment (first value) with a TCP port in the container (second value). In this example, SQL Edge is listening on TCP 1433 in the container and this is exposed to the port, 1433, on the host. \| \| --name azuresqledge \| Specify a custom name for the container rather than a randomly generated one. If you run more than one container, you can't reuse this same name. \| \| -d \| Run the container in the background (daemon) \| Azure SQL Edge containers aren't supported on the following platforms for produc 1. To view your Docker containers, use the `docker ps` command. ```bash - sudo docker ps -a + sudo docker ps -a ``` 1. If the STATUS column shows a status of Up, then SQL Edge is running in the container and listening on the port specified in the PORTS column. If the STATUS column for your SQL Edge container shows Exited, see the Troubleshooting section of Azure SQL Edge documentation. - The `-h` (host name) parameter is also useful, but it isn't used in this tutorial for simplicity. This changes the internal name of the container to a custom value. This is the name you'll see returned in the following Transact-SQL query: + The `-h` (host name) parameter is also useful, but it isn't used in this tutorial for simplicity. This changes the internal name of the container to a custom value. This is the name that is returned in the following Transact-SQL query: ```sql SELECT @@SERVERNAME, SERVERPROPERTY('ComputerNamePhysicalNetBIOS'), SERVERPROPERTY('MachineName'), - SERVERPROPERTY('ServerName') + SERVERPROPERTY('ServerName'); ``` Setting `-h` and `--name` to the same value is a good way to easily identify the target container. Azure SQL Edge containers aren't supported on the following platforms for produc ## Change the SA password -The SA account is a system administrator on the Azure SQL Edge instance that gets created during setup. After creating your SQL Edge container, the `MSSQL_SA_PASSWORD` environment variable you specified is discoverable by running `echo $MSSQL_SA_PASSWORD` in the container. For security purposes, change your SA password. +The SA account is a system administrator on the Azure SQL Edge instance that gets created during setup. After you create your SQL Edge container, the `MSSQL_SA_PASSWORD` environment variable you specified is discoverable by running `echo $MSSQL_SA_PASSWORD` in the container. For security purposes, change your SA password. 1. Choose a strong password to use for the SA user. The SA account is a system administrator on the Azure SQL Edge instance that The following steps use the Azure SQL Edge command-line tool, sqlcmd, inside the container to connect to SQL Edge. -> [!NOTE] -> sqlcmd is not available inside the ARM64 version of SQL Edge containers. - 1. Use the `docker exec -it` command to start an interactive bash shell inside your running container. In the following example, `azuresqledge` is the name specified by the `--name` parameter when you created the container. ```bash sudo docker exec -it azuresqledge "bash" ``` -1. Once inside the container, connect locally with sqlcmd. Sqlcmd isn't in the path by default, so you have to specify the full path. +1. Once inside the container, connect locally with sqlcmd. sqlcmd isn't in the path by default, so you have to specify the full path. ```bash /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P "<YourNewStrong@Passw0rd>" The following steps create a new database named `TestDB`. 1. From the sqlcmd command prompt, paste the following Transact-SQL command to create a test database: ```sql - CREATE DATABASE TestDB - Go + CREATE DATABASE TestDB; + GO ``` 1. On the next line, write a query to return the name of all of the databases on your server: ```sql - SELECT Name from sys.Databases - Go + SELECT name from sys.databases; + GO ``` ### Insert data Next create a new table, `Inventory`, and insert two new rows. 1. From the sqlcmd command prompt, switch context to the new `TestDB` database: ```sql - USE TestDB + USE TestDB; ``` 1. Create new table named `Inventory`: ```sql - CREATE TABLE Inventory (id INT, name NVARCHAR(50), quantity INT); + CREATE TABLE Inventory ( + id INT, + name NVARCHAR(50), + quantity INT + ); ``` 1. Insert data into the new table: ```sql - INSERT INTO Inventory VALUES (1, 'banana', 150); INSERT INTO Inventory VALUES (2, 'orange', 154); + INSERT INTO Inventory + VALUES (1, 'banana', 150); + + INSERT INTO Inventory + VALUES (2, 'orange', 154); ``` 1. Type `GO` to execute the previous commands: Now, run a query to return data from the `Inventory` table. ## Connect from outside the container -You can also connect to the SQL Edge instance on your Docker machine from any external Linux, Windows, or macOS tool that supports SQL connections. For more information on connecting to a SQL Edge container from outside, refer [Connect and Query Azure SQL Edge](connect.md). +You can also connect to the SQL Edge instance on your Docker machine from any external Linux, Windows, or macOS tool that supports SQL connections. For more information on connecting to a SQL Edge container from outside, see [Connect and Query Azure SQL Edge](connect.md). ## Remove your container
azure-sql-edge	Drop External Stream Transact Sql	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/drop-external-stream-transact-sql.md	Title: DROP EXTERNAL STREAM (Transact-SQL) - Azure SQL Edge description: Learn about the DROP EXTERNAL STREAM statement in Azure SQL Edge - Previously updated : 05/19/2020 Last updated : 09/14/2023 - - # DROP EXTERNAL STREAM (Transact-SQL) -Drops a streaming job. +Drops a streaming job. ## Syntax -```sql -DROP EXTERNAL STREAM {external_stream_name} +```syntaxsql +DROP EXTERNAL STREAM { external_stream_name } ``` ## See also -- [CREATE EXTERNAL STREAM (Transact-SQL)](create-external-stream-transact-sql.md) +- [CREATE EXTERNAL STREAM (Transact-SQL)](create-external-stream-transact-sql.md)
azure-sql-edge	Features	https://github.com/MicrosoftDocs/azure-docs/commits/main/articles/azure-sql-edge/features.md	Title: Supported features of Azure SQL Edge description: Learn about details of features supported by Azure SQL Edge. Previously updated : 06/29/2023 Last updated : 09/14/2023 keywords: keywords: # Supported features of Azure SQL Edge +> [!IMPORTANT] +> Azure SQL Edge no longer supports the ARM64 platform. + Azure SQL Edge is built on the latest version of the SQL Database Engine. It supports a subset of the features supported in SQL Server 2022 on Linux, in addition to some features that are currently not supported or available in SQL Server 2022 on Linux (or in SQL Server on Windows). For a complete list of the features supported in SQL Server on Linux, see [Editions and supported features of SQL Server 2022 on Linux](/sql/linux/sql-server-linux-editions-and-components-2022). For editions and supported features of SQL Server on Windows, see [Editions and supported features of SQL Server 2022 (16.x)](/sql/sql-server/editions-and-components-of-sql-server-2022). The recommended and supported file system for Azure SQL Edge is EXT4 and XFS. If ## Hardware support -Azure SQL Edge requires a 64-bit processor (either x64 or ARM64), with a minimum of 1 CPU and 1 GB of RAM on the host. While the startup memory footprint of Azure SQL Edge is close to 450 MB, the additional memory is needed for other IoT Edge modules or processes running on the edge device. The actual memory and CPU requirements for Azure SQL Edge will vary based on the complexity of the workload and volume of data being processed. When choosing hardware for your solution, Microsoft recommends that you run extensive performance tests to ensure that the required performance characteristics for your solution are met. +Azure SQL Edge requires an x86 64-bit processor, with a minimum of 1 CPU core, and 1 GB of RAM on the host. While the startup memory footprint of Azure SQL Edge is close to 450 MB, the additional memory is needed for other IoT Edge modules or processes running on the edge device. The actual memory and CPU requirements for Azure SQL Edge will vary based on the complexity of the workload and volume of data being processed. When you choose hardware for your solution, Microsoft recommends that you run extensive performance tests to ensure that the required performance characteristics for your solution are met. ## Azure SQL Edge components -Azure SQL Edge only supports the database engine. It doesn't include support for other components available with SQL Server 2022 on Windows or with SQL Server 2022 on Linux. Specifically, Azure SQL Edge doesn't support SQL Server components like Analysis Services, Reporting Services, Integration Services, Master Data Services, Machine Learning Services (In-Database), and Machine Learning Server (standalone). +Azure SQL Edge only supports the Database Engine. It doesn't include support for other components available with SQL Server 2022 on Windows or with SQL Server 2022 on Linux. Specifically, Azure SQL Edge doesn't support SQL Server components like Analysis Services, Reporting Services, Integration Services, Master Data Services, Machine Learning Services (In-Database), and Machine Learning Server (standalone). ## Supported features In addition to supporting a subset of features of SQL Server on Linux, Azure SQL Edge includes support for the following new features: - SQL streaming, which is based on the same engine that powers Azure Stream Analytics, provides real-time data streaming capabilities in Azure SQL Edge.-- The T-SQL function call `Date_Bucket` for Time-Series data analytics.-- Machine learning capabilities through the ONNX runtime, included with the SQL engine. +- The T-SQL function call `DATE_BUCKET` for Time-Series data analytics. +- Machine learning capabilities through the ONNX runtime, included with the SQL Database Engine. ## Unsupported features
azure-sql-edge