如果您有点像我，那么您会 最有可能使用年末季节来放松情绪，停下来 此刻，请考虑下一步。
是的-绝对，假期是指冷静，放慢脚步，与朋友和家人共度时光以及将时间奉献给您的亲人。对于我来说，在这些日子里，在饮食，家人和朋友聚会之间，还有很多“lay low” moments when I can digest technical topics or read up on them â€“ I am usually on the sofa and reading. Why not read something you enjoy and wanted to digest for quite some time â€“ even if itâ€™s technical and job-related? For as long as it doesnâ€™t get your thinking gear about the 问题s at work going or you get emotional or angry â€“ thereâ€™s no harm. We work in technology â€“ for as long as itâ€™s exciting, I would consider it fair game ðŸ˜Š
无密码：这是微软的既定目标之一，也是中期的旅程。密码是可以用来证明自己是谁的许多可能的凭证之一，而我们想转移到某个地方“better”。虽然概念很明确并且很有意义–这对您和您的组织意味着什么？什么“other” credential do you see? What use cases would that 其他 credentials have to support? Is it multiple credentials (tokens, FIDO, app, â€¦)? How do users enroll this new (secure!) credential (in a secure!) way? What is the bootstrapping process to do this? What is your debt to make 密码 go away entirely (applications, interfaces, devices)? What is your strategy to move the relevant applications to 蔚蓝 AD (where password-less will be easiest)? What can you do to start embarking on the password-less journey in the next quarter (Windows 你好 for Business)? You want to read more, check 我之前关于无密码的文章.
企业与企业之间：如果尚未使用Azure AD B2B，请考虑一下此概念。我的主张是，如果您是在线公司并且使用SaaS应用程序或Office 365，则迟早要支持协作方案。请尝试使自己熟悉一个想法，即并非您正在运行或托管的所有应用程序都专用于内部用户-但是业务合作伙伴，供应商等。如果您还没有-尝试熟悉一下Azure AD如何进行B2B（相对于某些其他产品）。尝试开始考虑应用程序分类和数据分类–当您考虑该应用程序时，应将其视为仅仅是数据的容器。您允许外部合作伙伴采用什么策略？那是用户主导的过程吗？用户是否通过一个中央门户网站，该门户网站使您可以控制谁邀请谁，或者是帮助台或IT驱动的活动？所有应用程序公平吗？是一些应用程序的禁忌（分类吗？）您如何跟踪那些外部组件（及其标识引用）？您是否已有内部流程–并且可以针对云进行调整？
企业对消费者：与合作伙伴和供应商交谈是可以的，对于某些组织“must”，因为该业务模型与生态系统，合作伙伴等紧密集成。您的业务模型是否预见到直接与消费者交谈和合作？给他们一个与您的业务互动的平台？购买，购买，提供反馈？与其他消费者交谈并交换想法–是否让您跟踪这些情绪并将其反馈回您的业务和工作中？ B2C是一个“problem”目前在“business” and “developers” (this is a claim I am making â€“ true or false?). Business may be interested in talking to consumers, 开发商 would have to build and drive the creation of a platform that brings 商业 and consumers closer together â€“ that may be highly 商业-related and canâ€™t be bought off-the-shelve. How does that fit your overall 身份 story? Is there a need to integrate these consumer-centric platforms/applications with backend systems, so two 身份 worlds collide? Do you feel IT should be involved, or is this best housed with Business + Devs?
应用程式，应用程式，应用程式: Where are most of your applications today? Where is the 商业 moving? Building 现代 workplaces and a foundation for collaboration with partners and vendors will have some impact on your application landscape. These things get easier when your applications are “natively”语音云–并集成到身份提供商中。你那里的故事是什么？有关系吗？什么是最复杂的应用程序？如何授予（供应商，合作伙伴）这些应用程序访问权限？公司范围内是否有赞成的决定“modern” applications that speak cloud 本机地? How is it enforced? What are the inhibitors to make this decision (no more Windows AD-integrated applications
保持控制: How do you control this madness that the industry calls 数字化转型? The perimeter melting away, applications everywhere, users everywhere? How well defined is your governance story for applications, data, users, devices? How do you keep your 商业 secured, while at the same time allow productivity to happen (with little to no boundaries)? How do you make sure that the right people have the right access at the right time? Even from day 0, when they start? How do you make sure they lose access when they leave or change their job? How do you know who should have access to what? Is that an IT 问题 to figure out â€“ or an IT 问题 to translate and supportâ€“ but someone elseâ€™s 问题 to decide and define? Who grants access â€“ IT, 安全 or resource owner? Or all of them? Do you have all the lifecycle processes in place to automate as much of this madness as possible â€“ and get
云先: When will you be able to turn your mindset and your 商业 upside down â€“ and see the cloud as your native place, your home story, the place you are â€“ and on-premises a satellite thatâ€™s kept for small, simple things that you still rely on (printing!?). While this may be unbelievably far away, depending on your size, industry, etc. â€“ think about the inhibitors that keep you on-premises. What is it, that keeps you there? Applications â€“ how can you remediate that? Why are they on-premises and not in the cloud (protocols? Access to Domain Controllers)? Resources â€“ such as printers? Highly confidential things that cannot go to the cloud (canâ€™t they do â€“ or do we lack the right controls such as the right encryption so only you can read the data, and where itâ€™s stored becomes irrelevant?). Hardware â€“ what hardware do you rely on that doesnâ€™t support cloud? That canâ€™t be managed through the cloud? This isnâ€™t about solving all of these 问题s right now â€“ but being aware. And by being aware, keeping track of these things. And to make it even more fun, 阅读先前尝试迁移应用程序的故事 到云。
就这样，我的想法清单 身份。您注意到，我问了很多问题而没有回答。 但是，我希望这篇文章有点令人发指，并且您走了 有关在此新产品中要研究的内容的一些新思想，想法和线索 year 2019.