Describe the bug
The setup script fails if the resource group already exists. This is due to a wrong comparison operator here https://github.com/microsoft/mona-saas/blob/main/Mona.SaaS/Mona.SaaS.Setup/basic-deploy.sh#L228

Instead of using -eq it must be ==.

To Reproduce
Steps to reproduce the behavior:

Pre-create a resource group and then run the setup script as described in the README.md.

Expected behavior

Setup script does not fail if the resource group already exists.

When running the basic-deploy.sh script locally I get stuck in an infinite loop of login prompt. I discovered that the "id" property does not exists in the Azure CLI (tried both Windows and macOS). The same value is present in a property named "objectId".

If we decide to allow running the script locally and harden check for dependencies, I think we need to check for both id and objectId to get the user id.

I do not yet know what, if anything, breaks as a result. Just making a note that the property name for user id is different in Cloud Shell and local Azure CLI.

I want to configure a custom domain en Azure App Services, After I did it, when I am redirect to login page I get this error
Message: AADSTS50011: The redirect URI 'https://XXXXXX/signin-oidc' specified in the request does not match the redirect URIs configured for the application 'YYYYYYYYY'. Is this posible?

The link to sign out does not work and result in a 404.

Describe the bug
Trying to deploy mona using de Bash Command ./basic-deploy.sh

To Reproduce
Steps to reproduce the behavior:

1. Open Cloud Shell on Azure Portal

2. Run this sequence of commands

   git clone https://github.com/microsoft/mona-saas
   cd ./mona-saas/Mona.SaaS/Mona.SaaS.Setup
   chmod +x ./basic-deploy.sh

3. Run this command:
   ./basic-deploy.sh -r "eastus" -n "ycareqamona" -d "Azure Marketplace Saas Application Connection - YCare (QA)" -g "ycareqamona" -s "032e2561-xxxx-yyyy-8aef-dde43deec485"

