Your company has an Azure Stack integrated system with 100 tenants.
You have been assigned a task to create a new Private offer and provide the offer to a tenant.
How would you achieve that?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: D
While creating an offer, including at least 1 base plan; you can even create add-on plans that the tenant users can add to their subscriptions.
A subscription defines how the users will access your offers.
After creating an offer, the users require a subscription to that offer before they can utilize it.
Subscriptions can be created for both private as well as public offers.
If you don't want to allow your tenants to create or develop their own subscriptions, just make all these offers private, and after that create or develop subscriptions on behalf of the tenants.
This is the common approach followed while integrating Azure Stack with external billings or service catalog systems.
After you create the subscription for a tenant user, that tenant can log in to the user portal and check the offer he or she is subscribed to.
Option A is incorrect.
Azure Stack operators can use the delegation functionality to allow the other users to create the offers and users.
Option B is incorrect.
New-AzsOffer cmdlet can be used to create an offer consisting of specific base plans and some add-on plans.
Option C is incorrect.
Cmdlet Set-AzsSubscription is used to modify the tenant subscription of the currently logged-in user.
Option D is correct.
The goal can be achieved by creating a new subscription and then assigning the subscription to the tenant.
Reference:
To know more about creating subscriptions, please visit the below-given link:
To create a new Private offer and provide the offer to a tenant in an Azure Stack integrated system with 100 tenants, the following steps can be taken:
Option A: By delegating the rights to the tenant user and instructing the user on how to create or add a new subscription. This option involves granting the tenant user the necessary permissions to create or add a new subscription. This can be achieved by delegating the 'Owner' role to the tenant user on the subscription. Once the tenant user has the 'Owner' role, they can create or add a new subscription. However, this option requires the tenant user to have sufficient knowledge of Azure Stack and the subscription creation process.
Option B: By running the cmdlet New-AzsOffer and assigning the subscription to the tenant user. This option involves creating a new Private offer using the New-AzsOffer cmdlet and then assigning the offer to the tenant user. This option allows for more control and customization of the offer being provided to the tenant user. The cmdlet creates a new Private offer in Azure Stack Hub Marketplace with a specified SKU, pricing model, and terms. After creating the offer, the cmdlet can then be used to assign the subscription to the tenant user.
Option C: By running the cmdlet Set-AzsUserSubscription and then specifying the subscription of the tenant user. This option involves setting the tenant user's subscription by using the Set-AzsUserSubscription cmdlet. This cmdlet is used to configure the Azure Stack Hub subscription of a user in the directory. Once the cmdlet is run, it assigns the specified subscription to the user.
Option D: By creating a new subscription and then assigning the subscription to the tenant. This option involves creating a new subscription and assigning it to the tenant user. This option allows for complete control over the subscription creation process, but it requires a higher level of knowledge of Azure Stack and the subscription creation process.
In summary, the best option for creating a new Private offer and providing the offer to a tenant in an Azure Stack integrated system with 100 tenants would depend on the specific requirements of the tenant and the level of control and customization needed. Option B (using the New-AzsOffer cmdlet) would provide the most control and customization, but it also requires more technical expertise. Option A (delegating rights to the tenant user) is simpler but requires the tenant user to have sufficient knowledge of Azure Stack. Option C (using Set-AzsUserSubscription) and Option D (creating a new subscription) are also viable options, but they may not provide as much control and customization as Option B.