Skip to content

Commit 90f09d8

Browse files
committed
Removed Workspaces tabs
1 parent 057f076 commit 90f09d8

File tree

6 files changed

+0
-231
lines changed

6 files changed

+0
-231
lines changed

articles/marketplace/includes/preview-interface.md

Lines changed: 0 additions & 15 deletions
This file was deleted.

articles/marketplace/support.md

Lines changed: 0 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,6 @@ Microsoft provides support for a wide variety of products and services. Finding
1919

2020
## Get help or open a support ticket
2121

22-
#### [Workspaces view](#tab/workspaces-view)
23-
2422
1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard/home) with your work account. If you have not yet done so, you will need to [create a Partner Center account](create-account.md).
2523

2624
1. On the Home page, select the **Help + support** tile.
@@ -53,58 +51,14 @@ If you cannot find your answer in the self help, select **Provide issue details*
5351
>[!Note]
5452
>If you have not signed in to Partner Center, you may be required to sign in before you can create a ticket.
5553
56-
#### [Current view](#tab/current-view)
57-
58-
1. Sign in with your work account. If you have not yet done so, you will need to [create a Partner Center account](create-account.md).
59-
60-
1. In the menu on the upper-right of the page, select the **Support** icon. The **Help and support** pane appears on the right side of the page.
61-
62-
1. For help with the commercial marketplace, select **Commercial Marketplace**.
63-
64-
![Support drop-down menu](./media/support/commercial-marketplace-support-pane.png)
65-
66-
1. In the **Problem summary** box, enter a brief description of the issue.
67-
68-
1. In the **Problem type** box, do one of the following:
69-
70-
- **Option 1**: Enter keywords such as: Marketplace, Azure app, SaaS offer, account management, lead management, deployment issue, payout, or co-sell offer migration. Then select a problem type from the recommended list that appears.
71-
72-
- **Option 2**: Select **Browse topics** from the **Category** list and then select **Commercial Marketplace**. Then select the appropriate **Topic** and **Subtopic**.
73-
74-
1. After you have found the topic of your choice, select **Review Solutions**.
75-
76-
![Next step](./media/support/next-step.png)
77-
78-
The following options are shown:
79-
80-
- To select a different topic, click **Select a different issue**.
81-
- To help solve the issue, review the recommended steps and documents, if available.
82-
83-
![Recommended solutions](./media/support/recommended-solutions.png)
84-
85-
If you cannot find your answer in the self help, select **Provide issue details**. Complete all required fields to speed up the resolution process, then select **Submit**.
86-
87-
>[!Note]
88-
>If you have not signed in to Partner Center, you may be required to sign in before you can create a ticket.
89-
90-
---
91-
9254
## Track your existing support requests
9355

