Im trying to create a teams extension/app without using my school or working email since i would need to ask my administrator. I just want to do some testing without deploying the app.
Thanks
I tried to sign in to a basic account, school account but sideloading isn't activated and I need to ask the administrator for such a thing
Microsoft provides free 365 developer accounts for exactly this type of need - please see https://developer.microsoft.com/en-us/microsoft-365/dev-program
Related
I have developed a bot by modifying the template provided from https://github.com/microsoft/botframework-sdk. The bot works perfectly in the Bot Framework Emulator.
I have tried to deploy it by using my trial account. it looks like it is lack of some accesses, which i am not quite sure.
my question is, if i plan to deploy this bot into MS teams installed on my computer, can it be fulfilled by using my trial account in Azure? or i need to purchase a paid account?
Regards,
It's completely possible to run in on Azure, and everything will work 100% fine a free trial account, or of course with a paid account. Be aware that the "web app bot" template will default to a "standard" pricing model in Azure, which will use $70 of your credit, so you should change it to a cheaper price plan immediately, especially if you're just using this for development. There's even a "Free" option (i.e. free forever, even after the Free Trial expires), but then it's limited to how many hours per day the bot will run.
Another option is to host your bot in an Azure Function ("serverless"), but it's a lot more work as the samples and wizards on the internet mostly use the Azure Web App model, so you'd need to manually convert it over to running that way. Certainly you can get started with the free trial though!
As another completely possible option, if this is just for development, then you can run the bot on your local machine, using Ngrok, which creates an real, live "https" address for you, that Teams can accept to work with your bot, even though it's running from your local machine. This is of course great for development/debugging, but not realistic for a live deployment.
I am a Software Engineer and working on developing an integration of my company's product with Microsoft Teams. The idea is that the product will send messages/notifications/alerts to a chat channel in Microsoft Teams. At the moment we are only working towards developing this integration with Microsoft Teams and not other office 365 products.
After researching on MSDN, Microsoft developer platform, google etc. I came to know that I can set up an incoming webhook which gives me a URL against a channel in Microsoft Teams and I can send messages to it. However, I came across another method which is having a connector in the Microsoft store. I would like to add a connector because it provides a nice front end and also gives us a presence on the store for external users. I found out that I can register a connector from the connector developer dashboard. Here is the documentation link that I was referring to:
https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/connectors
To test it out I referred to the following example on the MSDN blog:
https://blogs.msdn.microsoft.com/mvpawardprogram/2017/01/24/part-3-office-365-groups/
However, I am unable to see Microsoft Teams groups in the drop down. I am the owner of these groups on Microsoft Teams side. At my organization only I am using Microsoft Teams to test this integration because I am the only developer working on this. Please, see the screenshot below:
Then I read about sideloading your connector to Microsoft Teams to test it out which meant uploading the manifest.json file from the connector developer dashboard. Please, see the below screenshot:
But, after I download the manifest file and follow the instructions mentioned on this link https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/apps/apps-package I am still running into problems testing the office 365 connector with Microsoft Teams when uploading the manifest file. This is the error that I get, please see the screenshot below:
Also, I do this from my developer trial account and this is because from my company's paid developer enterprise account I do not see an option to upload a custom app. Please, see the screenshot below:
This is a product issue and I have been in touch with the product support for the past three weeks. We have tried various things over this course of time and nothing has worked. They have also ran recovery diagnostics on my account as well but, I saw no changes. All they tell me is that "this is bizarre, this should not be happening and that maybe Teams is a fairly new product and nobody develops for it etc. etc. " Although I do feel many enterprises are using it. Please, see the screenshot below:
I have not heard back since then. Please, help me regarding this issue. I would really love to start developing the actual integration with our product since it would be of great value to our customers.
Thanks,
Maria Shoaib.
Please use App Studio to create manifest file and test your connnector so that there are no errors while creating an app package. Also, please ask your tenant admin to enable the sideloading of external apps for Upload Custom App link to appear in Microsft Teams.
i researched a lot to unlock my nokia lumia windows 7 device in order to deploy my app but didn't find any satisfying answer or procedure. I'm a student and wanted to test my final thesis app on my device but when i go for the device unlock procedure i have to pay for it for Microsoft's developer account in order to test the app. Please guide me is there any other way to test the app on my device ?
http://msdn.microsoft.com/library/windowsphone/help/jj206719(v=vs.105).aspx
Individual or Student: Select Individual if you’re an individual developer. Select Student if you’re a student with a verified DreamSpark account. You can get a new DreamSpark account during registration. At this point, you’ll be required to provide proof of your student status. There’s no annual membership fee for if you purchase the subscription using DreamSpark. You’ll receive a verification email from Dev Center to validate your email account.
If your university is part of the Microsoft Dreamspark Program, you are lucky in this case :)
I have a Wp7 app (ready in a xap), and I'd like to give it to a client, so he can use it in 5-10 devices. But it is an "internal" client for our service, so I'd rather not publish it on WP Marketplace for all to see...
Is there any reasonable way to do this?
when you upload app on marketplace you can set it as private so only users with direct link can see/install it. There was an app which hacked WP7 that allows you to install apps without marketplace but I've heard it's not legal anymore*.
*search for it because I'm not sure about this one.
edit: http://www.electronista.com/articles/12/01/02/chevronwp7.runs.out.of.tokens.may.not.renew/
Maybe you can try http://labs.chevronwp7.com/
EDIT : Sorry, it seems that all tokens are sold out, so this is not solution for you.
As pointed out by others, you can publish a application on the marketplace as a beta, allowing 5 users to test it using their Live IDs.
But all unlocked phones can have a XAP installed. Generally, Windows Phone applications aren't designed for internal distribution. If you don't intend to publish the application on the marketplace at any point, you need to estimate in the cost of $100 per phone, per year, for the usage of your application.
I'll recommend you contact Microsoft, if you need a specialized deal.
I am developing an app, which I have tested on the visual studio Emulator. I would Like to deploy it to about 8 Phones within our organization. Is there a way to deploy apps directly to the phones without going through the marketplace, or without having to pay the $99 per year app hub memebership fee. I don't need to deploy apps to the marketplace place at this time, just directly to our personal company phones.
I have tried running the "windows phone developer registration", but I get a message stating that I have to register my phone in the Marketplace, and that is where I am asked to pay a $99 membership fee.
Nope, unfortunately you can't deploy to any phone you want. The phone needs to be developer unlocked, meaning you need to have paid the $99 AppHub membership fee and registered the phone. I believe you can register a maximum of 3 phones under one account.
The other option is to, of course, jailbreak the phone. Google to see if you can lay your hands on a copy of Chevron WP7. The other owners may not be very willing to go along with this though. On the other hand, they'd probably love it if you bought all of them AppHub licenses :-)
You can unregister phones on AppHub, so maybe you can buy one license, unlock 3 phones, test on those, then unlock another 3 after unregistering the first 3 ...
If you have one developer account, you can use the beta feature on the AppHub to allow the other users in your organisation to download the app from the marketplace.
You just have to add their LiveId to the app. There's a limit on users, but if it was 10 or 50, I can't remember. You should go check it out.
If you don't have a developer account, you're pretty much square.
Stay tuned for Chevron Labs, where you will be able to unlock multiple devices for a small fee (in case you don't need to distribute apps in the Marketplace - exactly your situation). Otherwise, your only official choice is the AppHub unlock.
You must register as a developer, for which you have to pay the $99 registration fee. However, the new AppHub update gives you the ability to deploy your apps to the phones in your enterprise at no further cost, and they do NOT have to be developer unlocked.
You have two options. First is the private beta, in which you can have up to 99 people get your app before it goes through certification. I don't remember if this is time-limited or not. Second, is after your app gets certified, you can publish it as a hidden app, and only those people that you want to be able to install the app can. No one else can even see it in Marketplace.
Don't mess with unlocking the phones you want to put the app on - the best way is to go through the process and publish the apps as hidden.