Is there a way to identify the knowledgebase that we have created is not vulnerable and open for security threat? Can someone else break into the existing Knowledgebase and access our inhouse documents? We are keen to know about this so that we need to decide on whether to go ahead with this implementation.
Microsoft provides several resources that you can reference regarding privacy and security. The first doc gives a simple overview of MS compliance and privacy. This link is a detailed report on Microsoft Azure Compliance Offerings that should answer any question you have. This last link is Microsoft's compliance website where you can explore offerings across different regions, industries, and products.
Hope of help!
Related
I have created a custom question answering project using Microsoft Conginitive Services and deployed the same.
Now I would like to create an UI where an user can see the unanswered questions and update the knowledge base with appropriate answer using the UI itself.
From the deployment details, I am able to extract the Ocp-Apim-Subscription-Key. But I am little confused about the appropriate way of API call in my UI to track and update the unanswered questions.
Could not find many write-up or examples regarding this. Please guide me regarding the same.
It depends on the questions answering resource type you are using, as this service has evolved.
Azure Cognitive Service for Language (end of 2021)
This is the newest version of QnA Maker (as of late 2021), now called "Custom question answering" being part of Azure Cognitive Services for Language.
This service has a better offering in terms of API:
Service documentation is here
API documentation here
The "active learning" feature is offered through Language Studio portal (see doc).
But if you want something custom, you might be interested in the Authoring API: programmatically, you could use "Get QnAs" operation will give you all QnAs, and the RetrieveQnaRecord object included in the response contains a SuggestedQuestionsCluster object which could lead to interesting feedbacks to add.
QnA Maker (v4.0)
QnA Maker 4.0 has a REST API documented here.
In addition, you can directly check some calls using the API exposition in the right region. Example for West US here
=> For this service, there is no "feedback" solution exposed. The API allows to update a knowledge base, but you will not have an operation providing unanswered questions.
My boss purchased Microsoft 365 which came in three products. He now challenged me to design a management system, like an employee self-service portal. I am hereby looking for advice on where to start or which product to use, since I am new to this.
I have tried a bit of research and I came across the Sharepoint platform which can be used to create workflows and automate tasks. Is this the right way forward or there is a better and standard way to do it? Please somebody advise me.
Yes, you are on the right track if your goal is to create an employee portal. SharePoint and Azure Active Directory are the right services to start with. There is no best practice per say since it is all code and you could even build your own .NET app from scratch if you wanted to do that, but SharePoint is useful because it can give you some frameworks for getting something like an employee self-service portal set up quickly.
There are some good tutorials out there for this already:
https://www.youtube.com/watch?v=1NX0oh3VSNU
https://resources.techcommunity.microsoft.com/resources/build-modern-intranet-on-sharepoint-office-365/
This one even has some best practices for design choices:
https://blog.mydock365.com/employee-portal-design-sharepoint-intranet/
Hope this helps!
I would encourage you to explore the training portal for Microsoft 365 and SharePoint specifically:
Here is a link to the free SharePoint training resources offered there:
Microsoft Support: SharePoint video training
This site also offers some fantastic infographics and cheat-sheets for SharePoint:
How to customize your SharePoint website
Office cheat sheets: SharePoint Online
Check out the SharePoint Look Book:
SharePoint Look Book
We're completely upgrading our production and development environment from co-located boxes to an Azure implementation and we'll be developing using Visual Studio Online. Up until this point our dev has occurred on a Remote Desktop environment where developers were logging into Windows server and developing on that RDP box.
We want to set this up and we have some confusion about the Account types/set up types.
It appears there are two ways to set up our Azure and two ways to set up our developers. We are a MS partner w/ some MSDN licenses and Azure credits.
So for Azure we can use our existing MS accounts and just set up an Azure Pay As You Go (PAYG) subscription. This was suggested to us initially but it seems weird to have the entire companies Azure environment going through an individuals live ID. Then we saw we can sign up as an Organization now and it uses Azure AD. We have not been using Active Directory and we're not sure how much complexity this is going to add to our administration. Is there a discernible difference/benefit to going one way or the other?
Then, when we sign up our developers we can either have everyone sign up with their live ID's (we have MSDN w/ VS Premium credits for all developers) or we can set them up using Active Directory with Work Accounts. Having our credits allotted in work accounts sounds like a good way to control things at first reading, but it also seems a bit more complex. I'm wondering if there is much difference between MSDN accounts signed up w/ live IDs or AD Work Accounts. I can't find a real comparison article or pro/con type of discussion anywhere.
It sounds like you have already figured out the main differences. As an organization, I would suggest signing up for Azure as an organization. You can do that here. This is going to give you the management capabilities for resources typically needed by an organization.
Your developers can continue to use the MSDN subscriptions. As Dylan commented, these are not to be used for production environments. You should consider using these for Dev/Test environments and activating your MSDN benefits. This will save you some money. More on that here.
Visual Studio Online will work with your Work Accounts and again give you more control over managing your online resources. This link describes the sign-up process for both Microsoft Accounts and Work Accounts. And if you scroll down a bit you will find your original question specifically addressed.
Finally, you can also add your Work Account(s) to your existing MSDN subscriptions if you like. This way you (and your developers) can use the same account credentials when accessing Azure Subscriptions. Information on how to do that is available in this link.
Your Work Account subscription should be limited to personnel responsible for managing your "production" environment.
After signing up for Azure as an Organization, you can add users to the directory as described here. You can also add "external" users using their existing Microsoft Accounts. It's just a few dialogs to add a user.
Do we have azure based site to share technical knowledge with team. To interact with colleagues. Or Do we have ready made site which we can customize?
I'm going to make a big assumption that I understand what your question is. Assuming you are looking for some type of collaborative website engine that can easily be deployed within Windows Azure, for the purpose of collaboration amongst your peers:
If you create a new Windows Azure Web Site and look at the gallery, you'll see several ready-made options such as Mediawiki, phpBB, DotNetNuke, Joomla, Kentico, Lemoon, mojoPortal, Orchard, Umbraco, and WordPress. I'm guessing at least one of these would help you build a collaborative knowledge site for your team.
Per your comment (which makes me think I assumed correctly): here's starter info on Web Sites, from the Azure portal. Also you should download the Training Kit, also linked from the Azure portal.
I´m interested to capture links, references and comments about multi-tenant architectures to deploy in the modality SaaS (Software as a Service) on the Windows Azure Platform.
One link for you is the Fabrikam shipping sample from microsoft - https://fabrikamshipping.cloudapp.net/
Source code - http://archive.msdn.microsoft.com/fshipsaassource
Blog posts - http://blogs.msdn.com/b/vbertocci/archive/2010/10/07/new-online-demo-introducing-fabrikamshipping-saas.aspx
You can also look at our sample and book. It is similar to Fabrikam but has the content that goes along with the code that talks about all the trade offs. We will be updating our code/content in the next month to work with the new features of Windows Azure (ACS & Caching).
You can get the book on Amazon.
Here's a brand new multi-tenant sample application, Cloud Ninja, that demonstrates several facets of a multi-tenant application in Windows Azure. There's also a related blog here.
One thing you might need for your multi-tenant architecture is to have multiple SSL certificates (one for each tenant's custom domain) for a single HTTPS binding.
I'm a Microsoft Technical Evangelist and I have posted a detailed explanation and a sample "plug & play" source-code on how to do it with Azure Cloud Services with SNI at:
http://www.vic.ms/microsoft/windows-azure/multiples-ssl-certificates-on-windows-azure-cloud-services/