4. Got this error:
   ....
   ....
   Building Mona web app for deployment to [mona-web-ycaremonaqa]...
   System.IO.IOException: Structure needs cleaning : '/home/luiz/.dotnet'
   at System.IO.FileSystem.CreateDirectory(String fullPath)
   at System.IO.Directory.CreateDirectory(String path)
   at Microsoft.Extensions.EnvironmentAbstractions.DirectoryWrapper.CreateDirectory(String path)
   at Microsoft.DotNet.Configurer.FileSystemExtensions.<>c__DisplayClass0_0.b__0()
   at Microsoft.DotNet.Cli.Utils.FileAccessRetrier.RetryOnIOException(Action action)
   at Microsoft.DotNet.Configurer.FileSystemExtensions.CreateIfNotExists(IFileSystem fileSystem, String filePath)
   at Microsoft.DotNet.Configurer.FileSentinel.Create()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
   at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, IAspNetCertificateSentinel aspNetCertificateSentinel, IFileSentinel toolPathSentinel, Boolean isDotnetBeingInvokedFromNativeInstaller, DotnetFirstRunConfiguration dotnetFirstRunConfiguration, IEnvironmentProvider environmentProvider, Dictionary`2 performanceMeasurements)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)
   ./basic-deploy.sh: line 503: cd: ./topublish: No such file or directory

Expected behavior
The deployment should be completed with no errors.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Win10
• Browser: chrome
• Version 111.0.5563.111

Additional context
This is a brand new subscription (Microsoft Sponsorship).

Describe the bug
Getting an error in Logic Apps when NumberOfSeats parameter is null. The parse action of the subscription object fails

To Reproduce
Steps to reproduce the behavior:

1. Create a standard from with a flat fee pricing model
2. Run the live purchase or cancellation flow (not in test mode)

Expected behavior
The Logic App should run normally and perform any added action

Desktop

• OS: Windows
• Browser: Edge

Using the Classic App Insights limits the available regions that can be used and is also flagged for deprecation in February 2024.

https://azure.microsoft.com/en-us/updates/we-re-retiring-classic-application-insights-on-29-february-2024/

We should move to workspace based version instead.

Have you guys tested this application behind an Azure Application Gateway?

URL Validation for purchase confirmation and configuration pages. Found from Casey and Josh... TBD

If setup fails, it would be nice if resources was deleted to make setup more of an atomic operation. It might not be obvious to everyone that you need to remove both the resource groups and the app registration.

Describe the bug
I was testing the mona saas framework and while trying to activate the test subscription was getting 403.

To Reproduce
Steps to reproduce the behavior:

1. In test mode click on "complete the setup" button.
2. Redirects to configured landing page
3. Try to call microsoft activate api to activate this subscription:
4. curl --location --request POST 'https://login.microsoftonline.com/$TENANT_ID/oauth2/token' --form 'grant_type=client_credentials' --form 'resource=20e940b3-4c77-4b0b-9a53-9e16a1b010a7' --form 'client_id=$CLIENT_ID' --form 'client_secret=$CLIENT_SECRET' --form 'scope=20e940b3-4c77-4b0b-9a53-9e16a1b010a7/.default'

I get an access_token as well. But when I use it in my request I get a 403.

curl -X 'POST' -H 'Authorization: $AUTHORIZATION' -H 'X-Ms-Marketplace-Token: '$'X-Ms-Marketplace-Token' 'https://marketplaceapi.microsoft.com/api/saas/subscriptions/${subcriptionId}/activate?api-version=2018-08-31'
5. See error: "The authorization token is invalid, expired, missing or this request is attempting to access a SaaS subscription for an offer that was published with a different Azure AD App ID from the one used to create the authorization token. Please make sure the authorization token is created using the same Azure AD App ID as the Azure AD App ID Id set for the offer in Technical Details tab in Partner Center."

Expected behavior
The activate request in test mode should be successful

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

I am testing Mona solution and I want to test /webhook/test
I created subscription by test landing page.
Next I want to test one of webhook for example:
Cancel subscription:
https://learn.microsoft.com/en-us/partner-center/marketplace/partner-center-portal/pc-saas-fulfillment-subscription-api#cancel-a-subscription
Url should looks like:
https://[MY MONA DNS]/webhook/test/saas/subscriptions/[SUBSCRIPTION_ID]?api-version=2018-08-31
I try add header "authorization" with "Bearer [ACCESS_TOKEN]" but I still got

I am using Postman for requests

Passthrough Mode is an awesome feature. Even if we're not yet ready to make it the default, I think it should be included in the App Settings of the App Service by default, but has it's value set to false.

That would make it easier to discover and change without having to look up the exact name in the docs.

Deployment:IsPassthroughModeEnabled

Is your feature request related to a problem? Please describe.
For smaller projects the costs of running an app service and sql server could be more than you'll probably earn from Marketplace in the startup phase. I think it would be useful to use services that can scale to zero.

We might not target small startups, but as someone who has done a lot of zero-budget-projects and sold apps on Apple AppStore, I know that marketplaces can be a super useful service, but I also know that paying minimum $50-$100 / month for something that might not work is too much.

Describe the solution you'd like
An option to deploy to Container Apps or to use Static Web Apps with Azure Function.

Describe alternatives you've considered
Write custom solution with containers or Next Js.

What if we use Azure Marketplace and a Solution Template offer to deploy MONA in the clients subscription?

I do not have a complete plan on how to do this, this this post is a mix of ideas and questions.

Collect information from the user

A createUiDefinition.json file can be used to collect more information from the user, such as options we have both as required and optional in the basic-deploy.sh script.

Deploy ARM template

How much of the CLI commands in basic-deploy.sh can be created with ARM templates and the variables from createUiDefinition?
Is it possible to run a script during deployment of a Marketplace solution, and if so, could we use basic-deploy.sh in a headless mode with arguments collection from createUiDefinition?

Why would it be worth the time?

When I speak to customers, partners and actually even Microsoft employees, they don't see a clear and easy path to get their solutions to Azure Marketplace. If we could make it as simple as a couple of clicks in the Marketplace I believe we can improve the number of solutions in the marketplace, and also show that we eat our own dog food.

– How do you get started with Azure Marketplace?
– Just install it from Azure Marketplace. :)

Let's discuss if this is a good idea and possible for us to achieve.

Dotnet 3.1 is no longer supported. We should update Mona to dotnet 7 asap.

https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

When running in cloud shell, are prereqesuites (zip, az, etc.) are always available but, when running locally, the user may run into problem when running the script if prerequisites are not installed.

We need to harden the setup script that it checks for all prerequisites before attempting to set up Mona.

When running locally, user might not have the jq dependency installed. We should check for this when checking other prerequisites.

Describe the bug
When running ./basic-deploy I'm stuck in a loop where I need to login. First I got this message:

A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.
The following tenants don't contain accessible subscriptions. Use 'az login --allow-no-subscriptions' to have tenant level access.
b89759cb-5739-4d4f-aba7-d8c17cbc2d9d 'Aktieguiden'
d4411231-0e72-43bc-9fa7-21b96e017c35 'Aktieguiden'

How ever, none of these are my set tenant when using az account show. I tried to delete these from Azure Portal since they're not used anymore. But, this did not fix the problem. I'm still stuck in the same loop of logins.

To Reproduce
Steps to reproduce the behavior:
I get the error when running ./basic-deploy.sh -r "swedencentral" -n "superuniquename" -d "My super good name" -s "xxxxxx"

Desktop (please complete the following information):
macOS

Output from script

[cloudqrmona  ]> Checking Mona setup prerequisites...
[cloudqrmona  ]> ✔   Azure CLI installed.
[cloudqrmona  ]> ✔   .NET installed.
[cloudqrmona  ]> ✔   All Mona setup prerequisites installed.
[cloudqrmona  ]> ✔   [swedencentral] is a valid Azure region (Sweden Central).
[cloudqrmona  ]> ✔   [2021-10-01] subscription event version is supported.
[cloudqrmona  ]> ✔   [en] language is supported.
A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with `az login --use-device-code`.
[
  {
    "cloudName": "AzureCloud",
    "homeTenantId": "xxxxx",
    "id": "xxxxx",
    "isDefault": true,
    "managedByTenants": [],
    "name": "Visual Studio Enterprise Subscription",
    "state": "Enabled",
    "tenantId": "xxxxx",
    "user": {
      "name": "[email protected]",
      "type": "user"
    }
  }
]

I have successfully ran basic-deploy.sh and got the URL's for the landing page. I visit the /setup url and login with the same account that ran basic-deploy.sh.

I still get the Access Denied page.

I've no tried this with to completely different Microsoft account.

Any ideas why I get this error?

As far as I understand, Mona is using only one Azure AD App Registration for multiple purposes:

• Communication with Marketplace APIs
• Single-tenant SSO for admin(s)

Wouldn't it make sense to separate that in several Azure AD App Registrations and to allow the use of existing App Registration during setup instead of creating new one?

Describe the bug
A clear and concise description of what the bug is.
If you have a guest account and try to access any page , returns an Access Denied.

To Reproduce
Steps to reproduce the behavior:

1. Create a guest account in your tenant
2. Add the Mona Administrator role to the user
3. Log in with your guest email credentials
4. Receives Access Denied page

Expected behavior
A clear and concise description of what you expected to happen.
Expected to be able to access the page
Screenshots

Desktop (please complete the following information):

• OS: windows 10
• Browser Chrome
• Version 106.0.5249.119

Additional context
Add any other context about the problem here.

When purchasing a solution the confirmation page of mona cannot find subscription information anymore.

Mona version 1.0.3.

We had are running the clean version in production.

To Reproduce
Steps to reproduce the behavior:
buy the solution
click on configure the account.
An error page is showed

Expected behavior
Go the the confirmation page

the Test page of mona is working well.

this

Screenshots

Describe the bug
The lp=$1 assignment in the checks breaks the if statement that follows afterwards. For instance, https://github.com/microsoft/mona-saas/blob/main/Mona.SaaS/Mona.SaaS.Setup/basic-deploy.sh#L29-L35

The if statement always returns 0 for the latest status code as lp=$1 directly runs after dotnet --version >/dev/null 2>&1 and always succeeds with exit code 0.

Hence, my initial setup failed to compile and upload the .NET application to the Azure Web App as .NET is missing on my MacBook.

To Reproduce
Have a MacBook without .NET installed. The pre-check will return true that .NET is installed instead of aborting the setup.

Expected behavior
That the setup script fails if I do not meet the prerequisites.

Describe the bug
AAD App registration multi tenant authentication not working without publisher verification of the automatically created AAD app. Had to find this through trial and error no where in the documentation this is mentioned.

Describe the bug
We're doing some tests to deploy a solution on Azure Marketplace and followed the instructions for setting up MONA SaaS.

We checked via the command line interface that the MONA resources (resource groups, app plans, app service, storage account etc.) were deployed correctly and the solution is working. However, those same resources do not show up when you access the Azure control panel via web.

To Reproduce
Steps to reproduce the behavior:

1. Follow the MONA setup instructions on https://github.com/microsoft/mona-saas
2. Check via Azure CLI that resources were deployed
3. Access the Azure subscription control panel via web
4. Deployed resources do not appear on the control panel

Expected behavior
Resources deployed by MONA should appear on the web control panel.

Desktop (please complete the following information):

• OS: Windows 11 (build 22621.1848)
• Browser: Chrome (114.0.5735.198)
• Azure CLI: 2.41.0

Hello,

One of my partner is facing the issue described on the doc regarding the disconnection of their logic app triggers to the grid.

When trying to reconnect, they are facing the following issue:

Is that an issue seen before by someone?

Describe the bug
In the last step of the logic app for a successful purchase where is an AND condition. One of the condition is a "true equals false" condition, which obviously cause it never to be true and therefor never resolve the subscription.

Kind of confusing... :)

https://github.com/microsoft/mona-saas/blob/main/Mona.SaaS/Mona.SaaS.Setup/integration_packs/default/on_purchased_workflow.bicep#L233

Mona cannot be installed in all regions. For instance, when trying to install in Sweden Central you get this error:

{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"BadRequest\",\r\n \"message\": \"Region doesn't support Classic resource mode for Application Insights resources. Please use Workspace-based mode.\",\r\n \"innererror\": {\r\n \"trace\": [\r\n \"System.ArgumentException\"\r\n ]\r\n }\r\n }\r\n}"}]}}

Would it be possible to either check before setup starts if the region support required Classic Resource Mode, or avoid this Classic Mode?