Merge pull request #234222 from MicrosoftDocs/main

Publish to Live Wednesday 4AM PST, 04/12

Author: PMEds28

articles/active-directory/saas-apps/howspace-provisioning-tutorial.md

@@ -0,0 +1,144 @@
+---
+title: 'Tutorial: Configure Howspace for automatic user provisioning with Azure Active Directory'
+description: Learn how to automatically provision and deprovision user accounts from Azure AD to Howspace.
+services: active-directory
+author: twimmers
+writer: twimmers
+manager: beatrizd
+ms.assetid: 4cc83a2e-916c-464b-8a8e-5e68c3aeb9f4
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: tutorial
+ms.date: 04/12/2023
+ms.author: thwimmer
+---
+
+# Tutorial: Configure Howspace for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both Howspace and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and deprovisions users and groups to [Howspace](https://www.howspace.com/) using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+
+
+## Supported capabilities
+> [!div class="checklist"]
+> * Create users in Howspace.
+> * Remove users in Howspace when they do not require access anymore.
+> * Keep user attributes synchronized between Azure AD and Howspace.
+> * Provision groups and group memberships in Howspace.
+> * [Single sign-on](../manage-apps/add-application-portal-setup-oidc-sso.md) to Howspace (recommended).
+
+## Prerequisites
+
+The scenario outlined in this tutorial assumes that you already have the following prerequisites:
+
+* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md) 
+* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
+* A user account in Howspace with Admin permissions.
+
+## Step 1. Plan your provisioning deployment
+1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
+1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+1. Determine what data to [map between Azure AD and Howspace](../app-provisioning/customize-application-attributes.md).
+
+## Step 2. Configure Howspace to support provisioning with Azure AD
+Contact Howspace support to configure Howspace to support provisioning with Azure AD.
+
+## Step 3. Add Howspace from the Azure AD application gallery
+
+Add Howspace from the Azure AD application gallery to start managing provisioning to Howspace. If you have previously setup Howspace for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+
+## Step 4. Define who will be in scope for provisioning 
+
+The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control provisioning by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
+
+
+## Step 5. Configure automatic user provisioning to Howspace 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
+
+### To configure automatic user provisioning for Howspace in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
+
+1. In the applications list, select **Howspace**.
+
+	![Screenshot of the Howspace link in the Applications list.](common/all-applications.png)
+
+1. Select the **Provisioning** tab.
+
+	![Screenshot of Provisioning tab.](common/provisioning.png)
+
+1. Set the **Provisioning Mode** to **Automatic**.
+
+	![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
+
+1. Under the **Admin Credentials** section, input your Howspace Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Howspace. If the connection fails, ensure your Howspace account has Admin permissions and try again.
+
+ 	![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
+
+1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
+
+	![Screenshot of Notification Email.](common/provisioning-notification-email.png)
+
+1. Select **Save**.
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Howspace**.
+
+1. Review the user attributes that are synchronized from Azure AD to Howspace in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Howspace for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you need to ensure that the Howspace API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for filtering|Required by Howspace|
+   |---|---|---|---|
+   |userName|String|✓|✓
+   |active|Boolean||
+   |name.givenName|String||
+   |name.familyName|String||
+   |phoneNumbers[type eq "work"].value|String||
+   |externalId|String||
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Howspace**.
+
+1. Review the group attributes that are synchronized from Azure AD to Howspace in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Howspace for update operations. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for filtering|Required by Howspace|
+   |---|---|---|---|
+   |displayName|String|✓|✓
+   |externalId|String||
+   |members|Reference||
+   
+1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+1. To enable the Azure AD provisioning service for Howspace, change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
+
+1. Define the users and/or groups that you would like to provision to Howspace by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
+
+1. When you're ready to provision, click **Save**.
+
+	![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
+
+This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. 
+
+## Step 6. Monitor your deployment
+Once you've configured provisioning, use the following resources to monitor your deployment:
+
+* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
+* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion
+* If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
+
+## More resources
+
+* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
+* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+
+## Next steps
+
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/toc.yml

@@ -3088,6 +3088,8 @@
         href: hootsuite-provisioning-tutorial.md
       - name: Hoxhunt
         href: hoxhunt-provisioning-tutorial.md
+      - name: Howspace
+        href: howspace-provisioning-tutorial.md
       - name: H5mag
         href: h5mag-provisioning-tutorial.md
       - name: Ideo

articles/active-directory/saas-apps/vera-suite-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: how-to
-ms.date: 03/31/2023
+ms.date: 04/12/2023
 ms.author: jeedes
 
 ---
@@ -56,24 +56,8 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
 1. In the Azure portal, on the **Vera Suite** application integration page, find the **Manage** section and select **single sign-on**.
 1. On the **Select a single sign-on method** page, select **SAML**.
-1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings.
 
-   ![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
-
-1. On the **Basic SAML Configuration** section, perform the following steps:
-
-	a. In the **Identifier** textbox, type the URL:
-	`https://logon.mykpa.com/identity/Saml2/`
-
-	b. In the **Reply URL** textbox, type the URL:
-	`https://logon.mykpa.com/identity/Saml2/Acs`
-
-	c. In the **Sign on URL** textbox, type one of the following URLs:
-	
-	| **Sign on URL** |
-	|-------------|
-	| `https://www.verasuite.com` |
-	| `https://logon.mykpa.com` |
+1. On the **Basic SAML Configuration** section, the user does not have to perform any step as the app is already pre-integrated with Azure.
 
 1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
 

articles/azure-web-pubsub/howto-develop-create-instance.md

@@ -1,32 +1,139 @@
 ---
-title: Quickstart - Create a Web PubSub instance from Azure portal
-description: Quickstart showing how to create a Web PubSub instance from Azure portal
-author: yjin81
-ms.author: yajin1
+title: Create an Azure Web PubSub resource
+titleSuffix: Azure Web PubSub
+description: Quickstart showing how to create a Web PubSub resource from Azure portal, using Azure CLI and a Bicep template 
+author: kevinguo-ed
+ms.author: kevinguo
 ms.service: azure-web-pubsub
 ms.topic: quickstart
-ms.date: 11/08/2021
+ms.date: 03/13/2023
 ms.custom: mode-ui
+zone_pivot_groups: azure-web-pubsub-create-resource-methods
 ---
+# Create a Web PubSub resource
 
-# Quickstart: Create a Web PubSub instance from Azure portal
+## Prerequisites
+> [!div class="checklist"]
+> * An Azure account with an active subscription. [Create a free Azure account](https://azure.microsoft.com/free/), if don't have one already.  
 
-This quickstart shows you how to create Azure Web PubSub instance from Azure portal.
+> [!TIP]
+> Web PubSub includes a generous **free tier** that can be used for testing and production purposes.
+ 
+ 
+::: zone pivot="method-azure-portal"
+## Create a resource from Azure portal
 
-[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
+1. Select the New button found on the upper left-hand corner of the Azure portal. In the New screen, type **Web PubSub** in the search box and press enter. 
 
-[!INCLUDE [create-instance-portal](includes/create-instance-portal.md)]
+    :::image type="content" source="./media/create-instance-portal/search-web-pubsub-in-portal.png" alt-text="Screenshot of searching the Azure Web PubSub in portal.":::
 
-## Try the newly created instance
+2. Select **Web PubSub** from the search results, then select **Create**.
 
-> [!div class="nextstepaction"]
-> [Try the instance from the browser](./quickstart-live-demo.md#try-the-instance-with-an-online-demo)
+3. Enter the following settings.
 
-> [!div class="nextstepaction"]
-> [Try the instance with Azure CLI](./quickstart-cli-try.md#play-with-the-instance)
+    | Setting      | Suggested value  | Description                                        |
+    | ------------ |  ------- | -------------------------------------------------- |
+    | **Resource name** | Globally unique name | The globally unique Name that identifies your new Web PubSub service instance. Valid characters are `a-z`, `A-Z`, `0-9`, and `-`. |
+    | **Subscription** | Your subscription | The Azure subscription under which this new Web PubSub service instance is created. |
+    | **[Resource Group]** |  myResourceGroup | Name for the new resource group in which to create your Web PubSub service instance. |
+    | **Location** | West US | Choose a [region](https://azure.microsoft.com/regions/) near you. |
+    | **Pricing tier** | Free | You can first try Azure Web PubSub service for free. Learn more details about [Azure Web PubSub service pricing tiers](https://azure.microsoft.com/pricing/details/web-pubsub/) |
+    | **Unit count** |  - | Unit count specifies how many connections your Web PubSub service instance can accept. Each unit supports 1,000 concurrent connections at most. It is only configurable in the Standard tier. |
+
+    :::image type="content" source="./media/howto-develop-create-instance/create-web-pubsub-instance-in-portal.png" alt-text="Screenshot of creating the Azure Web PubSub instance in portal.":::
+
+4. Select **Create** to provision your Web PubSub resource.
+::: zone-end
+
+
+::: zone pivot="method-azure-cli"
+## Create a resource using Azure CLI
+
+The [Azure CLI](/cli/azure) is a set of commands used to create and manage Azure resources. The Azure CLI is available across Azure services and is designed to get you working quickly with Azure, with an emphasis on automation. 
+
+> [!IMPORTANT]
+> This quickstart requires Azure CLI of version 2.22.0 or higher.
+
+## Create a resource group
+
+[!INCLUDE [Create a resource group](includes/cli-rg-creation.md)]
+
+## Create a resource
+
+[!INCLUDE [Create a Web PubSub instance](includes/cli-awps-creation.md)]
+::: zone-end
+
+
+::: zone pivot="method-bicep"
+## Create a resource using Bicep template
+
+[!INCLUDE [About Bicep](../../includes/resource-manager-quickstart-bicep-introduction.md)]
+
+## Review the Bicep file
+
+The template used in this quickstart is from [Azure Quickstart Templates](/samples/azure/azure-quickstart-templates/azure-web-pubsub/).
+
+:::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.web/azure-web-pubsub/main.bicep":::
+
+## Deploy the Bicep file
 
-## Next steps
+1. Save the Bicep file as **main.bicep** to your local computer.
+1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
 
-In real-world applications, you can use SDKs in various languages build your own application. We also provide Function extensions for you to build serverless applications easily.
+    # [CLI](#tab/CLI)
 
-[!INCLUDE [next step](includes/include-next-step.md)]
+    ```azurecli
+    az group create --name exampleRG --location eastus
+    az deployment group create --resource-group exampleRG --template-file main.bicep
+    ```
+
+    # [PowerShell](#tab/PowerShell)
+
+    ```azurepowershell
+    New-AzResourceGroup -Name exampleRG -Location eastus
+    New-AzResourceGroupDeployment -ResourceGroupName exampleRG -TemplateFile ./main.bicep
+    ```
+
+    ---
+
+    When the deployment finishes, you should see a message indicating the deployment succeeded.
+
+## Review deployed resources
+
+Use the Azure portal, Azure CLI, or Azure PowerShell to list the deployed resources in the resource group.
+
+# [CLI](#tab/CLI)
+
+```azurecli-interactive
+az resource list --resource-group exampleRG
+```
+
+# [PowerShell](#tab/PowerShell)
+
+```azurepowershell-interactive
+Get-AzResource -ResourceGroupName exampleRG
+```
+
+---
+## Clean up resources
+
+When no longer needed, use the Azure portal, Azure CLI, or Azure PowerShell to delete the resource group and its resources.
+
+# [CLI](#tab/CLI)
+
+```azurecli-interactive
+az group delete --name exampleRG
+```
+
+# [PowerShell](#tab/PowerShell)
+
+```azurepowershell-interactive
+Remove-AzResourceGroup -Name exampleRG
+```
+::: zone-end
+
+## Next step
+Now that you have created a resource, you are ready to put it to use.
+Next, you will learn how to subscribe and publish messages among your clients.
+> [!div class="nextstepaction"]
+> [PubSub among clients](quickstarts-pubsub-among-clients.md)