I want to get the introduction about a Client adding subscription on behalf of client 2,do you know where introduced in the solace guide,thanks you
You are looking for subscription managers.
A subscription manager is a custom coded program running in the back
end of your enterprise which manages subscriptions for other clients.
Solace enables a centralized subscription management architecture by
providing a special feature which allows certain clients to subscribe
and unsubscribe to topics on behalf of other clients.
There's a couple of blog posts on the Solace website that describe this in detail.
An Architectural Look at Managed Subscriptions in Solace
Solace Managed Subscriptions in Action
Related
It seems that Microsoft Teams conectors have to be registered/owned by an individual's microsoft account (unless they are published to the app store), whilst the Microsoft Teams app that uses them, can exist independently. Thus, if the individual who developed the connectors leaves the company, and their account is closed, all the company's connectors will stop working. Then new connectors will have to be created and the existing Teams app manifests will have to be modified. This will cause a problem for our clients who rely on them.
Is this correct and is there anything we can do about it?
I understand that the connectors and app could be published to the app store, but it is a private app, intended solely for use by our selves and our clients, so we don't feel it is appropriate to publish it.
The connectors are generated through the Connectors Developer Dashboard, https://outlook.office.com/connectors/publish and are owned/registered to the developer's Microsoft account. We use them to send notifications from our custom web app to our clients' channels in Microsoft Teams.
I want to deploy our SharePoint remote event receiver inside an Azure web app. but when i create a new web app i got 2 subscriptions ("Microsoft Azure" OR "Pay-As-You-Go"), as follow:-
So i am not sure what are the main differences between these 2 subscriptions?
second question; which one is more suitable for hosting SharePoint remote event receivers?
Pay as you go is just like it says, you pay for only the services that you use, based on the pricing for that service. More info here.
A subscription is as described here "a logical grouping of Azure services that is linked to an Azure account. A single Azure account can contain multiple subscriptions. Billing for Azure services is done on a per-subscription basis. For a list of the available subscription offers by type, see Microsoft Azure Offer Details"
You have two subscriptions set up. On is a pay as you go subscription, and one is another type, although I'm not sure what. There should be no difference which one you select from a technical standpoint. It is only a matter of how you want to be billed. Azure web apps have a free tier as well.
There is no technical difference between the two subscriptions. There might be a difference with regards to support levels or service level agreements (SLAs), e.g. if one of them is a Dev/Test subscription. There might be a difference in "purpose" - one might be exclusively for "production use cases", while the other might be for testing. There is no way for us to know.
You really should ask the person responsible for the Azure subscriptions on which one you should use. If you set them up yourself, you take a more detailed look at the subscriptions themselves.
we are working on an integration with service bus. We don't have an account with azure, so we can't run our own server, but our client does.
For testing purposes, are there any openly available service bus topics I can subscribe to and test our code? the content actually does not matter, we just want to make sure our code can connect and read messages.
If this is not possible, how is the approach for testing our subscription code for azure service bus? Do we need to open a azure account?
thanks!
You do need your own subscription to create and test Service Bus Topics.
To create your free Azure Subscription refer here.
Can I create and deploy Microsoft bot without azure services?
I want to use LUIS services without azure services.
Is it possible? Alternatives for azure?
Thank you for replies in advance
To answer your question - it is possible to create a bot which uses LUIS without using the Microsoft Bot Framework -
Using LUIS: LUIS expose their service via HTTP endpoint. If you create an application in LUIS and create a model, you can get the intents by issuing a request to the provided endpoint. It is not directly associated with Azure. Note that in order to allow unlimited traffic to your endpoint, you will need to associate it with an Azure subscription, but you do not have to use any Azure resources.
Microsoft Bot Framework - In order to create a bot without using the bot framework, first let's understand what services the framework provides you with. you need:
Somewhere to host your bot as a service. You can use any cloud provider for this or even host it on your machine
Build your bot - you bot will have to implement a conversation protocol, depending on the channel for which you are writing your bot
Integrate with the channel for which you are building your bot for - bots for Facebook, Telegram or Skype have different protocols and need to be connected differently with these platforms. The Bot Framework simplifies this process for you. But you can just create a specific bot for your desired platform. For that, you should check the documentation for the channel which you develop for.
What permissions I need to set for the following scenario:
I want to use Azure service bus in order to be able to connect a windows service agent running on premise and a worker role running in azure. The agent itself is a software that will run on different customers premises and communicate with my worker role via service bus. The worker role once per day will send a message to specific (maybe all, maybe few only) customers agent on premise, asking for some data. The agent will return the data to the worker role via service bus. In order to send custom message to specific customer agent I will use topics and subscriptions where every customer agent will lessen to it's specific subscription.
Now in order to build that agent and access service bus I have to make use of the namesapece, issuer name, issuer key which by default it's owner. Well owner has full control everywhere on that service bus therefore I don't want to give the owner credentials and secret key to each customer agent service. That means I have to build custom identity for each customer or a common one for all.
My questions: what do you recommend:
one common service identity for all agents or generate one identity for each agent service?
what is the minimum access I should give to them? I guess Listen and Send right?
We use the Service Bus Relay to expose internal services to third parties. We secure the services using SAS and create a new Shared Access Policy with the appropriate permissions (typically Send, Listen) for each client. On the "Configure" tab in the portal, add a "new policy name" then "save". You can then retrieve the Shared Access Key in the bottom section of the portal.
We found this method easier than generating IDs under ACS.