94-
#### [Workspaces view](#tab/workspaces-view)
95-
9656
1. To review your open and closed tickets, sign in to [Partner Center](https://partner.microsoft.com/dashboard/home) with your work account.
9757

9858
1. On the Home page, select the **Help + support** tile.
9959

10060
[ ![Illustrates the Partner Center Home page with the Help + support tile highlighted.](./media/workspaces/partner-center-help-support-tile.png) ](./media/workspaces/partner-center-help-support-tile.png#lightbox)
10161

102-
#### [Current view](#tab/current-view)
103-
104-
To review your open and closed tickets, in the left-navigation menu, select **Commercial Marketplace** > **Support**.
105-
106-
---
107-
10862
## Record issue details with a HAR file
10963

11064
To help support agents troubleshoot your issue, consider attaching an HTTP Archive format (HAR) file to your support ticket. HAR files are logs of network requests in a web browser.

articles/marketplace/switch-accounts.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,6 @@ You can be part of more than one account. This article describes how to see if y
2121

2222
## View and switch accounts
2323

24-
[!INCLUDE [Workspaces view note](./includes/preview-interface.md)]
25-
26-
#### [Workspaces view](#tab/workspaces-view)
27-
2824
You can check to see if you are part of multiple accounts by the presence of the _account picker_. In the top-right, select the your account icon as seen highlighted in the following screenshot.
2925

3026
[ ![Illustrates the account picker in Partner Center.](./media/manage-accounts/account-picker-workspaces.png) ](./media/manage-accounts/account-picker-workspaces.png#lightbox)
@@ -40,25 +36,6 @@ In the following example, the signed-in user is part of the four highlighted acc
4036

4137
[ ![Screenshot of accounts that can be selected with the account picker.](./media/manage-accounts/account-picker-two-workspaces.png) ](./media/manage-accounts/account-picker-two-workspaces.png#lightbox)
4238

43-
#### [Current view](#tab/current-view)
44-
45-
You can check to see if you are part of multiple accounts by the presence of the *account picker* in the left navigation menu, as seen highlighted in the following screenshot.
46-
47-
[ ![Screenshot of the account picker in the left-nav of Partner Center.](./media/manage-accounts/account-picker.png) ](./media/manage-accounts/account-picker.png#lightbox)
48-
49-
If you don't see the *account picker*, you are part of one account only. You can find the details of this account on the **Account settings** > **Organization profile** > **Legal** > **Developer** tab in Partner Center.
50-
51-
When you select this picker, all the accounts that you are a part of appear as a list. You can then select any of them to switch to that account. After you switch, everything in Partner Center appears in the context of that account.
52-
53-
> [!NOTE]
54-
> Partner Center uses [Azure Active Directory](../active-directory/fundamentals/active-directory-whatis.md) (Azure AD) for multi-user account access and management. Your organization's Azure AD is automatically associated with your Partner Center account as part of the enrollment process.
55-
56-
In the following example, the signed-in user is part of the three highlighted accounts. The user can switch between them by clicking on an account.
57-
58-
[ ![Screenshot of accounts that can be selected with the account picker.](./media/manage-accounts/account-picker-two.png) ](./media/manage-accounts/account-picker-two.png#lightbox)
59-
60-
---
61-
6239
## Next steps
6340

6441
- [Add and manage users for the commercial marketplace](add-manage-users.md)

articles/marketplace/test-drive-hosted-detailed-config.md

Lines changed: 0 additions & 103 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,6 @@ This article describes how to configure a hosted test drive for Dynamics 365 app
1818
1919
## Configure for Dynamics 365 apps on Dataverse and Power Apps
2020

21-
[!INCLUDE [Workspaces view note](./includes/preview-interface.md)]
22-
23-
#### [Workspaces view](#tab/workspaces-view)
24-
2521
1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard/commercial-marketplace/overview).
2622
2. If you can't access the above link, you need to submit a request [here](https://appsource.microsoft.com/partners/list-an-app) to publish your application. Once we review the request, you will be granted access to start the publish process.
2723
3. Find an existing **Dynamics 365 apps on Dataverse and Power Apps** offer or create a new **Dynamics 365 apps on Dataverse and Power Apps** offer.
@@ -61,69 +57,8 @@ This article describes how to configure a hosted test drive for Dynamics 365 app
6157
- **User manual** – A PDF user manual that helps test drive users understand how to use your app (required).
6258
- **Test drive demo video** – A video that showcases your app (optional).
6359

64-
#### [Current view](#tab/current-view)
65-
66-
1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard/commercial-marketplace/overview).
67-
2. If you can't access the above link, you need to submit a request [here](https://appsource.microsoft.com/partners/list-an-app) to publish your application. Once we review the request, you will be granted access to start the publish process.
68-
3. Find an existing **Dynamics 365 apps on Dataverse and Power Apps** offer or create a new **Dynamics 365 apps on Dataverse and Power Apps** offer.
69-
4. Select the **Enable a test drive** check box and select a **Type of test drive** (see bullet below), then select **Save**.
70-
71-
[![Selecting the 'Enable a test drive' check box.](media/test-drive/enable-test-drive-check-box.png)](media/test-drive/enable-test-drive-check-box.png#lightbox)
72-
73-
- **Type of test drive** – Choose **Dynamics 365 apps on Dataverse and Power Apps**. This indicates that Microsoft will host and maintain the service that performs the test drive user provisioning and deprovisioning.
74-
75-
5. Grant Microsoft AppSource permission to provision and deprovision test drive users in your tenant using [these instructions](./test-drive-azure-subscription-setup.md). In this step, you will generate the **Azure AD App ID** and **Azure AD App Key** values mentioned below.
76-
6. Complete these fields on the **Test drive technical configuration** page.
77-
78-
[![The test drive technical configuration page.](media/test-drive/technical-config-details.png)](media/test-drive/technical-config-details.png#lightbox)
79-
80-
- **Max concurrent test drives** – The number of concurrent users that can have an active test drive running at the same time. Each user will consume a Dynamics license while their test drive is active, so ensure you have at least this many Dynamics licenses available for test drive users. We recommended 3 to 5.
81-
- **Test drive duration** – The number of hours the user's test drive will be active. After the time has expired, the user will be deprovisioned from your tenant. We recommended 2-24 hours depending on the complexity of your app. The user can always request another test drive if they run out of time and want to access the test drive again.
82-
- **Instance URL**
83-
- *Customer Engagement* – The URL the test drive user will be sent to when they start the test drive. This is typically the URL of your Dynamics 365 instance on which your app and sample data is installed. Example value: `https://testdrive.crm.dynamics.com`.
84-
- *Canvas App (Power Apps)*
85-
1. Open the **PowerApps portal** page and sign in.
86-
2. Select **Apps** and then the ellipses at the app.
87-
4. Select **Details**.
88-
5. Copy the **Web link** from the **Details** tab:
89-
90-
[ ![Shows the TestDrive Canvas App window.](./media/test-drive/testdrive-canvas-app.png) ](./media/test-drive/testdrive-canvas-app.png#lightbox)
91-
92-
- **Instance web API URL**
93-
- *Customer Engagement* – The Web API URL for your Dynamics 365 Instance. Retrieve this value by signing into your Microsoft Dynamics 365 instance, selecting **Setting** > **Customization** > **Developer Resources** > **Instance Web API**, and copying the address (URL). Example value:
94-
95-
:::image type="content" source="./media/test-drive/sample-web-api-url.png" alt-text="An example of Instance Web API.":::
96-
97-
- *Canvas App (Power Apps)* – If you are not using CE/Dataverse as a backend to your Canvas App, use `https://localhost` as a placeholder.
98-
99-
- **Role name**
100-
- *Customer Engagement* – The name of the custom Dynamics 365 security role you created for test drive or you can use an existing role. A new role should have minimum required privileges added to the role to sign into a Customer Engagement instance. Refer to [Minimum privileges required to sign into Microsoft Dynamics 365](https://community.dynamics.com/crm/b/crminogic/archive/2016/11/24/minimum-privileges-required-to-login-microsoft-dynamics-365). This is the role that will be assigned to users during their test drive. Example value: `testdriverole`.
101-
- *Canvas App (Power Apps)* – Use "NA" when not using CE/Dataverse as the backend data source.
102-
103-
> [!IMPORTANT]
104-
> Ensure the security group check is not added. This allows the user to be synced to the Customer Engagement instance.
105-
106-
- **Azure Active Directory tenant ID** – The ID of the Azure tenant for your Dynamics 365 instance. To retrieve this value, sign in to Azure portal and navigate to **Azure Active Directory** > **Properties** and copy the directory ID. Example value: 172f988bf-86f1-41af-91ab-2d7cd01112341.
107-
- **Azure Active Directory tenant name** – The name of the Azure Tenant for your Dynamics 365 Instance. Use the format `<tenantname>.onmicrosoft.com`. Example Value: `testdrive.onmicrosoft.com`.
108-
- **Azure Active Directory application ID** – The ID of the Azure Active Directory (AD) app you created in Step 5. Example value: `53852862-a2ae-4e43-9461-faa49650a096`.
109-
- **Azure Active Directory application client secret** – Secret for the Azure AD app created in Step 5. Example value: `IJUgaIOfq9b9LbUjeQmzNBW4VGn6grr1l/n3aMrnfdk=`.
110-
111-
7. Provide the marketplace listing details. Select **Language** to see further required fields.
112-
113-
[ ![Illustrates Marketplace listing details page.](./media/test-drive/marketplace-listing-details-workspaces.png) ](./media/test-drive/marketplace-listing-details-workspaces.png#lightbox)
114-
115-
- **Description** – An overview of your test drive. This text will be shown to the user while the test drive is being provisioned. This field supports HTML if you want to provide formatted content (required).
116-
- **User manual** – A PDF user manual that helps test drive users understand how to use your app (required).
117-
- **Test drive demo video** – A video that showcases your app (optional).
118-
119-
---
120-
12160
## Dynamics 365 Operations Apps
12261

123-
[!INCLUDE [Workspaces view note](./includes/preview-interface.md)]
124-
125-
#### [Workspaces view](#tab/workspaces-view)
126-
12762
1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard/commercial-marketplace/overview).
12863
2. If you can't access the above link, you need to submit a request [here](https://appsource.microsoft.com/partners/list-an-app) to publish your application. Once we review the request, you will be granted access to start the publish process.
12964
3. Find an existing **Dynamics 365 Operations Apps** offer or create a new **Dynamics 365 Operations Apps** offer.
@@ -158,44 +93,6 @@ This article describes how to configure a hosted test drive for Dynamics 365 app
15893
- **User manual** – A PDF user manual that helps test drive users understand how to use your app (required).
15994
- **Test drive demo video** – A video that showcases your app (optional).
16095

161-
#### [Current view](#tab/current-view)
162-
163-
1. Sign in to [Partner Center](https://go.microsoft.com/fwlink/?linkid=2165507).
164-
2. If you can't access the above link, you need to submit a request [here](https://appsource.microsoft.com/partners/list-an-app) to publish your application. Once we review the request, you will be granted access to start the publish process.
165-
3. Find an existing **Dynamics 365 Operations Apps** offer or create a new **Dynamics 365 Operations Apps** offer.
166-
4. Select the **Enable a test drive** check box and select a **Type of test drive** (see bullet below), then select **Save draft**.
167-
168-
[![Select the 'Enable a test drive' check box.](media/test-drive/enable-test-drive-check-box-operations.png)](media/test-drive/enable-test-drive-check-box-operations.png#lightbox)
169-
170-
- **Type of test drive** – Choose **Dynamics 365 Operations Apps** option. This means Microsoft will host and maintain the service that performs the test drive user provisioning and deprovisioning.
171-
172-
5. Grant Microsoft AppSource permission to provision and deprovision test drive users in your tenant using [these instructions](https://github.com/Microsoft/AppSource/blob/master/Microsoft%20Hosted%20Test%20Drive/Setup-your-Azure-subscription-for-Dynamics365-Microsoft-Hosted-Test-Drives.md). In this step, you will generate the **Azure AD App ID** and **Azure AD App Key** values mentioned below.
173-
6. Complete these fields on the **Test drive technical configuration** page.
174-
175-
[![The Marketplace technical configuration page.](media/test-drive/technical-config-details.png)](media/test-drive/technical-config-details.png#lightbox)
176-
177-
- **Max concurrent test drives** – The number of concurrent users that can have an active test drive running at the same time. Each user will consume a Dynamics license while their test drive is active, so ensure you have at least this many Dynamics licenses available for test drive users. We recommended 3 to 5.
178-
- **Test drive duration** – The number of hours the user's test drive will be active. After the time has expired, the user will be deprovisioned from your tenant. We recommended 2-24 hours depending on the complexity of your app. The user can always request another test drive if they run out of time and want to access the test drive again.
179-
- **Instance URL** – The URL the test drive user will be sent to when they start the test drive. This is typically the URL of your Dynamics 365 instance on which your app and sample data is installed. Example value: `https://testdrive.crm.dynamics.com`.
180-
- **Azure Active Directory tenant ID** – The ID of the Azure tenant for your Dynamics 365 instance. To retrieve this value, sign in to Azure portal and navigate to **Azure Active Directory** > **Properties** and copy the directory ID. Example value: 172f988bf-86f1-41af-91ab-2d7cd01112341.
181-
- **Azure Active Directory tenant name** – The name of the Azure Tenant for your Dynamics 365 Instance. Use the format `<tenantname>.onmicrosoft.com`. Example Value: `testdrive.onmicrosoft.com`.
182-
- **Azure Active Directory application ID** – The ID of the Azure Active Directory (AD) app you created in Step 5. Example value: `53852862-a2ae-4e43-9461-faa49650a096`.
183-
- **Azure Active Directory application client secret** – Secret for the Azure AD app created in Step 5. Example value: `IJUgaIOfq9b9LbUjeQmzNBW4VGn6grr1l/n3aMrnfdk=`.
184-
- **Trial Legal Entity** – Provide a Legal Entity to assign a trial user. You can create a new one at [Create or modify a legal entity](/dynamicsax-2012/appuser-itpro/create-or-modify-a-legal-entity).
185-
- **Role name** – The AOT name (Application Object Tree) of the custom Dynamics 365 security role you created for test drive. This is the role that will be assigned to users during their test drive.
186-
187-
:::image type="content" source="./media/test-drive/security-config.png" alt-text="The security configuration page.":::
188-
189-
7. Provide the marketplace listing details. Select **Language** to see further required fields.
190-
191-
[![The Marketplace listing details page.](media/test-drive/marketplace-listing-details.png)](media/test-drive/marketplace-listing-details.png#lightbox)
192-
193-
- **Description** – An overview of your test drive. This text will be shown to the user while the test drive is being provisioned. This field supports HTML if you want to provide formatted content.
194-
- **User manual** – A PDF user manual that helps test drive users understand how to use your app.
195-
- **Test drive demo video** – A video that showcases your app (optional).
196-
197-
---
198-
19996
<!--
20097
## Next steps
20198

0 commit comments

Comments
 (0)